Have you tried running chmod 666 /dev/uinput and then seeing if it works? I've found that on my system (albeit a different distro) I need to consistently run that command as the permissions get reset every time I re-boot the computer.
I hadn't tried chmod 666 /dev/uinput yet, but I had tried changing the mode setting in the Udev files to 0666 instead of 0660, which I believe works similarly.
I just tried the command though, but unfortunately nothing changed
I had a similar issue with an Xbox 360 controller after this update on Solus.
I fixed it by disabling 'Use native runtime' in steam integration.
So I disabled "Use native runtime" in Linux steam integration. Controllers are now detected in steam and work in big picture mode. However, despite being detected in steam, none of my controllers can be used in game. Should I create a new issue for this problem?
So I disabled "Use native runtime" in Linux steam integration. Controllers are now detected in steam and work in big picture mode. However, despite being detected in steam, none of my controllers can be used in game. Should I create a new issue for this problem?
Same issue here, disiabled "use native runtime" and now none of my controls work in my games and rebinding them/loading other configs in steams controller configurations does nothing. It's like the games themselves see the controller but not the bindings anymore.
I hadn't tried
chmod 666 /dev/uinputyet, but I had tried changing the mode setting in the Udev files to 0666 instead of 0660, which I believe works similarly.I just tried the command though, but unfortunately nothing changed
Same here for me (Gentoo, flatpak-steam. The native binary also has the same problems and I tested it in other distros (fedora, debian and void)) I always have to reload the uinput module and give the permissions (chmod 666), so that the control works in games. My user is in the input group.
Any updates to this? I'd like to be able to play my games :(
I am having the exact same issue as both @smeejo1 and @jhill4009, same distro aswell. The fix by disabling "use native runtime" worked! Thanks :)
Your system information
Please describe your issue in as much detail as possible:
My issue is similar to the one described here (https://github.com/ValveSoftware/steam-for-linux/issues/7506), but for a different distro (Solus)
After Steam updated yesterday (12/7/20), Steam no longer detected my Hori Fighting Commander gamepad that had been working previously. In Big Picture mode, Steam says that no controller is detected. Switch Pro Controller still works.
I have tried editing the Udev files in /usr/lib64/udev, adding a new rules file in /etc/udev/rules.d, and reinstalling Steam, but none of these attempts have fixed the issue. I have installed steam on two different Solus machines to test, and the same problem occurs in both.
When I open steam in the terminal it doesn't seem to be able to locate the device. Before, upon startup, steam would notice that a device was plugged in and attempted to connect, even if the connection to the gamepad/arcade stick was ultimately unsuccessful.
(See terminal output here: https://gist.github.com/jhill4009/0745323efcdb485d03509952aac17a27)
(Here's what the output looks like with the Switch Pro Controller that connects successfully: https://gist.github.com/jhill4009/347de75fa37e467b8e72be551911af0a)
Steps for reproducing this issue: