Created attachment 176455 [details] A screen recording of xwayland app and "native" wayland app SUMMARY While pressing right button on mouse in Xwayland apps, cursor defaults to "X" cursor (tested on VSCode, Chrome, Redis Insight, Lutris and HandBrake). Does not appear if app is running "natively" in wayland. STEPS TO REPRODUCE 1. Open app and check if it's running via Xwayland. 2. Press right click to open any menu. 3. *Observe* OBSERVED RESULT Cursor fallbacks into "X" cursor while opening menus. EXPECTED RESULT Cursor is not an ugly "X" while right clicking to open menus. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.4 GB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION Rollbacking to 6.2.1 from 6.2.4 resolves this issue.
I can't reproduce: Can you confirm that it happens straight after login and the output of: xrdb -q
❯ xrdb -q Xcursor.size: 24 Xcursor.theme: macOS-BigSur Xft.antialias: 1 Xft.dpi: 96 Xft.hinting: 1 Xft.hintstyle: hintslight Xft.rgba: none and yes, opening chrome after login and pressing right mouse button still causes this issues. It's weird because i can reproduce it on both my systems. One laptop with AMD iGPU and workstation with nvidia prop drivers. Both same theme, same kernel, same packages. I can attach konsave preset to load, I'm using custom theme if it's important. (I have tried roling back into breeze cursor, but no luck)
Note 2: I have created new account with defaults to prevent "theme contamination" and issue is still present.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Fixed in followuing kwin updates. Upgrade kwin-libs-0:6.3.2.1-1.fc41.x86_64 External User updates Upgrade kwin-common-0:6.3.2.1-1.fc41.x86_64 External User updates Upgrade kwin-wayland-0:6.3.2.1-1.fc41.x86_64 External User updates Upgrade kwin-0:6.3.2.1-1.fc41.x86_64 External User updates Replaced kwin-0:6.3.0-3.fc41.x86_64 External User @System Replaced kwin-0:6.3.1-1.fc41.x86_64 External User @System Replaced kwin-common-0:6.3.0-3.fc41.x86_64 External User @System Replaced kwin-common-0:6.3.1-1.fc41.x86_64 External User @System Replaced kwin-libs-0:6.3.0-3.fc41.x86_64 External User @System Replaced kwin-libs-0:6.3.1-1.fc41.x86_64 External User @System Replaced kwin-wayland-0:6.3.0-3.fc41.x86_64 External User @System Replaced kwin-wayland-0:6.3.1-1.fc41.x86_64 External User @System