Summary: | Software cursor disappears when moving over right or bottom screen border in Wine games | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | username <linx.system.adm> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | nate |
Priority: | NOR | Keywords: | regression |
Version: | 5.26.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/kwin/commit/5432ffb76d97f7d729e1b7dfaa8f3a724b36eac0 | Version Fixed In: | 5.27.1 |
Sentry Crash Report: |
Description
username
2022-10-29 23:40:18 UTC
Can you clarify what you mean by software cursor? The software cursor drawn by kwin or the wine game? also, can you list wine games that are affected? can you reproduce it with some free X11 apps? (In reply to Vlad Zahorodnii from comment #1) > Can you clarify what you mean by software cursor? The software cursor drawn > by kwin or the wine game? also, can you list wine games that are affected? > can you reproduce it with some free X11 apps? By software cursor I mean that KDE draws the cursor in a different way when the variable KWIN_DRM_NO_AMS=1 is enabled. I am forced to use this variable to get rid of this issue: https://gitlab.freedesktop.org/drm/amd/-/issues/1513 The issue only reproduced with Wayland. To better see the issue I recorded video: https://www.youtube.com/watch?v=J1dIrPxSANk Wine games affected: World of Warcraft, The Sims 4 I tested some free games, can't reproduce it with SuperTux2, Warsow I will try to test more games later I did some more tests Games affected: Dota 2 (native) Games unaffected: CS: GO (native), Paladins (wine) A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3572 Git commit 815269a26f234758f95a729c2323de552723639b by Xaver Hugl. Committed on 09/02/2023 at 22:35. Pushed by zamundaaa into branch 'master'. backends/drm: set cursor again after it was hidden This isn't necessary with atomic modesetting, as moving and setting are the same thing. With legacy though, if the cursor was hidden, moving it with the layer visible does not automatically show it again, so that needs to be done explicitly M +2 -1 src/backends/drm/drm_output.cpp https://invent.kde.org/plasma/kwin/commit/815269a26f234758f95a729c2323de552723639b Git commit 5432ffb76d97f7d729e1b7dfaa8f3a724b36eac0 by Xaver Hugl. Committed on 09/02/2023 at 22:59. Pushed by zamundaaa into branch 'cherry-pick-815269a2'. backends/drm: set cursor again after it was hidden This isn't necessary with atomic modesetting, as moving and setting are the same thing. With legacy though, if the cursor was hidden, moving it with the layer visible does not automatically show it again, so that needs to be done explicitly (cherry picked from commit 815269a26f234758f95a729c2323de552723639b) M +2 -1 src/backends/drm/drm_output.cpp https://invent.kde.org/plasma/kwin/commit/5432ffb76d97f7d729e1b7dfaa8f3a724b36eac0 |