Hi, thank you for this great software! I found a minor UI behavior issue when using Oversteer via Flatpak on Ubuntu 26.04.
When launching Oversteer, it displays a popup saying: "You don't have the required permissions to change your wheel settings."
However, clicking "OK" dismisses the message, and I can perfectly modify my wheel settings after that.
How to reproduce:
Have a system where other USB HID devices (like a mouse or keyboard) create restricted /dev/hidraw* nodes (e.g., crw------- root root).
Have the racing wheel properly configured with udev rules so its specific /dev/hidrawX node is accessible (e.g., crw-rw-rw-).
Launch Oversteer.
Root cause analysis:
It seems Oversteer scans all /dev/hidraw* devices on startup to check for permissions. Because it hits a permission denied error on an unrelated device (like /dev/hidraw0 for my mouse), it throws the global error dialog, even though the actual wheel (e.g., /dev/hidraw9) is perfectly accessible and functional.
Suggested improvement:
Oversteer should probably ignore Permission denied errors during the general device scan phase, and only throw the permission error if the specific targeted racing wheel device node cannot be opened.
Environment:
OS: Ubuntu 26.04
Install method: Flatpak (Flathub)
Wheel: Logitech G29 Driving Force Racing Wheel
Hi, thank you for this great software! I found a minor UI behavior issue when using Oversteer via Flatpak on Ubuntu 26.04.
When launching Oversteer, it displays a popup saying: "You don't have the required permissions to change your wheel settings."
However, clicking "OK" dismisses the message, and I can perfectly modify my wheel settings after that.
How to reproduce:
Have a system where other USB HID devices (like a mouse or keyboard) create restricted /dev/hidraw* nodes (e.g., crw------- root root).
Have the racing wheel properly configured with udev rules so its specific /dev/hidrawX node is accessible (e.g., crw-rw-rw-).
Launch Oversteer.
Root cause analysis:
It seems Oversteer scans all /dev/hidraw* devices on startup to check for permissions. Because it hits a permission denied error on an unrelated device (like /dev/hidraw0 for my mouse), it throws the global error dialog, even though the actual wheel (e.g., /dev/hidraw9) is perfectly accessible and functional.
Suggested improvement:
Oversteer should probably ignore Permission denied errors during the general device scan phase, and only throw the permission error if the specific targeted racing wheel device node cannot be opened.
Environment:
OS: Ubuntu 26.04
Install method: Flatpak (Flathub)
Wheel: Logitech G29 Driving Force Racing Wheel