After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 775729 - restoring backlight brightness sometimes delayed when returning from suspend
restoring backlight brightness sometimes delayed when returning from suspend
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2016-12-06 22:14 UTC by Christian Hergert
Modified: 2019-03-20 11:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Hergert 2016-12-06 22:14:43 UTC 
Sometimes when returning from suspend, it takes about 15-30 seconds for my brightness to be restored. Trying to manually set it using the status menu from gnome-shell also does not work (and its really hard to see the menu without a backlight).

The brightness appears to be equal to the lowest setting on my Lenovo X1 Carbon Gen3. I'm running an up to date Fedora 25, and currently on Xorg. I haven't noticed this behavior on Wayland sessions, but that doesn't mean it's not possible there too. It doesn't happen every time.

I also think the unlock screen was very dim (having a hard time remembering) but I'm so used to typing that quickly that it probably was dim too.
Comment 1 Bastien Nocera 2016-12-07 12:02:40 UTC 
Try disabling automatic brightness in the power settings. If it happens when the functionality is not enabled, then it's likely a kernel bug. gnome-settings-daemon does nothing to restore brightness on resume.
Comment 2 Christian Hergert 2016-12-07 20:19:01 UTC 
I don't have the "Automatic Brightness" UI in Power, so presumably the X1 Carbon Gen3 doesn't have a light sensor, or it is not getting discovered.
Comment 3 Bastien Nocera 2016-12-07 23:10:50 UTC 
Then I'm afraid that's probably not gnome-settings-daemon's fault. Maybe try running a different Xorg session, so you could check the behaviour there. systemd would be the one taking care of suspending the machine. The X server should handle anything display related.

If that doesn't happen, then we can try and investigate further in gnome-settings-daemon.
Comment 4 Christian Hergert 2016-12-08 21:43:22 UTC 
I'll keep trying to reproduce, but it might take some time since it's not 100% reproducible.
Comment 5 GNOME Infrastructure Team 2019-03-20 11:38:56 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/313.