Happens each time I resume from suspend with the Oxygen Plasma theme. It seems that the crash occurs when the NetworkManager applet pops up the notification that it has reconnected to my WiFi connection. Plasma totally stops responding and the notification window never gets filled in. Plasma is pegged at 100% CPU, running as /usr/bin/plasma --shut-up right now. Reproducible: Always Steps to Reproduce: 1. Set Oxygen Plasma theme (and turn off blur plugin?) 2. Connect to some network with NetworkManager applet. 3. Suspend to RAM 4. Resume from suspend Actual Results: Plasma totally locks up upon reconnecting to the network. Expected Results: Not having Plasma die.
Created attachment 90023 [details] Screenshot of unfilled notification window on resuming.
Plasma 4 or Plasma 5 ? Your report is contradicting here.
It's Plasma 5. What part is contradicting?
Thanks for the update. I was not sure because the Plasma 5 binary is /usr/bin/plasmashell
(In reply to Christoph Feck from comment #4) > Thanks for the update. I was not sure because the Plasma 5 binary is > /usr/bin/plasmashell I see. My apologies- I must have just mistyped it.
Can you still reproduce this? And do you know howto use gdb? It would be interesting to see where it gets stucked. If you can't use gdb, it's simple, just follow this: -open konsole and get plasma's pid (run "pidof plasmashell") -attach gdb by doing "gdb --pid nnnn" where nnnn is the pid from above -if gdb says something about not being permitted to do that, run it again as root (sudo gdb...) -gdb will do things for a bit and then will stop plasma, so type "c" into gdb and hit enter, plasma should continue -now just wait for the 100% cpu hog again -once it happens, switch to konsole running gdb and press "ctrl+c" -now type "thread apply all bt" and that gives you looooong trace -post that trace here Cheers!
Sorry for not responding for so long. I got super busy. This issue doesn't seem to happen for me with the recent update to 5.2. So... maybe it isn't an issue anymore...
I *think* I'm experiencing the same issue. I suspended my machine, resumed it, and the screen did not properly render... a lot of triangles and flashing, but nothing usable. The kcmshell5 is now running at 100% CPU. Any workarounds?
@William - your issue is likely a different one. From the original description, this looks like bug 341951 which is a bug in the graphics driver. *** This bug has been marked as a duplicate of bug 341951 ***