bitfocus
[BUG] udev Permissions seem to brick after recent kernel update
Make sure you're on the latest stable or beta build
- [x] I have tested this on the latest stable or beta release
Is this a bug in companion itself or a module?
- [x] I believe this to be a bug in companion and not a specific module
Is there an existing issue for this?
- [x] I have searched the existing issues
Describe the bug
I am not sure if this is an issue directly with companion itself, but I recently updated a system running Companion (the repositories, not Companion initially) and I lost the ability for it to connect to the streamdeck. Initially it was failing to even establish a connection to the Streamdeck, lsusb would hang and I discovered that the kernel wasn't even initializing the streamdeck, the dmesg log was this - `[ 1042.787191] usb 1-4: new high-speed USB device number 53 using xhci_hcd
[ 1042.973500] usb 1-4: device descriptor read/64, error -71
[ 1043.266772] usb 1-4: Device not responding to setup address.
[ 1043.472932] usb 1-4: Device not responding to setup address.
[ 1043.679481] usb 1-4: device not accepting address 53, error -71
[ 1043.681972] usb usb1-port4: attempt power cycle`
Googling around led me to try adding xhci_hcd.quirks=262144 to GRUB seemed to resolve the connection issue. However- Companion still wouldn't connect to the SD. It could see it now though, and the log would display the error `error
Surface/Controller Found "elgato-streamdeck" device, but no access.
Please quit any other applications using the device, and try again.`
It turned out the device permissions were set to root only, I created a new udev rule with this line - KERNEL=="hidraw*", ATTRS{idVendor}=="0fd9", ATTRS{idProduct}=="006c", MODE="0660", GROUP="companion" and that immediately allowed Companion to see the SD again.
From what I can tell, something updated and possibly wiped out the udev rules that were in place? I'm not sure what it's supposed to look like- 50-companion.rules is still there and looks like what it should in the current repository
Steps To Reproduce
Update the kernel
Expected Behavior
Not to lose the ability to have Companion connect to a StreamDeck
Environment (please complete the following information)
- OS: Ubuntu 24.04 LTS
- Browser:Firefox
- Companion Version: 4.2.0 stable (was initially a previous version of 4.x.x, updated after I lost the SD to see if that'd fix it)
Additional context
My apologies if this is not actually a bug and is something I did. This is a machine we use only every so often. It got put away fine, we pulled it back out, updated via apt and it bricked. Those are the steps I took to resolve the issue and I wanted to make sure it was made known in case this isn't isolated to us. Thanks!
What kernel version is it that broke for you?
I am using fedora with kernel 6.17.9-300.fc43.x86_64 and havent had issues. I havent tried on ubuntu 24.04 in a while though.
I have no ideas as to what could have happened for you, that line you added to your udev file is already in there as far as I can tell, so that shouldnt have changed anything.
It updated to 6.8.0-88-generic.
There are a couple of other udev rules after companion, I'm guessing one of them switched it? I added my rule to a new udev file with a 99 prefix.
That doesnt sound normal. That would only happen if another application had rules for the same usb ids in a later numbered file.
You got it working though, and this doesnt sound like anything that would be happening more widely, so Im going to close this.
If you want to figure out what happened, we can keep discussing.
I'm curious what other udev rules files you have. Perhaps any from other applications which could use streamdecks?
I agree. Something odd happened and I don't really know what initiated it. I mostly just wanted to make sure it wasn't something that was prevelant, but when I get a chance I will look closer at the other rules and report back. Thanks!
Nothing else seems to reference the streamdecks in the udev rules. And the companion rules are intact and have the same rule that I added with the 99- file that ultimately fixed it. I'm confused, but as you said it's working so 🤷