Hello there, As the title suggests, the mouse does not move/respond while playing Helldivers 2 through Steam with either Plasma 6.0.0 or 6.0.1 via Wayland. What's interesting is that if I go into the menu, the mouse cursor moves and I can interact with the options.....but the moment I start playing and moving my character, mouse look doesn't work...but mouse buttons do. Apparently, a few others are experiencing the same issue. https://old.reddit.com/r/linux_gaming/comments/1b89iu8/kde_plasma_6_helldivers_2_broken_mouselook/ https://old.reddit.com/r/linux_gaming/comments/1bahzh0/cant_look_around_in_games_after_recent_kde_plasma/ As those threads suggest, using gamescope or running Plasma via X11 are the only workarounds at the moment. Some have mentioned that other games are affected but Helldivers 2 is the only one that I have encountered with this issue so far. Everything works fine with Plasma 5.27 via Wayland. STEPS TO REPRODUCE 1. Run KDE Plasma 6.0.0/6.0.1 via Wayland 2. Launch Helldivers 2 3. Test if mouse look works while moving the playable character. OBSERVED RESULT When in-game and controlling the main character, mouse look stops working...but mouse buttons work (almost as if the mouse is stuck). EXPECTED RESULT Mouse look should work. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD Radeon RX 6800M Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G513QY System Version: 1.0 ADDITIONAL INFORMATION If there's any further data/information I can help with, please let me know.
Looking through the bug reports, it's likely this issue is as described in this report: https://bugs.kde.org/show_bug.cgi?id=482629 Alt+Tabbing sometimes gets it to work but it's random/inconsistent that it will work and eventually it happens again. My main mouse is a Logitech G502...tested with another mouse but the results is the same.
*** This bug has been marked as a duplicate of bug 482629 ***
The issue seems to be resolved after upgrading to 6.0.3.