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 727048 - Invalid backlight level at startup
Invalid backlight level at startup
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: power
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
: 709127 725056 728498 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-03-25 21:34 UTC by Armin K.
Modified: 2014-08-05 10:44 UTC
See Also:
GNOME target: 3.14
GNOME version: ---


Attachments
Picture 1, after log in (1.06 MB, image/png)
2014-03-25 21:34 UTC, Armin K.
  Details
Picture 2, after reloading the shell (1.06 MB, image/png)
2014-03-25 21:35 UTC, Armin K.
  Details
power: Emit change notification for brightness (2.66 KB, patch)
2014-04-22 23:22 UTC, Matthias Clasen
committed Details | Review

Description Armin K. 2014-03-25 21:34:50 UTC
Created attachment 272904 [details]
Picture 1, after log in

When I first log into gnome-shell, my backlight level shown on the system status is zero (see picture 1). I can get it ti show correctly after I reload gnome-shell (alt+f2 - r - enter) (see picture 2).

I'm using gnome-shell-3.12.0 with latest components, all built today.
Comment 1 Armin K. 2014-03-25 21:35:31 UTC
Created attachment 272905 [details]
Picture 2, after reloading the shell
Comment 2 Ray Strode [halfline] 2014-03-26 18:08:25 UTC
i think this because of a recent systemd change.  the systemd-backlight@ service tries to restore the backlight from /var/lib/systemd/backlight and if there are multiple backlight interfaces, they fight with each other (only some of them will have the right value, some will say 0, etc).
Comment 3 Armin K. 2014-03-26 18:14:30 UTC
$ ls /sys/class/backlight/
intel_backlight

I only have single folder in /sys/class/backlight and systemd restores backlight way before gdm is even started. It might be something with intel ddx since latest version has some backlight helper in libexecdir which I'm not sure how it works.
Comment 4 Ray Strode [halfline] 2014-03-26 18:21:36 UTC
could be.  does it happen if you rm -f the ddx and just let it fallback to the generic modesetting driver ?
Comment 5 Armin K. 2014-04-01 13:24:30 UTC
It's same on gnome-shell-wayland so I doubt it's true what I previously said.
Comment 6 Boyan Ding 2014-04-15 05:31:53 UTC
Confirming this bug from Arch Linux and I remember seeing the same thing on gnome-shell-wayland against the newest xwayland ddx (with mutter from git) in an vmware virtual machine.
Comment 7 Jasper St. Pierre (not reading bugmail) 2014-04-22 15:12:52 UTC
gnome-settings-daemon seems to be reporting the wrong value on startup, and never sends a PropertyChanged when it reads the real one. Code looks good to me, so I'm not sure what's going wrong.
Comment 8 Matthias Clasen 2014-04-22 23:22:55 UTC
Created attachment 274917 [details] [review]
power: Emit change notification for brightness

This is not happening automatically, and without it, the gnome-shell
and the gnome-control-center sliders don't react to each others
changes. This may also fix the problem where brightness sliders are
stuck at zero after login.
Comment 9 Matthias Clasen 2014-04-23 02:28:38 UTC
*** Bug 728498 has been marked as a duplicate of this bug. ***
Comment 10 Matthias Clasen 2014-04-23 14:30:29 UTC
Comment on attachment 274917 [details] [review]
power: Emit change notification for brightness

Attachment 274917 [details] pushed as ca70fd0 - power: Emit change notification for brightness
Comment 11 Bastien Nocera 2014-04-25 10:17:49 UTC
*** Bug 725056 has been marked as a duplicate of this bug. ***
Comment 12 Bastien Nocera 2014-04-25 10:30:56 UTC
Putting on NEEDINFO to check whether the problem is fixed by that patch.
Comment 13 Florian Müllner 2014-04-25 14:33:51 UTC
*** Bug 709127 has been marked as a duplicate of this bug. ***
Comment 14 Bastien Nocera 2014-08-05 10:44:27 UTC
Let's mark this as fixed, please file a new bug if the problem persists (it was fixed in gnome-settings-daemon 3.12.2 and 3.13.1).