STEPS TO REPRODUCE 1. Update to latest KDE Git via kdesrc-build 2. Backup and / or delete ~/.cache/ 3. Fully restart KWin Wayland by logging out and logging back in OBSERVED RESULT Cursor does not change correctly in response to hovering over particular GUI elements. For example, when hovering over click-and-drag resizable elements, the cursor will not become what it becomes in X11, but turn into a normal pointer that is misaligned to the element it is hovering over. As soon as the element isn't being hovered over, the cursor shifts back to normal. Same result when hovering over editable text box elements. Cursor sometimes shifts bizarrely from state to state when changing the GUI element being hovered over. Will try to capture a video, but don't know how to do so in a Wayland session right now, alas. EXPECTED RESULT Cursor should act in a KWin Wayland session as it does in an KWin X11 session. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-arch1-1-custom-bcachefs-git-01580-g5a6bf64b47f4 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B85 System Version: 1.0 ADDITIONAL INFORMATION
https://invent.kde.org/-/snippets/2376 for KWin Support Information
*** This bug has been marked as a duplicate of bug 458865 ***
(In reply to Antonio Rojas from comment #2) > > *** This bug has been marked as a duplicate of bug 458865 *** Hi, Antonio ~ this doesn't appear to be related to said linked bug, as it happens in basically all applications for me, regardless of what it is, regardless of whether said application is using Portals or not. It's a consistent cursor-based bug that happens in Firefox, Libreoffice, Dolphin, etc, and so on, and only on KWin Wayland.
This is a Mesa bug: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7351
(In reply to Zamundaaa from comment #4) > This is a Mesa bug: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7351 Many thanks! :)