SUMMARY After waking up from screen saver, panels on second screen go all wonky. Either disappear, or an included task manager shows up tasks from the wrong screen. Restarting plasmashell then "fixes" it STEPS TO REPRODUCE 1. On second screen, set up a panel with a task manager with "Show only tasks from the current screen" is ticked. 2. At first, it does indeed only show tasks from the second screen, as it should 3. Wait 10 minutes for the screen saver to kick in 4. Move the mouse to wake it from screen. 5. Now, the task manager in the panel on the second screen shows tasks from the *first* screen. Sometimes, that panel is also gone altogether (i.e. not displayed at all) 6. Execute kquitapp plasmashell ; nohup plasmashell >/dev/null 2>&1 </dev/null & 7. Now, everything is back to normal OBSERVED RESULT After wakeup, task manager in the panel on the second screen shows tasks from the *first* screen. Sometimes, that panel is also gone altogether (i.e. not displayed at all). Things get back to normal only after restarting plasmashell EXPECTED RESULT The task manager should display the tasks from the screen it is on, and not from some other screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Where is "About System"? (Full path...) (available in About System) KDE Plasma Version: 4:5.14.5.1-1 KDE Frameworks Version: what is the name of the package? Qt Version: 5.11.3+dfsg1-1+deb10u3 ADDITIONAL INFORMATION
Some addition: Before the bug first appeared, I had replaced my screens. The new ones are both connected via DisplayPort, whereas the old ones used to be connected one via HDMI and one via DisplayPort. This left the following situation in my ~/.config/plasmashellrc [ScreenConnectors] 0=DP-2 1=eDP-1 2=HDMI-3 3=DP-1 4=HDMI-2 5=:0.0 I now cleaned this out from a text console while not being logged in KDE, to leave this: [ScreenConnectors] 0=DP-2 1=DP-1 2=:0.0 ... an now the problem no longer occurs (touching wood...)
More comments about this on bug 416739. Unfortunately I was mistaken in my comment from 2020-09-13 : the problem only went away for a while, but now occurs again. Copying the config files from a backup from when it was working did not help this time :-(
*** This bug has been marked as a duplicate of bug 416739 ***
*** This bug has been marked as a duplicate of bug 427278 ***