From: Albin <albin@fripost.org>
To: 22952@debbugs.gnu.org
Subject: bug#22952: MacBook2,1 brightness control requires root privileges
Date: Tue, 8 Mar 2016 23:50:44 +0100 [thread overview]
Message-ID: <56DF5744.6000706@fripost.org> (raw)
Hi,
I've discovered that the non-working brightness controls for the
MacBook2,1 are due to insufficient permissions.
The first indication of this was that I could change brightness by
running the program redshift with root permissions (`sudo redshift`).
Today I was presented with this dialog box in GNOME 3 after having
pressed one of the brightness-control keys:
"Authentication is needed to run
'/gnu/store/[...]-gnome-settings-daemon-3.18.2/libexec/gsd-backlight-helper'
as the super user.
Administrator
Password [__________]"
I tried to input both the user password and the root password but none
of this this had any effect. When I back into GNOME 3 as root, however,
the brightness controls were working.
Does anyone have a suggestion what I could try to give the various
brightness control programs (for GNOME 3, Xfce, etc.) the required
permissions without having to be logged in as root?
Cheers!
Albin
next reply other threads:[~2016-03-08 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 22:50 Albin [this message]
2016-03-09 13:21 ` bug#22952: MacBook2, 1 brightness control requires root privileges Ludovic Courtès
2017-04-19 22:23 ` bug#22952: Macbook2,1 " Joshua Branson
2017-04-20 8:45 ` bug#22952: Macbook2, 1 " Ludovic Courtès
2020-11-17 21:23 ` bug#22952: Backlight brightness keys in GDM and MATE require password authentication pelzflorian (Florian Pelz)
2020-11-18 21:14 ` Marius Bakke
2020-11-19 18:39 ` pelzflorian (Florian Pelz)
2022-01-04 23:46 ` bug#22952: MacBook2, 1 brightness control requires root privileges zimoun
2022-01-06 12:30 ` pelzflorian (Florian Pelz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56DF5744.6000706@fripost.org \
--to=albin@fripost.org \
--cc=22952@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).