But there is also a disclaimer in front of my face I did not pay attention to late night
The factual accuracy of this article or section is disputed.Tango-inaccurate.png
Reason: Is this limited to the UHD770 alone? Is this limited to the Plasma Desktop or does it also happen on every Qt application regardless of the environment? Should we not recommend uninstalling xf86-video-intel instead? Is this bug reported somewhere? (Discuss in Talk:Intel graphics)
Edit: but if it is a problem with Qt switching X11/Wayland may not solve the issue on plasma.
I think the big issue is people donāt understand how their hardware works. Then they blame the desktop because they donāt know how to get it working.
That is often true, but out of the box the users DE was not working properly in this case. But then there are difference between DE like compositors, graphic configs and qt/gtk, that may contribute. I had some odd screen flickering on cinnamon long time ago when connecting an external monitor but nothing on gnome or plasma. Itās just a pain when it occurs and not everyone has the patience trying to fix it.
Maybe useful if @pattmayne manages to try login X11 in gnome (itās just a click on login and selection on bottom right I think), then we at least can discard or not that the problem stems from X11/Wayland usage.
Hardware/driver seems to be the problem but why it works on gnome and not plasma is strange.
Actually when I log into Gnome with the Xorg option it DOES give me similar glitches as I had in KDE Plasma. So it might be a Gnome vs Wayland thing.
Iām not reinstalling Plasma just to test this all more thoroughly. I think I remember logging into KDE with both Wayland and Xorg to test it anyway, and that it didnāt solve the issue, but I might be wrong. I stayed up fairly late trying to get this to work and tried a lot of stuff. Iām enjoying Gnome now and Iāll very likely stick with it.
Iām not entirely clear how the Iris XE graphics play into this. Does Xorg use the Iris XE graphics while Wayland does not? That would be a shame since I spent a little extra money to get the Iris XE option. I wonder how many of these issues will be smoothed out in the coming months.
So for anybody reading for solutions to similar problems, I found two ways to deal with the issue. Installing Mesa on Plasma worked (see solution above) but I ultimately moved to using Gnome Wayland, which also works great without any hacks or fixes. Also this Gnome installation starts up much quicker for some reason.
Fairly new hardware takes a bit time to be smoothed out on Linux, although drivers are still getting out pretty quickly and arch based distro is great to have these rolling in asap.
Was just having this same issue on my 2022 LG Gram 16 which i am currently trialing eos on, using the modesetting driver fix as per the arch wiki currently because using mesa-amber was causing me to fallback to software rendering. Using wayland sessions for both plasma and gnome worked just fine, issue only exists with X11, Hoping there is a proper fix for X11 in the works before i make the jump. Using wayland is kinda off the table because it still cannot fractional scale and on a 16" 2560x1600 panel thatās basically necessary.
Yeah thatās a drawback in Gnome Wayland. I have the same resolution and I can only do 100% or 200%. There is a hack to do fractional scaling but itās just blurry.
So youāre saying that KDE Plasma Wayland also does not support fractional scaling?
It does and as of 5.26 xwayland apps finally scale right. However it still isnāt perfect, all text appears very slightly fuzzy. Much better time than gnome though.
Sighā¦ maybe Iāll have to reinstall KDE. Most accounts say there arenāt major compatibility issues. Gnome is beautiful and I actually love the interface, but everything is so tiny without fractional scaling.
Maybe, would be good to know if KDE Wayland can scale laptop and external monitor with different resolution with two different scaling factors. It seems to work pretty well on gnome Wayland. I never tried KDE Wayland as of yet.
Note: GTK does not and has no plans to support DPI scaling on all elements except fonts. Therefore, fractional scaling on gnome uses oversampling, which means rendering at a higher resolution, then scaling down with integer scaling, and is true for both wayland and xorg sessions. This brings higher GPU and CPU (since GTK is not fully hardware accelerated) usage, more power consumption, and in some cases significantly slower responsiveness, particularly noticeable in xorg. If itās necessary to avoid these problems, consider switching to a Qt based desktop environment.
Experimental features. This is the code for Wayland (which I tried, and it worked, but it was blurry):
sudo gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
And this is the one for Xorg (which I havenāt tried yet because Xorg has been buggyā¦ except when I installed Mesa-Amber on my first installation of Endeavorā¦ might have to do that again and see if Xorg scaling is really better):
gsettings set org.gnome.mutter experimental-features "['x11-randr-fractional-scaling']"
I found them both on this site:
I should also mention that Iām now running both Gnome and KDE Plasma, each with both Xorg and Wayland functionality. In each case the Xorg is glitchy and the Wayland runs smooth, but thereās no fractional scaling at all, and Gnome runs much smoother. But I had it freeze twice and had to restart it. So many bugs with this new machine lol.
My original plan was to proceed with a light touch toward hacks. Iām going the opposite direction now. I need to throw everything at this machine until something works, and then possibly reinstall everything again with that fresh knowledge. Installing for the 3rd time wonāt hurt my SSD card.
Iām going to do the mesa-amber install again AND the xorg scaling hack to see how it looks in Gnome.
Looks like those are the same hacks that gave me the blurry images on Wayland. And if theyāre a resource hog then I donāt want it, even if the Xorg version is less blurry
