I run OpenRGB and the software itself has an option to start on system startup, but it doesn’t start with sudo permissions (and cannot detect a certain USB device I have connected because of it).
If there’s a way to not tamper with its current startup procedure but somehow give it superior permissions, that would be enough.
Otherwise, I’m assuming there’s a file somewhere in which I need to paste some command that has “sudo openrgb” as well as some request for it to start up minimized possibly?
Anywho. Any help is appreciated. Ideally, again, there’d be some way to just simply give it more permissions permanently at the system level.
I’ve never used OpenRGB, but I just downloaded & extracted the package from the repos & noticed that there is a systemd service file: /lib/systemd/system/openrgb.service:
I am entirely confused by your reply ahaha. But I did find the mentioned file as well as grab a screenshot of the relevant part of my settings for OpenRGB.
If it’s relevant, it does detect things like my GPU, keyboard, and mouse. But there’s another USB device it isn’t detecting. I know you’re not familiar with the software, so it’s not too relevant. I’m just letting you know it “is” working in its current configuration, but it just needs a bit higher permissions to find that other device.
I’m not sure exactly what the “server” is or if it is running in the background. I notice it seems to not be selected in my settings. So, I’m a bit confused. Sharing the screenshot if it offers any clarification to move forward.
Edit: it’s also probably not too relevant, but I’m using the git one from the AUR. The creator pushed me towards that one simply because the official one doesn’t have my device added yet. I’m fairly confident it’s not a relevant difference to the software, though.
Try closing the OpenRGB GUI, then run the systemctl enable --now openrgb command (which should start the background service), and see if there is any difference and if the USB device is detected when you open the OpenRGB GUI again.
If enabling the systemd service causes problems, you can easily disable it:
I ran the command and it does seem to find the device now thankfully, and even seems to persist through the startups!
However, now it seems inconsistent at finding my graphics card? I have no clue why that would be the case. When I disable it, it seems to find it easier, but when I enable the command, it seems to not detect it upon restarting the computer.
This is much less of an issue (I’m not so hurt about it. The thing I’m trying to get working is part of my workflow (an indicator light), and my GPU’s LED isn’t ahaha).
If the answer isn’t apparent to you, no worries. It might be software specific and I’m not too fussed.
It is the only device on the list that is directly attached to my motherboard and not attached via USB, if that for some reason seems relevant.
I won’t be able to give much more (any?) help as I really don’t know the software. However, a quick browse via a search for “gpu linux” I did on the OpenRGB subreddit did indicate one possible answer.
Do you have the i2c-tools package, which is an optional dependency of openrgb, installed?
If that doesn’t fix the GPU detection issue, then hopefully someone else on this forum might be able to provide more advice. Or you might have to just spend a bit of time searching/browsing the OpenRGB subreddit, which seems to be a good place for help when it comes to Linux users.
Absolutely zero pressures/worries about it. I figured it was probably outside the scope here.
I do indeed have that dependency installed from the official repository (and I’m assuming I didn’t need to “do” anything with it based on your reply…just “have” it).
All is well, though. I’m not fussed enough with it and you have better things to do, so we can consider it solved.