Your message dated Sat, 26 Aug 2023 14:27:14 +0200
with message-id <e639567c-0f21-4fdb-873b-4634b99d6...@debian.org>
and subject line Re: systemd: backlight service messes with screen brightness
has caused the Debian Bug report #950609,
regarding systemd: backlight service messes with screen brightness
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
950609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 244.1-2
Severity: normal
Tags: patch

Dear Maintainer,

Brightness controls on keyboard (and any other mean except xrandr) have not 
been working reliably since the day I installed Debian on my laptop: sometime 
it was possible to tune brightness after a fresh boot, sometime only after a 
S2R and resume.
Trying to find a solution, I have discovered that masking the backlight 
service fixes the problem:

sudo systemctl mask systemd-backlight@backlight:nvidia_0.service

I have double checked that enabling the service again restores the issue.
The relevant information on my system are:
Laptop model: HP Omen 15-dh0002nl, GPU Nvidia
Software: Debian/Unstable Xorg Nvidia proprietary drivers (don't mind about my
custom kernel, the issue is the same with Debian stock kernel)



-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.17-hpomen (SMP w/12 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:it (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser          3.118
ii  libacl1          2.2.53-5
ii  libapparmor1     2.13.3-7
ii  libaudit1        1:2.8.5-2+b1
ii  libblkid1        2.34-0.1
ii  libc6            2.29-9
ii  libcap2          1:2.27-1
ii  libcryptsetup12  2:2.2.2-2
ii  libgcrypt20      1.8.5-3
ii  libgnutls30      3.6.11.1-2
ii  libgpg-error0    1.36-7
ii  libidn2-0        2.2.0-2
ii  libip4tc2        1.8.4-2
ii  libkmod2         26+20191223-1
ii  liblz4-1         1.9.2-2
ii  liblzma5         5.2.4-1+b1
ii  libmount1        2.34-0.1
ii  libpam0g         1.3.1-5
ii  libpcre2-8-0     10.34-7
ii  libseccomp2      2.4.2-2
ii  libselinux1      3.0-1
ii  libsystemd0      244.1-2
ii  mount            2.34-0.1
ii  util-linux       2.34-0.1

Versions of packages systemd recommends:
ii  dbus  1.12.16-2

Versions of packages systemd suggests:
ii  policykit-1        0.105-26
pn  systemd-container  <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.136
ii  libnss-systemd   244.1-2
ii  libpam-systemd   244.1-2
ii  udev             244.1-2

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sat, 31 Jul 2021 23:52:29 +0200 Michael Biebl <bi...@debian.org> wrote:
On Fri, 7 Feb 2020 20:29:25 +0100 Valerio Passini
<valerio.pass...@unicam.it> wrote:
> Hi Michael,
> > Il Ven 7 Feb 2020, 19:05 Michael Biebl <bi...@debian.org> ha scritto: > > > Control: tags -1 = moreinfo
> >
> > What exactly was not working? What did you do, what did you expect, what
> > did (not) happen.
> >
> > Screen brightness controls (the two keyboard buttons designed to tune
> brightness and the sliders in GNOME and KDE) are ineffective. If I press
> the buttons or I move the slider, the OSD shows that brightness is
changing
> while actually it's not. I expect that brightness is being regulated by my
> actions.
> > systemd-backlight@.service simply stores the current backlight value on
> > shutdown and restores it on boot.
> > It reads from /sys/class/backlight/*/brightness and writes accordingly.
> > If that somehow confuses the hardware, this smells like a driver/kernel
> > issue.
> >
> > Michael
> >
> > I know that it seems unrelated to systemd-backlight, that service should
> store and restore brightness through reboots, but here:
>
https://devtalk.nvidia.com/default/topic/1061387/linux/screen-brightness-resets-to-max-after-reboot-linux-/
> I have found that systemd-backlight is keeping brightness to maximum and
so
> I tried to disable it just to see if my problem would be fixed, and so it
> is.
> The real culprit might be something else as you said previously, but at
the
> moment it is a decent workaround for me and it might be worth
investigating
> it further.
> > Tell me if you need more info. Best regards

Is this problem still reproducible?
If so, is it specific to the proprietary NVIDIA driver or also reproducible
with the noveau driver?


This smells like a driver and/or hardware specific problem.
Given the existing information, it's not really actionable for us, I'm thus closing the bug report.

Regards,
Michael

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to