https://bugs.kde.org/show_bug.cgi?id=427060
Fabian Vogt <fab...@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CONFIRMED CC| |fab...@ritter-vogt.de --- Comment #24 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to Méven Car from comment #22) > Quoting Zammundaa > https://www.reddit.com/r/kde/comments/tbr5ey/comment/i0a7ki0/ > ?utm_source=share&utm_medium=web2x&context=3 > > ``` > VMs pretend they support atomic modesetting, when they don't actually > support it properly.[...] > > You can work around it by using the environment variable KWIN_DRM_NO_AMS=1, > which forces KWin to use the legacy driver API that VMs actually handle > properly (or to be really precise, less badly) > ``` This comment blames the wrong component(s) in the stack, as it's actually the kernel which does not support specifying a cursor hotspot if AMS is used. I suggest to have KWin prefer legacy modesetting in VMs for that reason, like other compositors already do. When the necessary kernel changes are implemented (which I unfortunately don't see any sign of), this could be changed again in the future. -- You are receiving this mail because: You are watching all bug changes.