448963 2022-01-22 17:17:55 +0000 Panel disappears after turning monitors off/on 2022-01-24 19:46:32 +0000 1 1 4 Plasma plasmashell generic-multiscreen 5.23.90 Arch Linux Linux RESOLVED DUPLICATE 353975 NOR normal 1.0 0 lars aleixpol nate notmart plasma-bugs-null xglooom 0 oldest_to_newest 2096854 0 lars 2022-01-22 17:17:55 +0000 SUMMARY After turning my monitors off and back on again, the panel on one of my monitors (always the same one) is missing. Restarting plasmashell (using `plasmashell --replace`) reliably restores the missing panel. STEPS TO REPRODUCE 1. Turn monitors off. 2. Turn monitors on. OBSERVED RESULT The panel on one of my monitors is gone. EXPECTED RESULT The panels stay where they should. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics 2097062 1 nate 2022-01-23 05:58:45 +0000 I guess the targeted fix we made for this in 5.24 wasn't enough. I'm CCing Marco, who made that fix and is working on this area of Plasma. 2097083 2 xglooom 2022-01-23 07:51:14 +0000 In my case not only panel is gone, but background goes black and right click on it not work anymore. 2097234 3 lars 2022-01-23 18:42:11 +0000 (In reply to Aleksey Zagorodnikov from comment #2) > In my case not only panel is gone, but background goes black and right click > on it not work anymore. Indeed, this is also the case for me (but I hadn't noticed it yet because the desktop was covered by windows). 2097241 4 nate 2022-01-23 18:54:45 +0000 Oh, that is actually a separate issue. In that case, the panel itself didn't lost its containment mapping; the whole containment itself disappeared and a new one was not automatically created. This is Bug 371717; which I will re-open. *** This bug has been marked as a duplicate of bug 371717 *** 2097737 5 nate 2022-01-24 19:46:32 +0000 *** This bug has been marked as a duplicate of bug 353975 ***