this post was submitted on 12 Feb 2024
6 points (100.0% liked)
Linux Questions
1062 readers
2 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Probably but I was hoping for a simple solution
Actually there probably is one. I thought that the classic way of managing permission by the
video
group is gone, but in all my installs (Arch and NixOS) the GPU devices (~~/dev/video*
~~ EDIT:/dev/dri/card*
, the previous one is your webcam) are still owned byroot:video
. Maybe just adding your user tovideo
group will work? Arch Wiki even suggests this in this case:For me it is owned by the video user and the render group.
I don't mind running iceWM in a VM as it has a fairly small overhead. Its not like I'm actually using the desktop so it takes pennies worth of ram and no CPU
Interesting. For me, it's only the
/dev/dri/render*
device that is owned by therender
group, but this device is world-RW anyway. Still, I guess you can add the user to therender
group too? I did find some info that Debian uses that group this way, though I have never used Debian myself, so can't verify that.I already did that so that podman could access the device. (Podman runs as a local user). What was strange was that podman couldn't access it without a graphical session running but my local user could.
No idea then :( AFAIK the logind mechanism I mentioned originally is based only on permissions, but I had never really needed to look into it further.