SUMMARY A few days ago, my laptop upgraded to KDE Neon 5.16, and the system became surprisingly unstable after waking-up from suspension with dozens of system-wide issues affecting usability (I'm almost certain this has something to do with a re-written notifications system). STEPS TO REPRODUCE 1. Suspend system to RAM. 2. Wake system up. OBSERVED RESULT A variety of system-wide bugs happen all at once: 1. All application icons are now missing from tray. This affects layout indicator and every application that usually puts itself on the tray (for instance, messengers, like Telegram, Skype etc). However, system tray icons, like network manager, clipboard, battery, volume are still displayed. 2. Many global shortcuts stop working, for instance: - Ctrl+Alt+T to bring up terminal (does nothing) - PrintScreen, Ctrl+PrintScreen etc (appears to have no effect) - CapsLock, which is configured to switch keyboard layout on my system (simply triggers CapsLock key) However, Ctrl+Alt+L to lock screen still works. 3. As the result of the bug above, switching keyboard layout no longer works. There is also no way to switch layout manually, since layout indicator is missing from the tray. Any attempt to change/update options for switching layouts has no effect. System starts functioning normally after reboot. There was one time this buggy state resolved spontaneously after a while: a lot of delayed notifications popped up at once, missing icons appeared and global shortcuts started functioning. I couldn't, however, reproduce this "self-cure" behaviour anytime later. WORKARROUND It took me a while to figure a working workaround for this one. Simply replacing the window manager (kwin) cannot recover system from this buggy state (the bugs always persist). The only workaround I figured out so far is to replace plasmashell itself: $ plasmashell --replace & This is why I'm putting this bug under "plasmashell" section. SOFTWARE/OS VERSIONS OS: KDE neon 5.16 Kernel: x86_64 Linux 4.18.0-21-generic Uptime: 1d 1h 52m Packages: 2969 Shell: bash 4.4.19 Resolution: 3280x1248 DE: KDE 5.59.0 / Plasma 5.16.0 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: breeze Font: Noto Sans Regular CPU: Intel Core i7-6700HQ @ 8x 3.5GHz [56.0°C] GPU: GeForce GTX 950M
So all the issues go away if you just restart plasmashell? Do they return when the computer is restarted?
(In reply to Nate Graham from comment #1) > So all the issues go away if you just restart plasmashell? Do they return > when the computer is restarted? No, I've never (yet) seen this happen after a fresh boot. But all the described issues *always* occur after suspension (without exceptions). At first, I thought it could be (somehow) Compositor-related, because I used to have several glitches and regressions on KDE with NVidia drivers, but switching rendering backend between XRender and OpenGL has no effect. UPDATE: I've also discovered, the very same behavior occurs when switching between TTY and desktop session. For precisely, once you use Ctrl+Alt+F2/F3/.. to switch to TTY, then Ctrl+Alt+F1 to return to the desktop session, all of the described bugs also occur. (P.S.: The screen appears normal for a split second, then it re-renders and all the application tray icons vanish, meaning the system already entered this "buggy" state with no). P.S.: I cannot see any related errors in system journals after this starts to happen. However, when plasmashell is restarted (via --replace flag), I can cleary these lines among the others: org.kde.kded5[4544]: Imported file "/usr/share/khotkeys/kde32b1.khotkeys" org.kde.kded5[4544]: Imported file "/usr/share/khotkeys/konsole.khotkeys" org.kde.kded5[4544]: Imported file "/usr/share/khotkeys/defaults.khotkeys" <...> org.kde.kded5[4544]: Registering "org.kde.StatusNotifierHost-2455" as system tray This components may in fact be responsible. Could it be that it doesn't restore or restart properly after recovering from suspension/TTY?
Sorry for not responding. :( Sadly without a reproducible case, there's not much we can do here. Did it ever happen again?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Nate Graham from comment #3) > Sorry for not responding. :( > > Sadly without a reproducible case, there's not much we can do here. Did it > ever happen again? No problem! That bug was reproducing consistently upon waking up after suspension, as mentioned in the original report. However, after next major version update (I think, from 5.17.x onwards, but it's hard to remember already) the issue was no longer there and waking up functioned normally. I think, this bug can be closed now.
OK great! Let's call it fixed. :)