Bug 458171

Summary: Display scaling settings not used when switching from Wayland and X11
Product: [Applications] systemsettings Reporter: Iyán Méndez Veiga <me>
Component: kcm_kscreenAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella, plasma-bugs
Priority: NOR    
Version: 5.25.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Iyán Méndez Veiga 2022-08-22 14:09:12 UTC
SUMMARY
I have configured a scale of 125%. It works both in Wayland and X11, but when switching from one session to the other, the setting is not used and screen is back to 100%.

The value in the settings keep showing 125% but is not true. The only way to fix it, is move it to a different value, save, and then change it back to 125%.


STEPS TO REPRODUCE
1. Start Wayland session
2. Configure the display scale to 125%
3. Log out
4. Start X11 session
5. Log out
6. Start Wayland session

OBSERVED RESULT
Wayland uses 100% scaling, but it shows 125% in the settings.

EXPECTED RESULT
Scaling settings should work even when switching between different sessions.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.2-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: LENOVO
Product Name: 20XYCTO1WW
System Version: ThinkPad X1 Yoga Gen 6

ADDITIONAL INFORMATION
Thank you so much for all the improvements regarding Wayland. I have been using Wayland for almost have a year now and it's a great experience, specially with a touchscreen. I only have to switch back to X11 once in a while to run some things with Matlab (which crashes and freezes continuously with Wayland).
Comment 1 Iyán Méndez Veiga 2022-08-22 14:13:20 UTC
Ups, sorry about the noise. I think this is a duplicate of Bug 433460.
Comment 2 Nicolas Fella 2022-08-22 17:54:49 UTC

*** This bug has been marked as a duplicate of bug 433460 ***