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 662117 - Brightness slider doesn't sync with the current value
Brightness slider doesn't sync with the current value
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Screen
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 670043 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-18 17:39 UTC by yktooo
Modified: 2012-08-20 17:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Brightness: fix for gnome-settings-daemon changes (2.67 KB, patch)
2012-06-14 20:51 UTC, Giovanni Campagna
committed Details | Review

Description yktooo 2011-10-18 17:39:04 UTC
If brightness is changed not using the GNOME Control Center, but elsewhere, for example, with a brightness applet or with:

pkexec /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness <value>

the slider doesn't pick this value up. It only remembers the position it was ever dragged to.

It may be difficult to implement realtime tracking, but at least reading the current setting on initialization would be nice.
Comment 1 l300lvl 2011-12-19 02:34:08 UTC
I must confirm this. I would assume things are going to change in 3.4 perhaps regarding this, but at any rate. 

Running xbacklight and /usr/lib/gnome-settings-daemon-3.0/gsd-backlight-helper --get-brightness both confirm the correct brightness. Yet when you enter gnome-control-center>Screen the slider remains at a fixed setting, not of the actual brightness. So then you change it or it attempts to set it via undimming and it is not set correctly, but instead is set to that of the slider. 

I.e if you had it set to 7/70 manually and it dimmed, and had the slider set to 10/100(maximum), when it undimmed it would go to the sliders value, not ours.

The slider also has no affect on brightness at start-up, leaving no obvious reason for ever setting it with that slider.
Comment 2 Bastien Nocera 2012-06-12 13:04:53 UTC
*** Bug 670043 has been marked as a duplicate of this bug. ***
Comment 3 Giovanni Campagna 2012-06-14 20:51:46 UTC
Created attachment 216464 [details] [review]
Brightness: fix for gnome-settings-daemon changes

Apparently, g-s-d changed its DBus interface, and that made all
external changes to brightness invisible to the panel. Update
accordingly.
Comment 4 l300lvl 2012-06-14 22:08:30 UTC
The thing that sucks is it took well over a year for anyone to notice this bug. Is there anyway to patch this or perhaps rebuild g-s-d  or whatever it would be manually, so we could see this fixed in 3.2/3.4?
Comment 5 l300lvl 2012-06-15 02:14:57 UTC
(In reply to comment #3)
> Created an attachment (id=216464) [details] [review]
> Brightness: fix for gnome-settings-daemon changes
> 
> Apparently, g-s-d changed its DBus interface, and that made all
> external changes to brightness invisible to the panel. Update
> accordingly.
Comment 6 Clemens Buchacher 2012-07-08 07:51:40 UTC
This patch breaks the build. The build is fixed by commit ff08d1e3 (screen: Fix the build) in the master branch. But it is still broken in branch gnome-3-4. Please cherry-pick.
Comment 7 Bastien Nocera 2012-08-20 17:32:48 UTC
(In reply to comment #6)
> This patch breaks the build. The build is fixed by commit ff08d1e3 (screen: Fix
> the build) in the master branch. But it is still broken in branch gnome-3-4.
> Please cherry-pick.

Thanks for the notice, pushed.