From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] gdm fails to change screen brightness
Date: Sun, 25 Feb 2024 04:44:54 +0100 [thread overview]
Message-ID: <20240225034454.D73EE26D41@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48876@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
Closed issue by mayhair on void-packages repository
https://github.com/void-linux/void-packages/issues/48876
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.17_1 x86_64 GenuineIntel uptodate FFFFFFFFF
### Package(s) Affected
gdm-44.1_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
It is possible to change the screen brightness via GDM, either by using the brightness keys or the graphical slider.
### Actual behaviour
Pressing the brightness keys or using the slider does nothing, graphically. It does output an error similar to this to socklog:
```
2024-02-22T09:17:48.62989 authpriv.crit: Feb 22 14:17:48 pkexec[2028]: gdm: The value for the SHELL variable was not found in the /etc/shells file [USER=root] [TTY=unknown] [CWD=/var/lib/gdm] [COMMAND=/usr/libexec/gsd-backlight-helper /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight 80]
```
This is peculiar, because executing the same command (`/usr/libexec/gsd-backlight-helper /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight [brightness]`), as root and within an interactive shell works with no problems.
### Steps to reproduce
When GDM is set as the display manager, make sure you are logged out.
Then try to change the brightness, either by pressing the brightness keys or by clicking the top-right corner (where the Wi-Fi and battery symbols are) and adjusting the brightness slider.
next prev parent reply other threads:[~2024-02-25 3:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 12:18 [ISSUE] " mayhair
2024-02-22 21:43 ` chrysos349
2024-02-23 4:56 ` mayhair
2024-02-23 4:56 ` mayhair
2024-02-23 4:58 ` mayhair
2024-02-24 11:51 ` ahesford
2024-02-24 11:56 ` ahesford
2024-02-25 3:44 ` ahesford [this message]
2024-02-25 3:44 ` ahesford
2024-02-25 14:56 ` mayhair
2024-02-25 14:57 ` mayhair
2024-02-25 14:57 ` mayhair
2024-02-25 15:10 ` mayhair
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240225034454.D73EE26D41@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).