You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I tried fetching my Headset's battery status (Corsair HS 70 pro) in order to display that information in my instance of xmobar. I am running arch with kernel version 6.8.2.
If I try running headsetcontrol -b or with any other option (without sudo) I get the output:
Found Corsair Headset Device!
Error: [battery] Could not open device. Error: Failed to open a device with path '/dev/hidraw0': Permission denied
The vendor id and product id are listed int the .rules file at /usr/local/lib/udev/rules.d/70-headsets.rules, and I did try reloading these rules with the command given in the readme and rebooting. What might be the issue here?
I did try that, with no success unfortunately. I am really confused, because it used to work in the past... I think before I used the version from the AUR, and not building from source. The issue here is that things are really hard to reproduce, since Arch installs mostly are not the same. I don't know if this is worth looking into for you, unless more people have the same issue. Can you maybe point me to the crucial parts in the repo that I can have a look into, to maybe try to find a fix for me?
Description
Hello, I tried fetching my Headset's battery status (Corsair HS 70 pro) in order to display that information in my instance of xmobar. I am running arch with kernel version 6.8.2.
If I try running
headsetcontrol -b
or with any other option (without sudo) I get the output:The vendor id and product id are listed int the
.rules
file at/usr/local/lib/udev/rules.d/70-headsets.rules
, and I did try reloading these rules with the command given in the readme and rebooting. What might be the issue here?Headset Name
Corsair HS 70 Pro
On which OS does the problem happen?
Linux
Device information
Detailed Device Information
The text was updated successfully, but these errors were encountered: