Steam input on Wayland bug.

[Vepar]

I can't play KB/M games with Steam input on Wayland because the "mouse" only moves the cursor position, but not the actual cursor.

It makes all the kb/m games unplayable with the gamepad when using Steam controller.

Does anyone know of a fix?

[jrubz]

I remember something similar happening with Crosscode's Linux native version and having to fall to Proton+ the win.exe version. Each game works differently with it.

First question, which game is it happening with or are there multiple?

Second, what distribution (not too important, but knowing which kernel you are on can affect things) and environment (Gnome, KDE, Sway) are you running?

Third, are the games running Linux native binaries, or is this happening in Proton? Which Proton version have you selected to use?


If the game is trying to open as a Wayland window, but hasn't been updated, try placing this in its starting variables to force it to start in xWayland as a compatibility workaround.
GDK_BACKEND="x11"
(this might change based on what libraries the game uses. I pulled this from the Debian documentation on Wayland. https://wiki.debian.org/Wayland

[thetargos]

There is a 'recently' patched issue with Steam Input and Wayland, which would cause exactly that behavior, not present on X11 (and one of the reasons the Deck's Desktop mode runs on X11), so I suppose you require a fairly recent Wayland and libinput stack in order to have the trackpads move the cursor on a wayland compositor

[Vepar]

Originally posted by jrubz:

I remember something similar happening with Crosscode's Linux native version and having to fall to Proton+ the win.exe version. Each game works differently with it.

First question, which game is it happening with or are there multiple?

Second, what distribution (not too important, but knowing which kernel you are on can affect things) and environment (Gnome, KDE, Sway) are you running?

Third, are the games running Linux native binaries, or is this happening in Proton? Which Proton version have you selected to use?


If the game is trying to open as a Wayland window, but hasn't been updated, try placing this in its starting variables to force it to start in xWayland as a compatibility workaround.
GDK_BACKEND="x11"
(this might change based on what libraries the game uses. I pulled this from the Debian documentation on Wayland. https://wiki.debian.org/Wayland

It's not happening in any specific game, it's happening to desktop mode, games, anything involving a cursor. Most recently Tyranny on Heoric launcher. I use "SC Controller" app for gamepad configurations. But even if i use just Steam, the cursor position is moving, but the cursor is not. I can see it highlighting stuff in the library, but the cursor doesn't move.

So it's directly steam input on wayland related, not related to anything regarding proton or linux native games. Though - idk why but linux native games don't recognize the controller at all (like Grim fandango recently). Idk if that's the game's fault or not but that's another topic.

I use Arch with gnome and the LTS kernel (cause the new one had a kernel panic so i'm waiting for an update before i try the normal kernel again).
So it's 6.1.37-1-lts.
Gnome 44.

Originally posted by thetargos:

There is a 'recently' patched issue with Steam Input and Wayland, which would cause exactly that behavior, not present on X11 (and one of the reasons the Deck's Desktop mode runs on X11), so I suppose you require a fairly recent Wayland and libinput stack in order to have the trackpads move the cursor on a wayland compositor

Yes, X11 doesn't have that issue but i can't use it cause it's just horrible. The dual monitors get switched, apps open up on the wrong monitor, and displayport dies after a resume. I get a tiny bit more FPS on X11 on some games but i can't deal with the jankyness of it.

How recent and what packages do i need? :D

Querying pacman for package versions:

local/libinput 1.23.0-1
local/xf86-input-libinput 1.3.0-1 (xorg-drivers)
local/lib32-libva 2.18.0-1
local/lib32-wayland 1.22.0-1
local/libdecor 0.1.1-2
local/libva 2.18.0-1
local/qt5-wayland 5.15.10+kde+r51-1 (qt qt5)
local/qt6-wayland 6.5.1-1 (qt6)
local/wayland 1.22.0-1
local/wayland-protocols 1.31-1
local/wlroots 0.16.2-1
local/xorg-xwayland 23.1.2-1 (xorg)
local/steam-native-runtime 1.0.0.75-3

Cause i'm on Arch, and while i'm currently on the LTS kernel, Gnome and everything else should be the newest version...

EDIT: I updated the system, and the kernel updated too. I restarted Arch into the normal kernel, and even went into Steam bet. Still the same issue.

[thetargos]

IIRC it should still should be in Wayland/libinput git

[jrubz]

hmm. I'm not seeing anything that looks out of place with your package list there. Your Kernel choice likely isn't an issue. This only happens in Steam right?

It's your own system as well, but did you install anything from the AUR that replaced a base package that could be related to input?

[Vepar]

Originally posted by jrubz:

hmm. I'm not seeing anything that looks out of place with your package list there. Your Kernel choice likely isn't an issue. This only happens in Steam right?

It's your own system as well, but did you install anything from the AUR that replaced a base package that could be related to input?

Originally posted by thetargos:

IIRC it should still should be in Wayland/libinput git

Well, this is all of the AUR packages:

dotpac
fancontrol-gui
heroic-games-launcher-bin
libinput-git
libsidplay
looking-glass
playonlinux
prismlauncher
python-inputs
python-steam
python-vdf
reshade-shaders-git
sc-controller
steamtinkerlaunch
tidal-hifi-bin
timeshift
unityhub
ventoy
viber
vkbasalt
webkit2gtk-5.0
yay

The onlyone that is related to input from the list is libinput-git which i installed a few minutes ago to see if it'll fix the issue.

It did not.

Everything else shouldn't have affected input in any way.

Besides, this was present since i installed Arch. And was present in KDE when i had it as well.

Do i need to install wayland-git as well from AUR? I'd rather not mess with wayland in general, but i'll try it. :P

[Vepar]

Umm...

UPDATE:

Using SC Controller app, with Steam closed, now moves the cursor. And i tested Tyranny in Heroic, and it works inside the game too.

I guess libinput-git did work, just not for Steam.

[deaddoof]

Workaround found for this bug. Extest

https://github.com/Supreeeme/extest

This project implements the X11 XTEST extension which is needed for steam input. The project needs a recent xwayland and a pretty recent version of libei

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

There is an upstream bug for this issue.

[Vepar]

Originally posted by deaddoof:

Workaround found for this bug. Extest

https://github.com/Supreeeme/extest

This project implements the X11 XTEST extension which is needed for steam input. The project needs a recent xwayland and a pretty recent version of libei

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

There is an upstream bug for this issue.

Nice, didn't know about that.
Currently i'm on Xfce4 cause Nvidia and wayland aren't friends yet.
But i'll keep that in mind for the future!