Created attachment 160815 [details] Journalctl on a live session SUMMARY If you go to System Settings on an X11 session on Plasma 6 and change the scaling nothing happens. I' This is what journalctl outputs when trying to change scale factors (full log will be attached. Ps: It's from a live session): Aug 07 22:33:48 neon kded6[1920]: g_settings_set_value: key 'scaling-factor' in 'org.gnome.desktop.interface' expects type 'u', but a GVariant of type 'i' was given Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: XRandR::setConfig Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Requested screen size is QSize(1920, 1080) Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Needed CRTCs: 1 Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Actions to perform: Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: Priorities: false Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Change Screen Size: false Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Disable outputs: false Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Change outputs: false Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: Enable outputs: false Aug 07 22:33:48 neon kscreen_backend_launcher[2088]: kscreen.xrandr: XRandR::setConfig done! Aug 07 22:33:48 neon kded6[1967]: xsettingsd: Reloading configuration Aug 07 22:33:48 neon kded6[1967]: xsettingsd: Loaded 13 settings from /home/neon/.config/xsettingsd/xsettingsd.conf Aug 07 22:33:48 neon kded6[1967]: xsettingsd: Reloading configuration Aug 07 22:33:48 neon kded6[1967]: xsettingsd: Loaded 13 settings from /home/neon/.config/xsettingsd/xsettingsd.conf Aug 07 22:33:49 neon kded6[1967]: xsettingsd: Reloading configuration Aug 07 22:33:49 neon kded6[1967]: xsettingsd: Loaded 13 settings from /home/neon/.config/xsettingsd/xsettingsd.conf STEPS TO REPRODUCE 1. Login on an X11 session 2. Change scale factor OBSERVED RESULT Nothing happens EXPECTED RESULT Scale changes SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 5.19.0-50-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series
On X11 you need to log out and then log in again for any scaling to take effect.
(In reply to Zamundaaa from comment #1) > On X11 you need to log out and then log in again for any scaling to take > effect. You're right, I didn't realize that. I should've tested this in Plasma 5 as well before reporting, because the behavior is the same. In that case this should be considered an UX issue with System Settings. It probably should show a message telling the user they need to restart the session or the computer for changes to take effect, otherwise it looks like nothing happened.
KScreen already tells you to do that and gives you a button to directly reboot. Perhaps it's broken in Plasma 6 though?
Created attachment 160869 [details] No feedback on Plasma 5 and 6 The behavior is the same between Plasma 5.27.7 and Plasma 6. There's no feedback on X11. I noticed that on Wayland it usually shows the "revert in x seconds" dialog, but not on X.
(In reply to Zamundaaa from comment #3) > KScreen already tells you to do that and gives you a button to directly > reboot. Perhaps it's broken in Plasma 6 though? I tested on Wayland now (on 5.27.7) and after confirming the "revert in x seconds" confirmation dialog there's no message telling to reboot. At least the screen changes scale immediately there even though it's blurry, so there's at least some feedback, on X there's nothing.
There's supposed to be a message on X11, so it looks like it broke. On a cursory glance at the code, I can see two possible explanations: 1. the scaleChanged() signal is not being emitted or handled correctly. 2. the changed() signal is firing right after scaleChanged is emitted, which causes all of the messages to disappear. The screen recording points me in the direction of #2, since it seems like something appears at the top of the window for a brief moment and then immediately disappears. My motivation to fix X11-only bugs is starting to wane, though. :)