Summary: | Glitching cursor and screen content in applications in full screen when using a fractional scaling factor | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Hexagon <apricus> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | 6ot3tjpxk, evanc577, nate, xaver.hugl |
Priority: | NOR | ||
Version First Reported In: | 5.27.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Hexagon
2023-03-02 23:00:42 UTC
I'm having the same problem, but only for scaling factors below 150%. This might be because it's my secondary 1080p monitor and my primary 4K monitor is set to 200% scale. The problem also happens in Chromium browsers, but not consistently, and only after the "press Esc to exit fullscreen" popup has disappeared. This is happening for me as well on 2 machines, one with 4k 150% scaling and the other 1080p 125% scaling I just discovered that this does not only happen on YouTube, but every website triggering the "full screen" function of Firefox which is not the same as pressing F11. When using F11 the problem is not there. The fullscreen function of the browser can be called by JavaScript and Firefox presents a banner on the top on enabling stating "my.site.com is now full screen. Exit Full Screen (ESC)". It is probably this: docElm.mozRequestFullScreen(); https://hacks.mozilla.org/2012/01/using-the-fullscreen-api-in-web-browsers/ I just discovered, that it does not only occur in Firefox but other applications too and seems to be a general problem of KWin, therefore I changed the ticket title. It also happens on Signal. To reproduce it there send a video into a chat and start playback of it, enter fullscreen playback and move the mouse. You see the same glitches and mouse cursor size changes as in Firefox playing a YouTube video. New info of a chat with a KWin developer: The problem started after "Direct Scanout" was implemented in KDE Plasma 5.27 released on 2023-02-14. Workaround: One can disable the "Direct Scanout" using the environment variable "KWIN_DRM_NO_DIRECT_SCANOUT=1" in /etc/environment and relogging / restarting the computer. The problem should go away. Afaik this has been fixed in amdgpu, with https://patchwork.freedesktop.org/patch/557059/ |