https://bugs.kde.org/show_bug.cgi?id=419494
--- Comment #14 from Grady <mindinsom...@gmail.com> --- This might be something to take another look at now given there's been a recent change in how KDE handles multiple monitors that may impact what has been discussed here: Information about the changes here: https://notmart.org/blog/2022/12/multi-screen/ And here: https://pointieststick.com/2022/12/16/this-week-in-kde-wayland-fractional-scaling-oh-and-we-also-fixed-multi-screen/ Quoting pointiestick.com blog post: > Fixing Multi-Screen > > Multi-screen is a complicated beast because it touches so many parts of the > software stack. Ultimately most of our problems arose from the use of > connector IDs to identify screens and map Plasma desktops and panels > (“containments”) to screens. This worked poorly, because connector IDs can > and do change under various circumstances. As a result, things often became a > scrambled mess, with the behavior either being random, or consistently wrong. > > That’s all changed. You can read the details here. In a nutshell, we now use > an index-based system, with index numbers bound very tightly to Plasma > containments, but index numbers themselves being able to move between screens > based on how many screens there are. So for example, when screen 1 with your > Plasma desktop and panel becomes unavailable, a new screen becomes screen 1, > and the Plasma desktop and panel bound move over to it. > > This new system should result in vastly greater stability, reliability, and > predictability with respect to how screens are enabled and disabled, > positioned, and what Plasma desktops and panels they show. It fixes notorious > bugs like Plasma containments being randomly moved around or lost and > desktops sometimes losing their wallpapers, widgets, and icon settings. It > also makes arrangements of screen layouts and Plasma containments stable > across the Plasma X11 and Wayland sessions. Big stuff. And quoting the notmart.org blog post: > We have a new Wayland protocol for screen ordering (as well an X11 > counterpart) for KScreen and KWin to agree to which one is the real logical > ordering of the screens, so Plasmashell will now follow this without > attempting to identify monitors by itself, removing a very big failure point. This sounds like it would fix the issue which was described by Meven of not having a consistent method of identifying which monitor is which. -- You are receiving this mail because: You are watching all bug changes.
