Created attachment 152793 [details] journalctl output SUMMARY I have a dual monitor setup (1 DP monitor and 1 hdmi TV) where only 1 screen is on as default. When I turn on second monitor (TV) and ask plasma to switch primary out to second monitor (TV) and turn off the primary out (DP) -- I use the Display Configuration Widget for this --, the wallpaper changes (becomes the wallpaper of the secondary monitor I use when both are on) and the widgets that are placed on the primary monitor disappear. I also noted that if at login the secondary monitor (TV) is turned on, KDE does not see it (I cannot switch output) and the desktop is shown only on the primary monitor (default behavior) To get KDE to 'see' the TV I have to turn it off and on again The above was not happening with latest 5.25.5 All above using wayland below output of journalctl when trying to switch output from DP to hdmi (TV turned on and I want to see the desktop on TV and DP off) My system as below (Archlinux with latest KDE& Plasma) Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6800
Note that in order to get back the primary monitor default layout I need to logout and login again (aka correct wallpaper and plasma widget on desktop) Nothing else works
*** This bug has been marked as a duplicate of bug 385135 ***
Hi, note that the switching of layout (primary to secondary) happens also when: * only one monitor is on * monitor goes in (screen) power saving and turns off * system is woken from screen power saving by end user. Tthe end-user is presented with secondary monitor wallpaper, primary monitor plasma widgets are gone and there is no way to get them back: Ticking and un-ticking 'primary' option in System Settings->Display amd Monitor achieve nothings This bug is actually a duplicate of bug: https://bugs.kde.org/show_bug.cgi?id=458847 that was supposed to be fixed in 5.26.0