Hello @ruineka, the comment at https://github.com/ValveSoftware/steam-for-linux/issues/4738#issuecomment-271682124 is equally valid as it was in #6615. This issue should be looked at from the Xwayland side.
This MR might solve this issue
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/975
I had to build xwayland with libei, xdg-desktop-portal, xdg-desktop-portal-gnome and mutter with InputCapture to make it work in gnome.
It solves issues with steam input under wayland, but still need some work for better user experience.
Here you can track InputCapture support status: https://gitlab.freedesktop.org/libinput/libei/-/issues/1
This seems to be mostly fixed. Steam uses the input portal to ask for permission to move the mouse. Any issue moving forward is on the DE side like Plasma not remembering the permissions. The fix happened before June, I just forgot to mention it here.
@Managor could you elaborate on the input portal? I am having the invisible mouse issue on Fedora/Wayland and not sure how to request permissions for steam to move the mouse
I'm using Arch/Plasma/Wayland. The desktop portal looks like this and it activates as soon as you try to move the mouse with a Steam Input device
Nothing like this appears for me on Plasma 6.1.2 using Tumbleweed.
Nothing like this appears for me on Plasma 6.1.2 using Tumbleweed.
Same here on Plasma 6.1.4 Tumbleweed.
I can confirm. It works on Arch with KDE plasma 6.1.4.
Seems to be a tumbleweed issue maybe?
Plasma 6 by itself is not enough, you'll also need an xwayland built with support for libei. If your distro does not package xwayland with support for libei, then please file a bug on your distro's bug tracker.
Pretty sure tumbleweed packages xwayland with libei but i could be wrong. Libei is installed?
@kisak-valve Can you add "Need retest" label?
What controllers are you guys testing? When I use a Steam Controller, the portal appears but when I use a Dualshock 3, it does not. If I use SC to open the portal and allow remote control, now the dualshock works as well.
Pretty sure tumbleweed packages xwayland with libei but i could be wrong. Libei is installed?
On Tumbleweed I do have a libei1 installed but there is still no mouse cursor support on Wayland with the Steam Controller.
Pretty sure tumbleweed packages xwayland with libei but i could be wrong. Libei is installed?
On Tumbleweed I do have a
libei1installed but there is still no mouse cursor support on Wayland with the Steam Controller.
It is not clear to me, from what you have written, if you have checked whether XWayland was built with support for libei, or you have just installed a library next to it. (I have no reason to believe, that you didn't, I just wanted to point out, that it isn't clear.) As Nowa-Ammerlaan said, you need an XWayland built with support for libei. Just because you installed it, does not mean, that it will use it.
While a mandatory package dependency is a dead give-away if your distro has shipped with an XWayland built with support for it, but unfortunately I don't know what else can you check, that is more certain, than that, as libraries can be loaded dynamically, making them not a hard requirement. But on Ubuntu, the system I use, you can check the build logs online, for which I found the following:
Plasma 6 by itself is not enough, you'll also need an xwayland built with support for libei. If your distro does not package xwayland with support for libei, then please file a bug on your distro's bug tracker.
I've just checked the build logs for XWayland on Ubuntu 24.10 and 25.04, and the following line (the only one I found mentioning the library) during the configuration phase suggest the library, currently does not include libei support:
Run-time dependency libei-1.0 found: NO (tried pkgconfig and cmake)
The issue is present on this system, and no desktop portal activates. I am, unfortunately, struggling to report requests of any kind towards the Ubuntu team. While don't want to leave it at that, I also don't want to promise anything.
Related to this I have just found that when running a game under Wayland my 8bitdo Pro 2 seems to loose access to Steam Input mappings, and thus reverts to its standard dinput reported BAYX layout rather than the ABXY one that steam uses.
Arguments Used
PROTON_USE_WAYLAND=1
System
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/8604#issuecomment-3690817381
Steam Input works fine with xlibre... we are getting hdr via dolby vision worked on rn things wont be this way forever when gamescope passes hdr directly from the x server this will stop being an issue for good.
When using mouse emulation to play Old-school RuneScape under Wayland the cursor is invisible but is usable in the sense that it technically works.