Summary: | Mouse cursor stuck in top-left corner in some fullscreen games on Wayland | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | hazelnot <hazelnot> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | david.esotica, dbekatli, kde, lolqweety, nate |
Priority: | NOR | Keywords: | qt6, wayland-only |
Version First Reported In: | 6.0.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
hazelnot
2024-03-10 16:53:01 UTC
The issue seems to have been resolved, either by 6.0.2 or by a different package update that got pushed in the meantime. I'm still encountering the same issue with Doom Eternal on Plasma 6.0.2. The cursor gets stuck at the top left corner and can't be moved. The cursor works without issues when the Steam overlay is opened but not in the game. I also use two monitors in case it matters. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Yup, this is once again happening to me as well, after about a week of not having this issue anymore. Seems almost random. I just discovered that this might be related to focus loss. I managed to regain control of the pointer in one of the affected games by tabbing out and then tabbing back in. I encountered similar focus loss issues in other programs as well when using Wayland, sometimes clicking on the window or the icon in the task manager doesn't fully focus it, and alt-tabbing is needed. as @hazelnot mentioned it is probably related to focus loss indeed. I saw people mentioning that running games with gamescope may work as an temporary fix and I can confirm that. Sadly the alt tab method is very random and unconsistent for me. I can confirm that this is happening to me on Nobara, KDE 6.0.2 in Warhammer III. Also happened in Red Alert II. I've experimented with gamescope and it appears somewhat resolved. *** This bug has been marked as a duplicate of bug 452188 *** |