Created attachment 145969 [details]
Shell you got after Login in (check the Clock/Activities applet).
On a 4k monitor with scale set to 200%, the first shell you get after you log has blurry text (dpi issues) for a number of Qt apps and widgets
STEPS TO REPRODUCE
1. Have a 4K monitor scaled to 200% (Nvidia proprietary driver).
2. Do a fresh login into a Wayland plasma session.
A number of Qt apps and widgets (like the Digital clock text applet and the Activities applet) have blurry text (see screenshot attached. Restarting the plasma shell seems to fix this issue (screenshot attached).
The dpi scaling for text should work on the shell you got after login in.
Linux/KDE Plasma: Plasma master (Wayland session)
KDE Plasma Version: 5.23.90 master
KDE Frameworks Version: 5.91 master
Qt Version: 5.15.2
Video Driver: nvidia 495.46, egl-wayland 2:1.1.9
Created attachment 145971 [details]
Shell you got after restarting the plasma (check the Clock/Activities applet).
kquitapp5 plasmashell && kstart5 plasmashell
Can reproduce. For me, this started happening with 100% reproducibility after d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 in plasma workspace.
Seems related to Bug 433416.
This is not a duplicate of Bug 433416 since that concerns a Qt issue that happens when the scale is changed.
In this bug, the scale is not changed; it was already set to some value in the KCM. If we're triggering the same Qt issue brought up in Bug 433416 because the implementation causes the scale to change during login, that's something we should fix independently of the Qt bug. There's no reason for the scale to change on login when it's already been set.
FWIW I also experience this blurriness on login with the whole taskbar, not only the clock.
@Nate I'm pretty sure this bug and https://bugs.kde.org/show_bug.cgi?id=447732 are related.
Good catch, you're right.
So it seems like the re-scale on login triggers https://bugreports.qt.io/browse/QTBUG-78327, which is the cause of the blurriness.
That Qt bug should certainly be fixed, but the re-scale on login is the wrong thing to do anyway, especially if it also causes the issue you're seeing in 447732, which would not be fixed by fixing that Qt bug.
*** Bug 447732 has been marked as a duplicate of this bug. ***
> That Qt bug should certainly be fixed, but the re-scale on login is the wrong thing to do anyway, especially if it also causes the issue you're seeing in 447732, which would not be fixed by fixing that Qt bug.
from what I can tell, the nvidia driver doesn't expose the edid, so kwin reads wrong output configuration (or doesn't apply any at all). there's nothing that we can do.
can you report this issue(the nvidia driver not exposing EDID) to nvidia developers?
This is not NVIDIA-specific. I and several others affected have Intel iGPUs and no NVIDIA hardware.
*** Bug 449321 has been marked as a duplicate of this bug. ***
I was able to reproduce bug 449321, which might be related.
The KCM saves changes to ~/.local/share/kscreen/control/configs/<hash of outputs>, which are at some point read by the KDED module, applied and the resulting config saved to ~/.local/share/kscreen/<hash of outputs>. On startup, kwin_wayland reads the latter, if it exists.
This is an issue if first a configuration in the wayland session is created with e.g. 125% scale, but later on an X11 session started again. Once the KDED module notices a change (manual or automatic, but not sure about the latter), it immediately overwrites the ~/.local/share/kscreen/<hash of outputs> file created in the wayland session, but with "scale": 1 because the xrandr backend does not support per-output scaling. The result is that on the next start of kwin_wayland, a 100% scale is applied initially.
If rm -r ~/.local/share/kscreen and recreating the config in the wayland session helps, then this is probably the same as bug 449321. If not, this bug is most likely a different issue. Unfortunately there's no logging of what kwin_wayland does on startup.
> Can reproduce. For me, this started happening with 100% reproducibility after d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 in plasma workspace.
That should not influence Wayland applications, but I guess it changed the startup sequence just enough for a race condition to have a different outcome.
Yes, that makes sense.
(In reply to Nate Graham from comment #10)
> This is not NVIDIA-specific. I and several others affected have Intel iGPUs
> and no NVIDIA hardware.
qt handles changing scale poorly, I don't see what we can do in kwin to fix the blurriness. with nvidia it's easier to reproduce because kwin can't load the right output config at startup, so it sticks with a scale factor of 1
> I don't see what we can do in kwin to fix the blurriness.
We could not unnecessarily change scale on login, or if we have to, we would do it much earlier in the login process so that the scale is already set correctly by the time GUI software launches. I guess that would be a Plasma thing, so I'll move this back there.
For me, all of this started happening after https://invent.kde.org/plasma/plasma-workspace/-/commit/d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 was committed.
Created attachment 146428 [details]
FWIW this probably causes at least as much harm as it fixes:
1. Breaks desktop wallpaper - variety's quotes are "right-alligned", even some of them go out of the right corner and not all of them can be seen.
Created attachment 146430 [details]
2. Wrongly-alligned notifications
Created attachment 146431 [details]
Wrongly-alligned settings upon opening
3. Wrongly-alligned settings upon opening
(In reply to Lyubomir from comment #19)
> Created attachment 146431 [details]
> Wrongly-alligned settings upon opening
> 3. Wrongly-alligned settings upon opening
I have to say that Plasma 5.24 fixes the location of the windows and i'm very impressed by the new **smoothness**. Rocks!
I don't know if this is related but global scale on Wayland in Plasma 5.24 is broken for me.
This is when using 4k screen with 200% scaling and amdgpu.
Behaviour: after restart desktop session is displayed in 100% even though global scale is still set to 200%.
*** Bug 451083 has been marked as a duplicate of this bug. ***
*** Bug 451234 has been marked as a duplicate of this bug. ***
*** Bug 451259 has been marked as a duplicate of this bug. ***
*** Bug 452931 has been marked as a duplicate of this bug. ***
On my laptop i think this doesn't happen anymore. Even the splash screen is not blurry. It seems that it re-scales right before the Splash Screen appears... Have you fixed this?
(In reply to Nate Graham from comment #2)
> Can reproduce. For me, this started happening with 100% reproducibility
> after d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 in plasma workspace.
> Seems related to Bug 433416.
@Lyubomir reports the issue fixed for him/her. Can you confirm (or deny :-) that it's fixed for you as well?
It's fixed for me too with current git master. I would suspect it got fixed with the fix for a systemd boot race condition recently, which made it into Plasma 5.25.2.
I'm still on 5.25.1 LOL... the real programmer question: "But why does it work now???" /s
It might have been fixed in 5.25.1; I can't 100% remember right now
This bug as described in Bug 451259 is still present for me on Plasma 5.25.2
Hmm, then that must be a separate issue. I can't reproduce it FWIW.