Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Run as normal user

See original GitHub issue

I’ve been able to run this as a normal (non-root) user by creating the following udev rules in Arch Linux

/usr/lib/udev/rules.d/99-cm-rgb.rules

# cm-rgbi
SUBSYSTEM=="usb", ATTR{idVendor}=="2516", ATTR{idProduct}=="0051", MODE="0660", GROUP="plugdev", TAG+="uaccess", TAG+="udev-acl"

Then load the new rules with

sudo udevadm control --reload-rules
sudo udevadm trigger

Maybe this CLI tool could offer a way to create these rules for users with sudo access?

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

gfduszynskicommented, Jan 12, 2020

This feature is now implemented in v0.1.0 by running cm-rgb-cli add-udev-rule

1reaction

gfduszynskicommented, Jan 7, 2020

Ok, so I’ve learned what the TAG+="uaccess" means 😃

According to: https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/

If the goal is to have access to the device as current active user this tag is all that is required. No group should be defined in the rule unless device is to be used from a daemon.

I’ve even found reference to this group on Arch issue tracker, quote Plugdev is an obsolete group to give members of that group full access to removable devices. Permissions on such devices are granted by logind using ACLs these days, so there's no need for plugdev. Any package shipping such rules should be considered buggy. - Jan de Groot

I guess your rule should work equally well without the plugdev part.