[Feature Request] More Verbose error/information when dance pad device files (/jsX) aren't readable

[rlpowell]

Is there an existing issue for this?

• [X] I have searched the existing issues and none matched.

Operating System

Linux (Fedora 37)

CPU

N/A

GPU

N/A

Storage

N/A

Game Version

4.18.1

Game Mode

dance

Theme

fallback I think?, but it's not relevant

Describe the problem

This is right on the edge of bug vs. feature request, but:

If the /dev/input/js* files exist but are not readable, OutFox doesn't show any kind of error or complaint at all. The only indication that anything is wrong is that the dance pads don't show up in the game at all.

This plus my unusual SELinux setup led to me losing a couple of hours. :)

Describe what should happen

It would be nice if OutFox displayed some kind of error when the dance pad device files exist but can't be read, as that's clearly a bad configuration.

Relevant Log output

Logs are at https://gist.github.com/rlpowell/1fd89db71f85c5061cb2ecbeb8f1e71b

[Scraticus]

I've been looking into this one, and in alpha V we have enabled access to /jsX and /eventX by a pref so you can choose which end is which. If you have no access to /js because of SELinux, OutFox is never going to know this because we try to keep probing / scanning to a minimum for system security. You are right, I will see about adding more verbose debugging information a bit later on down the line. We also are trialling a new custom fedora build of OutFox, to help with some of the quirks.