Created attachment 154851 [details] Desired layout I have a 4 monitors layout. Yesterday I rebuilt my desk, slightly switching my layout (right monitor swapped with the left one, and flipped one of the monitors that was vertical). Unfortunately it looks like I am unable to persist those changes in the latest KDE+Plasma. It always reverts to the layout from before redoing my desk. STEPS TO REPRODUCE Unfortunately I do not know how to reproduce it on another machine since I only have one PC with multiple monitors 1. Have a monitor layout such as the one in the attachment 1. Restart PC or leave PC running long enough for power saving to kick in and turn off monitors 2. KScreen2 service is disabled (not sure if related, but it was preventing power saving from kicking in - it's another issue) 3. Log back into Plasma OBSERVED RESULT Monitor layout is not saved, it is reset to a layout from Plasma <5.26 EXPECTED RESULT Monitor layout to be saved SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest openSUSE tumbleweed (as of 12/27/22) (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: not sure how to check Qt Version: 5.15.7 ADDITIONAL INFORMATION Using Wayland
Created attachment 154853 [details] Reverts to this one
This should be fixed in Plasma 5.27.
(In reply to Nate Graham from comment #2) > This should be fixed in Plasma 5.27. Thank you Nate. I am going crazy from having to reset the config for all 4 monitors every time I come back to the PC. I had the temptation to disable all power saving features just to make sure I don't have to do it. :) Looking forward to 5.27 and thank you for a quick fix.
Nate, I installed Plasma and all related components from an openSUSE repo KDE:Unstable. The version I have is "5.26.80git.20230114T174945~0e72dcb9-ku.127.1". I can see the new UI with "Change Screen priorities". Unfortunately the display layout is not getting saved as it reverts back after unlocking my screen after longer inactivity or after logging back in after a reboot.
Darn. Is that different from what was happening before, or the same issue?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
> Darn. Is that different from what was happening before, or the same issue? My monitor layout is still not getting saved. It keeps resetting to a state it once saved after each time my monitors go into standby. I did a test of clearing all KDE/Plasma configs and starting with a fresh account. The issue was the same but I had to do the whole layout each time vs just a few adjustments. It is super annoying as I have to fix my monitor layout multiple times a day. Any time I go AFK and my monitors go into standby. I am happy to jump on to a debugging session or provide any info.
Nate, where does KWin store display configuration these days? All of my `.local/share/kscreen` files are from 2022.
Should be still there. If you move aside that folder, it should be re-created with new files. Maybe you can try that? It's possible the files are stale and aren't being updated for some reason.
I had a similar problem with my settings not being saved. My `.local/share/kscreen` files weren't updating either. As a workaround, I created a new local user, configured my screens there, and copied that user's `.local/share/kscreen` files to my account (and fixed ownership of the files) as a workaround to make my laptop usable. I see you mentioned trying it on a fresh account without success though. By chance, today I noticed my `KScreen 2` background service wasn't running. I enabled it and changed my screen configuration, and my `.local/share/kscreen` files updated. Stopping the service stopped the files from being updated, so the two are connected. You'd mentioned disabling that service due to a different problem, but have you tried temporarily enabling it while saving your screen configuration settings?
Aha, makes sense. Damian, can you verify that the "Kscreen2" service is running, and if not, turn it back on?
Jackpot! Steve, great deduction! That was it. I originally had to disable the KScreen service due to my monitors not wanting to stay in standby. Now that I'm on Wayland possibly the original issue with standby will go away. Once that I re-enabled the KScreen service, my settings started saving again. I am not sure why trying on a fresh user would not work earlier, possibly it was another issue which was independently fixed. Really happy to close this ticket now. Thank you Steve & Nate. PS. In light of this issue, I am not sure if ability to fully disable the KScreen service is such a blessing! Perhaps there could be a warning in the display settings?
Oh good. :) Yes, being able to disable KScreen is a mixed blessing for sure. Perhaps we should prohibit that.
(In reply to Nate Graham from comment #14) > Oh good. :) > > Yes, being able to disable KScreen is a mixed blessing for sure. Perhaps we > should prohibit that. Maybe, but look at the reason on why they turned it off. And I just found somebody else on r/kde who did it for the same reason. So maybe that if this happens it should only happen after that bug is fixed.