steam-devices VS issue-tracker

if you mean this ( https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules ) in /etc/udev/rules.d , yes i did

Create an udev rule for the device, you can copy the rule for your device from here.

I am attempting to play Spelunky with a controller but I am not having any luck. Spelunky has a platinum rating on protondb and runs as expected. I am in a flatpak and I did install the udev rules from valve if any of that makes a difference. My controller works fine in native games.

I solved the problem by copying the 60-steam-input.rules file to the folder: /etc/udev/rules.d

this is their Github: https://github.com/ValveSoftware/steam-devices

steam maintains udev rules for controllers that might help: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules

Here is my open PR for the hori alpha for reference: https://github.com/ValveSoftware/steam-devices/pull/42/files

To use a controller with the Steam flatpak, you need to layer the steam-devices package from RPM Fusion, or download the udev rules from upstream and install them to /etc/udev/rules.d/ (which is what I did).

> The effort you need to go through to actually use these depends on how your distribution handles the file permissions of /dev/uinput. Some of them have it as root:input, in which case you just need to usermod -a -G input and then relog to get it working. Others have it as root:root so you either need to go do some reconfigurations to change its permissions or live with running the software using it as root.

There's a trick to that. The TL;DR is "install the steam-devices package or similar" (https://github.com/ValveSoftware/steam-devices/), which adds the following udev rule (and others, but this is the relevant one):

  # Steam Controller udev write access

It is connected to No updates since 39.20231205.0 issue.

Silverblue already only includes what I would call 'system utilities' in the base image (file manager, terminal, etc.), plus Firefox.

Silverblue issue: https://github.com/fedora-silverblue/issue-tracker/issues/451

UPDATE: Here is the issue on the Fedora Silverblue issue tracker Github.

Could you file an issue in the upstream issue tracker? https://github.com/fedora-silverblue/issue-tracker