Bug ID | 1118864 |
---|---|
Summary | Possible easy fix for Steam Controller issues |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | X11 Applications |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | samueldgv@pm.me |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Hi everyone, I was wondering why the Steam Controller was not working properly in OpenSUSE although it's working perfectly in any other distribution I tried before. Turns out there is a permissions issue which I guess could be easily handled in the steam-controller package. Several non-Valve games should be affected by this, and I can confirm it with Hyperlight Drifter in my case. Steam fails to virtualise the Steam controller access due to not having permissions on /dev/uinput Doing a sudo modprobe uinput, or even more bluntly, a chmod 666 /dev/uinput fixes it. I wonder why the Games group could not have access to it for example? This issue also was handled before in steam's issue tracker, link below: https://github.com/ValveSoftware/steam-for-linux/issues/4083 "Steam will try to open /dev/uinput when it sees a Steam Controller to create the virtual controller device and will fail to do so if it's not able to write to it."