Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: append FAQ with permission issue fix, see #63 #115

Closed
wants to merge 1 commit into from

Conversation

xNaCly
Copy link

@xNaCly xNaCly commented Nov 14, 2024

Fixes #63.

Copy link
Contributor

@andeston andeston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems a bit redundant. The permissions section already gives the solutions.

brightnessctl/README.md

Lines 21 to 29 in 3152968

## Permissions
Modifying brightness requires write permissions for device files or systemd support. `brightnessctl` accomplishes this (without using `sudo`/`su`/etc.) by either of the following means:
1) installing relevant udev rules to add permissions to backlight class devices for users in `video` and leds for users in `input`. (done by default)
2) installing `brightnessctl` as a suid binary.
3) using the `systemd-logind` API.

If someone is having this problem and they don't know why, they probably didn't read the README. Maybe a link to the README in the error message would be more helpful?

@xdbob
Copy link
Contributor

xdbob commented Dec 8, 2024

I think it's the distribution job to ship a working binary out of the box: see https://bugs.launchpad.net/ubuntu/+source/brightnessctl/+bug/2076317 this issue for example

@Hummer12007
Copy link
Owner

Thanks for the suggestion. I clarified it a little.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ubuntu 20 udev rules not working
4 participants