Compatibility Report

This also affects Plasma Wayland, but it affects all Wine applications as far as I can tell. It affects every Steam game I have tried unless they are running through Gamescope.

Can confirm that Proton v7+ crashes all my games with multitouch touchpad inputs.

This bug does not occur with proton v6 or lower

System:
Fedora Linux 36
GNOME 42
Wayland

Apps tested (all crashed with the touchpad gestures):
Runescape 3
OldSchool Runescape
Cookie Clicker
Farming Simulator
winecfg (protontricks)

Same for me with Football Manager 2022 with Proton 5.X, and I've never noticed that months ago also with same version of Proton.

"This bug was not present ~5 month ago and is probably linked to the support of mutitouch gesture in XWayland"
I think you're right, because I've never noticed that and the last time I've played to this game on my laptop was before december and it was working very well

Same thing with all proton games which I tryied
Crash when using any three finger gestures
Same for any wine apps, for example log from lutris:

X Error of failed request:  BadMatch (invalid parameter attributes)
 Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  28 (X_GetDeviceButtonMapping)
  Serial number of failed request:  481
  Current serial number in output stream:  481
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  10 (X_UnmapWindow)
  Resource id in failed request:  0x3a00003
  Serial number of failed request:  49645
  Current serial number in output stream:  49646

System:

OS: Fedora Linux 36 (Workstation Edition) x86_64
Host: Aspire A515-44 V1.09
Kernel: 5.17.6-300.fc36.x86_64
Resolution: 1920x1080
DE: GNOME 42.0
WM: Mutter
CPU: AMD Ryzen 3 4300U with Radeon Graphics (4) @ 2.700GHz
GPU: AMD ATI 05:00.0 Renoir
Steam from flatpak

Work for Sid Meier's Ace Patrol with Proton 4.11-13
Any higher Proton version lead to crash

This bug does not occur with proton v6 or lower

For me proton v6 still crash, tomb raider

Started seeing this freezing/unresponsive (then force quitting) on all the final fantasy pixel remaster games with three-finger trackpad swipe between multiple desktops in gnome/wayland. Took me a while to realize it was specific to gestures on the trackpad causing the issue. Only occurs with the trackpad, same gesture on touchscreen has no issues.

Adding to my above comment. Nearly same log as others above.

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  28 (X_GetDeviceButtonMapping)

System

Proton Version: Experimental (did see issue on 6.3-8 and 7.0-2)
OS: Manjaro Linux X86_64
Host: XPS 13 1950
Kernel: 5.16.20-2-MANJARO 
DE: GNOME 42.1 
CPU: Intel i5-6200U (4) @ 2.800GHz 
GPU: Intel Skylake GT2 [HD Graphics 520]

Anyone know if this bug is handled by any developer ?

It's a very uncomfortable bug..

I have same issue with vanilla wine. It seems to be upstream bug but I can't find it reported.
My ASUS laptop has no intel inside - just nvidia + amd

I tried to register at WineHQ bugzilla but I'm still waiting for email...
anyway I think this could be our upstream bug https://bugs.winehq.org/show_bug.cgi?id=53114

I still have this bug

I was able to work around this issue by using an older version of Proton. Currently I am able to gesture between workspaces while using Proton 4.11-13

The versions I tried which do not work:

• Current experimental (2022.12.09)
• 7.0-5
• 6.3-8
• 5.13-6
• 5.0-10

I'm currently trying to play Dwarf fortress, but for the sake of this comment I also (very briefly) tested a couple other games with the same result.

Hopefully that will help find the root cause.

Edit: I just noticed I missed the comment above also stating that 4.11 seems to work, so +1 I guess

I am also getting this issue when playing Disco Elysium and Dwarf Fortress. Guess I'll have to use Proton 4.11 for them, but it's really annoying.

As mentioned in the upstream bug discussion, disabling touchpad gestures for all XWayland app fixes the issue

xinput list --name-only | grep ^xwayland-pointer-gestures | xargs -n1 xinput disable

This also affects Plasma Wayland, but it affects all Wine applications as far as I can tell. It affects every Steam game I have tried unless they are running through Gamescope.

It seems to not affect Sid Myer's Civ 6, which is not a wine application so I'd imagine this is a wine bug.

xinput list --name-only | grep ^xwayland-pointer-gestures | xargs -n1 xinput disable

