This one drove me completely nuts until I saw the git commits regarding the changes to containment filtering and lastScreen. This appeared in both the 5.8 and 5.9 series when the related commits were applied tho I cannot find which that are. Currently I have to use the following script to fix this after it happend on (almost any) reboot: #!/bin/bash kquitapp5 plasmashell sed -i 's/^lastScreen=.*/lastScreen=0/' $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc kstart5 plasmashell I'm not sure why plasma inserts lastScreen=1 or sometimes even lastScreen=-1 into the config file. I have to monitors attached but I only use clone mode as in: go to kscreen systemsettings, click the button to unify displays.
can you paste ~/.config/plasma-org.kde.plasma.desktop-appletsrc?
Created attachment 104624 [details] affected config file Sure, here it is... I didn't try to reproduce it reliably but it seems that the config is broken after running fullscreen games through Steam (native, not Wine).
indeed wrong.. is the system multimonitor? perhaps a second screen that has been attached and detached in the past?
Well, it's sort of a multi monitor system. Indeed, it has two monitors always attached. The first one is my standard PC monitor for working with the system (via DVI). The second one is my TV for watching movies or playing games in "couch mode" (via HDMI). Usually, I never disconnect the TV but I may have done so a few times in the past to instead connect a Raspberry Pi to the TV. Since I use this as a single monitor system because I cannot sit in two places at once, both screens are configured in clone mode via system settings (unify screens, or in German "Anzeigen vereinheitlichen"). Since disconnecting the TV, I have recreated the plasma config from scratch multiple times because I had problems with some widgets freezing plasma. So I unwillingly ditched the config multiple times. Even when I first hit this problem, I recreated the config by starting up with the defaults and recreating my particular setup from scratch. Only to see this happen again after a few reboots. At last, I found to fix this by setting lastScreen=0.
Thanks for the report Kai. I'm unable to reproduce this issue on Plasma from git master. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
I can still reproduce it on a real 2-monitor system at work: After an update to Plasma 5.20, one panel was gone, the other moved over to the second monitor. When I switch between Wayland session and X11 session, I can reproduce that behavior. I didn't yet confirm this behavior: In the office, someone disconnected one monitor from my workstation while a Wayland session was running. When I returned to the office later with the monitor already reconnected, both monitors seemed to have swapped places, and one panel was gone. Meanwhile, on the original system, I had no more problems: The configuration has been stable there for a while now. But I cannot use Wayland there, only X11. So I cannot confirm if the issue still exists on that system.
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!
New information was added with comment 6; changing status for inspection.
This might be related: https://bugs.kde.org/show_bug.cgi?id=416739
*** This bug has been marked as a duplicate of bug 356225 ***
*** This bug has been marked as a duplicate of bug 356727 ***