Closed rathann closed 8 months ago
Solaar depends on being able to write to /dev/hidrawN nodes. This is done by the Solaar udev rule that needs to be installed. One possible diagnosis is that at resume time the rule did not run. Validating this diagnosis would require being able to set up conditions for the situation to reliably occur and then monitoring udev rule processing. The other possible diagnosis is that Solaar is using a handle left over from before the suspend. Validating this diagnosis would also require being able to recreate the situation.
Was Solaar able to recover from this error? Did the new receiver show up?
Unfortunately, the original reporter cannot reproduce this anymore, so let's close for now. I'll ask reporters of all open bugs we have in Fedora at the moment to re-test with 1.1.11 before forwarding any more reports here.
Information
solaar --version
orgit describe --tags
if cloned from this repository): 1.1.9uname -srmo
):Linux 6.2.15-300.fc38.x86_64 x86_64 GNU/Linux
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Describe the bug Solaar is throwing a PermissionError exception after resuming a machine with a different receiver than the one present at suspend.
To Reproduce Steps to reproduce the behavior:
Screenshots N/A
Additional context Downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2208009 .