Since august after some recent updates I got a issue that my desktop freezes randomly. I don’t know how to reproduce it but it’s really annoying. I am not able click on anything, all completly frozen. It’s really annoying when you realize your clock widget is frozen and you live in totally diffrent time.
Restarting plasmashell helps but sometimes it’s just frozen on the command and not able to restart itself.
Also when it happens plasmashell utilizes 100% of my CPU. I tried to reset all settings, remove configs, did not help. Is there any log or someting that I can debug why it happens?
same issue for me. Kicker or Krunner are unresponsive, and cursor freezes briefly every second…
Plasma is unusable, even when I force a restart. Also the same on a fresh new create linux user…
KRunner just would not load today. First time issue ever encountered.
Then laptop frooze. Would not restart or shut down Lenovo Thinkpad.
Laptop has 32GB Ram and 1T SSD and is superfast all the time.
After many hours turned off.
Now Kde plasma will not load as befor.
Am taken to a completely new blue screen which is frozen, asking for password, and not the normal Plasma log in screen.
Am completely lost now as a new Linux user of 6 months.
Same here after some update but no cpu usage here’s the logs:
Sep 25 19:02:50 Sanctum-Sanctorum systemd[1154]: Started Strawberry - Strawberry Music Player.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 1135.
Sep 25 19:02:51 Sanctum-Sanctorum strawberry[14632]: 19:02:51.073 WARN OSDDBus:184 Error sending notification "org.freedesktop.DBus.Error.NoReply"
Sep 25 19:02:51 Sanctum-Sanctorum strawberry[14632]: 19:02:51.997 WARN OSDDBus:184 Error sending notification "org.freedesktop.DBus.Error.NoReply"
Sep 25 19:02:53 Sanctum-Sanctorum systemd[1154]: Started Konsole - Terminal.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 1157.
Sep 25 19:02:53 Sanctum-Sanctorum kded6[1337]: org.kde.plasma.appmenu: Got an error
Sep 25 19:02:53 Sanctum-Sanctorum kded6[1337]: org.kde.plasma.appmenu: Got an error
Sep 25 19:02:53 Sanctum-Sanctorum kded6[1337]: org.kde.plasma.appmenu: Got an error
Sep 25 19:02:53 Sanctum-Sanctorum kded6[1337]: org.kde.plasma.appmenu: Got an error
lines 1354-1398/1398 (END)
Same issue, but only occurs when running certain GPU applications such as DosBox with the CRT filter or GZDoom. I think in 10 years this is the first time I’ve seen PlasmaShell behave this way.
