Created attachment 183043 [details] Screenshot showing the issue described. SUMMARY Desktop is dislocated when I boot the system. It happened when I was using two monitors (one 1920x1200 and another 1920x1080), but it's worse now that I have three (added another one 1440x900). "kquitapp6 plasmashell && kstart plasmashell" fixes the issue until next boot. Issue was sporadic, but has become consistent. Marked as minor because I assume most people on multiple monitors would be using identical ones and that it happens only on different monitors. I don't have another 1920x1080 monitor to test that, though. STEPS TO REPRODUCE 1. Use multiple monitors of differing resolutions. 2. Boot up the system. OBSERVED RESULT Desktop layout is dislocated, as shown in the attachment. EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 6.4.2 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION Running X11, because Nvidia and Wayland don't mix well. On Wayland, the Nvidia Server Settings can't find out anything about the system: what system it's on, or the/how many monitors I have, nothing. Meaning I can't configure my monitors or anything graphics related. Some applications, like MangoHUD, also break.
>Desktop layout is dislocated, as shown in the attachment. Just the wallpaper, or are the screens overlapping if you open an app like dolphin. >because Nvidia and Wayland don't mix well. Is that based on recent experience or what the internet says? It should be fine. If you could test if you get this bug that would be a useful data point.
(In reply to David Edmundson from comment #1) > Just the wallpaper, or are the screens overlapping if you open an app like > dolphin. It's a bit weird, because while I can use the monitor just fine 99% of the time, sometimes an app can spawn a window "out of bounds", if that makes sense. I then have to extend it to a bigger monitor to work with it. Happens specially to peazip. If I drag a browser tab to a monitor, it also gets detached wrongly scaled depending on where it lands. > Is that based on recent experience or what the internet says? It should be > fine. > If you could test if you get this bug that would be a useful data point. Personal experience. Not to say it didn't get better, because prior to the most recent version I didn't get any display out, and now I do. Then again, the Nvidia Server Settings can't find any information about the system, and GOVerlay, when it didn't crash, was taking several minutes to save any configuration and still didn't show anything on screen whilst gaming. Those are the two reasons I even noticed I was on Wayland.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
(In reply to David Edmundson from comment #1) > Is that based on recent experience or what the internet says? It should be > fine. > If you could test if you get this bug that would be a useful data point. Ok, so I just tested again with Wayland and I couldn't make that bug happen.
I'm afraid we can't support very complex multi-monitor arrangements on X11. Wayland is the expected path for a good multi-monitor experience. If you're having problems with KDE software with the Wayland session due to your NVIDIA GPU, please open bug reports on those issues instead, so we can fix them and then you can use the Wayland session. :) And if you're having problems with 3rd-party software, please report the issues to them. Thanks for understanding!