You are not logged in.
I'm having some trouble understanding how permissions on a system differ between logging in at the console and starting an x session remotely. When I connect to my arch host via ssh and start an x session with startx, certain permissions aren't available that are when I log in at the console.
For example, I can stream Steam games perfectly to my phone when I physically log in. However if I start an x session remotely the games don't receive gamepad input. I've tried fiddling with custom rules so that my user account can w/r to /dev/input but this doesn't make a difference. My DualShock 4 controller can still control the mouse over Steam Link when it is connected to my phone over bluetooth (even outside of games).
I'm on kernel version 5.17.1 running X11 and the latest version of Steam.
Last edited by insignian (2022-04-19 10:49:05)
Offline
I'm really sorry for bumping but I'm at a loss, I've been at this for weeks. The documentation doesn't go in-depth enough for startx for me to even know where to begin. This works perfectly fine if I don't use startx over SSH. I'm starting to lose a bit of hair, I know I'm just missing a config file or something ![]()
Last edited by insignian (2022-04-19 00:11:14)
Offline
Please don't bump, it's against the forum rules...
https://wiki.archlinux.org/title/Genera … es#Bumping
Offline
games don't receive gamepad inputMy DualShock 4 controller can still control the mouseCompare the output of "xinput" and post the xorg logs for both conditions.
Also see https://wiki.archlinux.org/title/Xorg#Rootless_Xorg since the difference might be around that.
Offline
I was able to find a solution! Steam Link was reading from /dev/input/event* files which it had no access to when an x session was started remotely. Still not sure why that is, but it may be outlined in the link you shared so I'll take a look.
The fix required me to create the file /etc/udev/rules.d/85-input-events.rules with the line:
SUBSYSTEM=="input",ATTRS{name}=="Microsoft X-Box 360 pad",MODE="666"This custom rule seems to be the current work around that doesn't open all input events like keyboard and mouse (security risk). I'll update this as solved.
Last edited by insignian (2022-04-19 10:49:39)
Offline
You could compare "getfacl /dev/input/event*" and "groups" between the logins.
Offline