Created attachment 145322 [details] Odd behaviour SUMMARY Sometimes after having logged in successfully, the Desktop is not restored/initialized successfully. The Plasma session is still functional, startup apps are loaded as expected and other applications still seem to work fine. The login screen is not affected. To resolve the behaviour, I have to shutdown my computer and start it again. A simple reboot has no effect (the observed behaviour remains the same) STEPS TO REPRODUCE I have not yet found any chance to reporduce this behaviour intentionally. It just happens every once in a while. Today, it happened after having restarted my laptop after an Kernel Update via Discover app. OBSERVED RESULT * Instead of my wallpaper image, I have a black screen * my notification banners appear in the center of the screen instead of on the upper right * no context menu (right klick) on the desktop available * no files on my desktop are visible (simply empty) Neither logging out and in again nor a reboot solves the issue (it remains the same everytime I log in). Only a complete shutdown and restarting solves the issue. System log and kernel log do not show any errors/warnings. EXPECTED RESULT * Wallpaper displayed * notifications at the top right * context menu on the desktop available * display files on my desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Graphics Platform: X11
Created attachment 145323 [details] Sample "correct" behaviour
How many screens does your setup have? Just one ore more than one?
(In reply to Nate Graham from comment #2) > How many screens does your setup have? Just one ore more than one? Usually it is two (Laptop + external; external is the mirror of the laptop display; hdmi port) However, as far as I can remember, it does also occur if the monitor is not connected at all (no capble plugged into the laptop)
Thanks. *** This bug has been marked as a duplicate of bug 371717 ***
*** This bug has been marked as a duplicate of bug 353975 ***