-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dumps trace w/ mouse plugged in #170
Comments
That's strange, Does the following command work?
Can you also try?
|
It only tries to open the device when you have a compatible mouse plugged in and no udev rules installed. With
The above work fine and print everything as intended. |
Ok, I will look at that... To solve your issue:
:) |
Thank you. I managed to fix it before reporting the bug but it took a while until I found the RIVALCFG_DRY=1 environment variable. |
Ok, thank you again for your repport. I will try to fix permission issues when Rivalcfg is used with debug / help / version options :) |
I made a fix on |
Rivalcfg dumps trace with mouse plugged in and udev rules not installed. As a consequence --print-udev, --help and the other help switches cannot be displayed. I installed it into my home directory, so
sudo rivalcfg --update-udev
does not work since root env doesn't know about the local python lib path.The text was updated successfully, but these errors were encountered: