Proton losing mouse capture on mutil montior setups
I think that’s a Wayland/Gnome issue (i could 100% be wrong) but the work around is force locking your mouse using gamescope eg below.
gamescope -W 2560 -H 1440 -w 2560 -h 1440 --force-grab-cursor -- %command%
I've had the same issue with state of decay 2/arma 3.
I can confirm. Though it is not only Proton Experimental. This is happening to me since quite some time on various versions including GE. Mostly when encountering this - for example on changing proton versions - I counter this by using Protontricks, selecting winecfg and in one of the tabs there is an option in "Input" tab to capture the mouse in fullscreen application. This works almost every time though I remember having certain proton versions either not showing the option or if then not working.
As I am not gaming atm I am also not very sure but enabling wayland for Proton did help as well afair but introduced some annoyance sometime that the game regrets to start on my main screen and even when moving it it moves back on actions like alt tabbing.
Hope this information is useful.
Also started happening for me rather recently on Proton Experimental - gamescope does mitigate the primary issue (cursor escaping the window during gameplay), but it conversely does not unlock the cursor when menuing (a rather appreciated implementation choice in many games).
I noticed this morning in Borderlands 3.
I've been running into this, as well as maybe-related bugs like the game not opening on the right screen or the mouse position being wrong/offset. It's not super consistent.
Games: Brickadia, The Finals
Having the same issue
I have had this same issue and I am on gnome and wayland. I attempted to use winecfg to lock the cursor in fullscreen and while it does sort of work, I noticed that in the menus the cursor barely reaches into my second monitor and whenever I am clicking repeatedly while moving my mouse quickly in cursor lock, the cursor doesn't lock and I am assuming this is because the cursor lock doesn't stop the cursor from escaping before it reaches my other monitor.
I've also had this issue since May this year. I've had it in The Finals, ARC Raiders and Satisfactory. Wayland/gnome btw. Choosing to capture the mouse in winecfg did not seem to help for me, but I was in borderless (if that makes a difference).
I did some more testing and the following did NOT solve the issue for me:
gamescope -W 2160 -H 1440 -f --force-grab-cursor -- %command%
From my testing, it appears this only happens on wayland sessions (probably specifically gnome), with proton. I could not reproduce the issue in native games, or on xorg.
https://www.reddit.com/r/linux_gaming/comments/1my8h8g/multi_monitor_labwc_mouse_sometimes_randomly
The workaround in that thread seems to work.
Using proton-ge and setting this in the launch options:
PROTON_ENABLE_WAYLAND=1 %command%
I'm guessing this skips XWayland, which might cause other unforeseen issues.
Replying to https://github.com/ValveSoftware/Proton/issues/8869#issuecomment-3288585673
Not working for me. The issue only appears when using the PROTON_ENABLE_WAYLAND=1 launch option.
I can confirm that this issue happens with GNome, but not with KDE Plasma. Perhaps it should be reported to the GNome project instead.
I can confirm that this issue happens with GNome, but not with KDE Plasma. Perhaps it should be reported to the GNome project instead.
This happens to me and im using plasma. This is a wine/proton issue that happens to some but not all that is caused by something like either specific drivers, software or hardware. Are you maybe using some specific brand mouse that happens to not be of the "popular" brands? does it happen to be a cheap chinese one?
I use LIX Plus Onyx White REV 1.1 which isn't "cheap chinese" mouse and it still happens to me.
My setup:
- OS: CachyOS
- DE: GNOME 49 (Wayland)
- Mesa: 25.2.6-cachyos1.2
- Kernel: 6.17.7-arch1-1
- GPU: AMD Radeon RX 6700 XT
My setup:
- OS: CachyOS
- DE: GNOME 49 (Wayland)
- Mesa: 25.2.6-cachyos1.2
- Kernel: 6.17.7-arch1-1
- GPU: AMD Radeon RX 6700 XT
I have a similar setup with similar problems. Only difference is that I have a 7800 XT.
I also had the same issues with Debian 13 on Gnome, but not with KDE Plasma.
Replying to https://github.com/ValveSoftware/Proton/issues/8869#issuecomment-3502045342
We have the same GPU
specs:
Operating System: Arch Linux
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7700 8-Core Processor
Memory: 32 GB of RAM (31,0 GB usable)
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 AORUS ELITE AX V2
Ill try a logitech mouse in a bit and see if this is a mouse issue.
Trying a Logitech mouse did nothing so mouse incompatibility is not the cause.
I posted a bug report on the gnome GitLab here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/4436
Proton versions
proton experimentalx2 2025-07
Launch options
PROTON_ENABLE_WAYLAND=1x2 2025-10
Proton Version: Experimental
Games: The Finals, Dungeon Defenders
OS: Ubuntu 24.04.2 LTS
GPU: Radeon 760M
Issue:
In some games that use first person with the mouse cursor captured. If the mouse is being moved rapidly while clicking, in the direction of another monitor. For example when shooting and moving the camera in a fps like The Finals. The mouse will break free of the window and start clicking on the other monitor. This clicking outside the window when the mouse has broken out will sometimes cause the entire Gnome desktop environment to crash killing all applications and throwing you to the lock screen. This issue was tested with 3 monitors with the game in full screen on the middle monitor, I also tested with 2 monitors where the same issue occurred. The issue does not occur when using a single monitor since there is nowhere for the mouse to go.