Bug 474203

Summary: Wayland session does not save scaling or the monitors' order
Product: [Plasma] KScreen Reporter: Kalzi <kalzwayed>
Component: commonAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR Keywords: multiscreen, wayland-only
Version First Reported In: 5.27.7   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Kalzi 2023-09-06 01:06:39 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Have two 4k monitors 
2. Log into wayland
3. Change the scaling to 175% or 200% or whatever works for you.
4. Log out and log back in

OBSERVED RESULT
Scaling goes back to 100% after logging out then logging back in and the monitors' order resets and the mouse does not move across the screens as it should

EXPECTED RESULT
Scaling saves to whatever I set it to, even after a log out/log in or a reboot

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: EndeavourOS
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
I have two 27" 4k monitors. A dell to my right and a sceptre to my left. I set the scaling to 175% on both. also I have the Dell as my primary that is sitting to my right and also I have it to the right in the settings, too. Eevery time I log out or reboot, that order resets. The dell moves to the left in the settings and the other monitor goes to the right. Scaling goes back to 100%. Also, the Sceptre becomes the primary. And this happens every signle time. I have even reinsalled the whole system thinking it would fix it, it didn't.
Comment 1 Nate Graham 2023-09-06 19:15:20 UTC 
If you move aside (Don't delete!) your ~/.local/share/kscreen folder, re-create the layout on System Settings' Display & Monitor page, and then reboot, does the problem go away, or does it still happen?
Comment 2 Bug Janitor Service 2023-09-21 03:46:13 UTC 
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!
Comment 3 Bug Janitor Service 2023-10-06 03:46:30 UTC 
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!