Generic X-Box pad is not hidden for Vader 5 (Bazzite)

[nextproblemreporter]

Since the latest update the generic X-Box pad gets shown every time. Reboot and controller restart does not help.
Also M1-M4 are missing in steam for the Elite 2 tab and the gyro does not work in game, it works on desktop though.

[BANANASJIM]

Thanks! We couldn't reproduce these on the latest build with a real Vader 5 — all four paddles show in the Elite tab and the original pad is hidden correctly. This looks like the update may not have fully applied (known Bazzite issue #320). Could you paste:

padctl --version
systemctl --user status padctl.service --no-pager | head -5

If the version is older than the latest, that explains both the missing M1–M4 (the paddle fix is recent) and the visible X-Box pad (daemon not grabbing the controller). The in-game gyro is a separate known limitation tracked in #81.

How did you update — bazzite-setup.sh, the .deb, or something else?

[xl666]

I'm having a similar issue with bazzite, I believe it is related to the newer versions of steam client (I updated steam client and began to have problems), as official support is almost there, but still has problems.

[nextproblemreporter]

I just copy/paste the same script every time and just ran it again: "curl -fsSL https://raw.githubusercontent.com/BANANASJIM/padctl/main/scripts/bazzite-setup.sh
| bash -s -- --mapping vader5"

After that I just type "padctl switch mycurrentmapping.
This time it even said that no device is connected. Only after a controller reboot it found it.
But still the same bugs as said above.

padctl --version
padctl 0.1.13

systemctl --user status padctl.service --no-pager | head -5
● padctl.service - padctl gamepad compatibility daemon
Loaded: loaded (/etc/systemd/user/padctl.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
/etc/systemd/user/padctl.service.d

[BANANASJIM]

Thanks — 0.1.13 is current, so it's not a stale install.

xl666 may be right. Recent Steam builds read the Vader's hidraw directly on Linux. padctl hides the original pad via evdev grab + xpad unbind, but it can't lock hidraw (the kernel has no exclusive-open for it), so if Steam reads the raw device the Xbox pad stays visible and Steam may read paddles off the physical controller instead of our emulated Elite 2.

Two checks would confirm it:

lsof /dev/hidraw* | grep -i steam
cat /proc/bus/input/devices | grep -A10 "Xbox Elite"
evtest /dev/input/eventN    # press M1–M4

If steam/steamwebhelper holds the hidraw node, that's the cause. If BTN_TRIGGER_HAPPY1..4 fire in evtest but Steam ignores them, it's the client side. Turning off Steam Input for the Elite 2 should help meanwhile.

[xl666]

These are my outputs on bazzite:

xl666@bazzite /v/h/x/scripts> lsof /dev/hidraw* | grep -i steam
lsof: WARNING: can't stat() fuse.openrgb.appimage file system /tmp/.mount_openrgOP3IE9
      Output information may be incomplete.
steam    2436 xl666  109u   CHR  241,1      0t0  226 /dev/hidraw1

xl666@bazzite /v/h/x/scripts> cat /proc/bus/input/devices | grep -A10 "Xbox Elite"
N: Name="Xbox Elite Series 2"
P: Phys=
S: Sysfs=/devices/virtual/input/input50
U: Uniq=
H: Handlers=event9 js0 
B: PROP=0
B: EV=20000b
B: KEY=1f0f 0 0 0 0 0 0 7cdb000000000000 0 0 0 0
B: ABS=3003f
B: FF=10000 0

For the evtest:

• If I teste the input for the elite controller all button presses are registered (m1, m2, C, Z, etc)
• Those inputs are not shown in the steam controller input test as the extra buttons are only shown for the other controller (Flydigi Vader 5 Pro)
• If I test with evtest the other controller (Flydigi Vader 5 Pro) I don't see any output

[xl666]

After appliying comit #731bc17 the controller is not even shown in bazzite, padct status doesn't show anything either.