Thanks Julian.
I can confirm that the bug is gone after installing 47.1 on oracular and 
rebooting.

The upstream commit that fixes this issue is 
https://gitlab.gnome.org/jadahl/gnome-settings-daemon/-/commit/e7d890ea53b994d80ae14f41a9db01eaad3621bc
The upstream bug is 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/818

I still have the bug that the brightness set before suspend is not
restored on resume but the correct previous brightness is used when
increasing or decreasing it with the keyboard. But I guess this is
another bug and maybe not related to gnome-settings-daemon and more to
systemd. Maybe you can reproduce it too: set a very low brightness,
suspend, resume, brightness is high, increase brightness and brightness
is reduced because the increase is relative to the very low value set
before suspend.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2081294

Title:
  gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  The key shortcuts as well as slider controls in GNOME for setting the
  brightness of the screen on a amdgpu_bl1 laptop stops working after a
  sleep/resume cycle. The GNOME logs are the following after pressing
  the brightness increase and decrease Fn keys on the keyboard:

  12:46:37 (sd-bright): amdgpu_bl1: Failed to write brightness to device: 
Invalid argument
  12:46:37 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > 
min' failed
  12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device: 
Invalid argument
  12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > 
min' failed
  12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device: 
Invalid argument
  12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > 
min' failed
  12:46:35 (sd-bright): amdgpu_bl1: Failed to write brightness to device: 
Invalid argument
  12:46:35 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > 
min' failed
  12:46:34 (sd-bright): amdgpu_bl1: Failed to write brightness to device: 
Invalid argument
  12:46:34 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > 
min' failed

  Setting the backlight manually using the sysfs interface or the gsd-
  backlight-helper program still works:

  $ sudo strace /usr/libexec/gsd-backlight-helper 
/sys/class/backlight/amdgpu_bl1 15
  ...
  openat(AT_FDCWD, "/sys/class/backlight/amdgpu_bl1/brightness", O_WRONLY) = 4
  write(4, "15", 2)                       = 2
  close(4)                                = 0

  This is why I am filing this bug against gnome-settings-daemon and not
  the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to