@kisak-valve Is there any way Steam could automatically run this command when launching XWayland games? I lost nearly 2 hours of progress in a game because it crashed due to this bug.

xinput list --name-only | grep ^xwayland-pointer-gestures | xargs -n1 xinput disable

@kisak-valve Is there any way Steam could automatically run this command when launching XWayland games? I lost nearly 2 hours of progress in a game because it crashed due to this bug.

@dylanmtaylor The WineHQ bug discussion linked above describes a way to make this change persistent and permanently disable touchpad gestures for all XWayland apps. Most of the apps don't even use any touchpad gestures, so this change probably won't affect you

xinput list --name-only | grep ^xwayland-pointer-gestures | xargs -n1 xinput disable

@kisak-valve Is there any way Steam could automatically run this command when launching XWayland games? I lost nearly 2 hours of progress in a game because it crashed due to this bug.

@dylanmtaylor The WineHQ bug discussion linked above describes a way to make this change persistent and permanently disable touchpad gestures for all XWayland apps. Most of the apps don't even use any touchpad gestures, so this change probably won't affect you

That's completely fair, but it would be really nice if the steam client would run that command before starting a game so that it will not crash for everyone and nobody would have to do a workaround.

nobody would have to do a workaround

I think running that command in and of itself is a workaround. The proper solution is to address the upstream Wine bug

nobody would have to do a workaround

I think running that command in and of itself is a workaround. The proper solution is to address the upstream Wine bug

Yes, but in the meantime, surely it'd be nice to not have it crashing for users?

Edit: The Command needs to be ran everytime the computer reboots, or the problem persists.

@ZoeTheTransHoe check the WineHQ thread linked above for a way to make this permanent

xinput list --name-only | grep ^xwayland-pointer-gestures | xargs -n1 xinput disable

the @ZoeTheTransHoe command fix's the issue

I don´t know why but I did not have this issue anymore on running Football Manager 2023 through Proton 8 out of the box, I'm running Manjaro Gnome so I'm on rolling release and a lot of things where updated recently.

Good news for this bug!

I don´t know why but I did not have this issue anymore on running Football Manager 2023 through Proton 8 out of the box, I'm running Manjaro Gnome so I'm on rolling release and a lot of things where updated recently.

Good news for this bug!

I am using Debian 12 lol

Same thing with most games I've tried, borderless or fullscreen, Wayland on Fedora 38 with RTX 4070 and i7-13700H

Can confirm with Townscaper & Enter The Gungeon, Proton Experimental, Gnome 42, Pop! OS, Lutris.

Still occurring with Scrivener 3, under Bottles on GNOME 45, Fedora Silverblue.

@myAinsel to be fair you shouldn't use Proton with software like Scrivener

Can confirm with Overwatch 2 and Deep Rock Galactic on fedora 38.

having this bug please fix !!!

Having the same issue. Gnome 45, Fedora 39, Proton Experimental

same issue in Detroit and Genshin, proton 8 in bottles, kde plasma.
3 finger and 4 finger gestures work fine, but if i use two finger pinch it crashes.

@frak0d Genshin?

I am hitting this issue on the new Apollo Justice: Ace Attorney game in GNOME Wayland.

Edit: It's fixed for me with the new XWayland version 23.2.6.

This is an upstream issue in Wine. You should report everything there instead of commenting about it here.

https://bugs.winehq.org/show_bug.cgi?id=53114

The thread also provides a simple workaround which solves this problem. If you have this issue as well, you should read that and perhaps join the upstream discussion instead of leaving a +1 comment here, where it's most likely not going to help whatsoever.

Additionally, there already is a merged XWayland PR that supposedly fixes this issue.

https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1215

You should wait for XWayland to update and include the fix.

There's now a PR open to backport the fix to the 23.2 branch of Xwayland, so it'll hopefully land soon.

@1player could you send the PR link here? Thanks!

@1player could you send the PR link here? Thanks!

https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1282

And it looks like xserver releases every month so we just need to wait for 23.2.5.

This is fixed in XWayland 23.2.6 on Fedora 40 :)

Ubuntu should also have the fix for this with its new XWayland version in 24.04. :)
https://packages.ubuntu.com/source/noble/xwayland
Arch Linux too. https://archlinux.org/packages/extra/x86_64/xorg-xwayland/
@kisak-valve I think this can finally be closed.