Hi! New here. I’ve been trying a hand at this bug slowly for some time now, digging in systemsettings’ code, I didn’t get anywhere due to unfamiliarity with the codebase, I don’t know if the bug is really related to kwin as reported in the bug or just limited to systemsettings(since it’s the only place where the bug occurs AFAIK)
I wonder if anyone really familiar with the code/bug would be able to point me in the right direction or provide any kind of help, is there work already being done to address this bug?
I think I reproduce it when I launch systemsettings through krunner or plasmashell rightclick but not when using the shortcut “Meta + I” or the icon from the task manager or the menu.
So I think it might be due to how plasma launches systemsettings rather than a a bug in systemsettings. It seems the process is not started properly or something along those lines.
But I am not too sure.
As Méven mentioned, this is going to be a very difficult issue to diagnose and fix. I suspect it’ll be deep in the guts of Qt, KWin, the graphics drivers, or some interplay of the three. Not for the faint of heart.
I can’t reproduce it myself on Wayland with a single 175% scale screen, FWIW.
You are talking about he Qt quick rendering backend right (kcmshell6 kcm_qtquicksettings) ?
That’s the first this is mentioned, since you can test with and without and it shows a different behavior, the rendering API used is a determining factor.
And when it comes to OpenGL, the drivers are usually the main culprits. With vulkan the drivers do a lot less of work and let the application make better decision, like when to draw and such.
So next question would be what is your GPU and hardware kinfo. This is always when it comes to rendering and screen to mention your GPU (or APU).
