Your message dated Sun, 9 Nov 2025 21:03:09 -0500 with message-id <CAAajCMaQ4aUjtM4OA418LXsro+LK0Q2-77rVcR2Z3tyvj=4...@mail.gmail.com> and subject line closing old gnome-settings-daemon bugs has caused the Debian Bug report #740951, regarding gnome-settings-daemon: Screen brightness hotkeys work only to lower 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 [email protected] immediately.) -- 740951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740951 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-settings-daemon Version: 3.8.5-2 Severity: normal When using the screen brightness hotkeys, (Fn + F[89] in this System76 daru4), the brightness is only adjusted when lowering it. WHen pressing the "raise brightness" hotkey, the OSD appears, but doesn't brightness doesn't rise. Opening the gnome power settings to adjust brightness works fine. Further investigation shows that the org.gnome.SettingsDaemon.Power.Screen.StepUp method is not working: # This works no matter if current percentage is lower or higher mdbus2 org.gnome.SettingsDaemon.Power \ /org/gnome/SettingsDaemon/Power \ org.gnome.SettingsDaemon.Power.Screen.SetPercentage \ 90 # This doesn't work mdbus2 org.gnome.SettingsDaemon.Power \ /org/gnome/SettingsDaemon/Power \ org.gnome.SettingsDaemon.Power.Screen.StepUp # But this does mdbus2 org.gnome.SettingsDaemon.Power \ /org/gnome/SettingsDaemon/Power \ org.gnome.SettingsDaemon.Power.Screen.StepDown Filing to gnome-settings-daemon because it seems like it provides this service. Please reassign if wrong. Also, if there is more information I could provide, please ask, I will be glad to provide it. Saludos -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-power-manager depends on: ii dbus-x11 1.8.0-2 ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1 ii gnome-settings-daemon 3.8.5-2 ii libc6 2.18-4 ii libcairo2 1.12.16-2 ii libglib2.0-0 2.38.2-5 ii libgtk-3-0 3.10.7-1 ii libpango-1.0-0 1.36.2-2 ii libpangocairo-1.0-0 1.36.2-2 ii libupower-glib1 0.9.23-2+b1 ii notification-daemon 0.7.6-1 ii upower 0.9.23-2+b1 gnome-power-manager recommends no packages. Versions of packages gnome-power-manager suggests: ii policykit-1 0.105-4 -- no debconf information
--- End Message ---
--- Begin Message ---There have been many changes to Debian since this bug was originally reported. If you are still experiencing this issue with Debian 13 (or with Debian 12 or Testing or Unstable), please report a new bug. Thank you, Jeremy Bícha
--- End Message ---
