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 671821 - [screen] Brightness controls disappear quickly - "Timeout was reached"
[screen] Brightness controls disappear quickly - "Timeout was reached"
Status: RESOLVED DUPLICATE of bug 671505
Product: gnome-control-center
Classification: Core
Component: Other Preferences
3.3.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-11 11:42 UTC by Mantas Mikulėnas (grawity)
Modified: 2012-03-11 13:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mantas Mikulėnas (grawity) 2012-03-11 11:42:41 UTC 
When opening the "Brightness and Lock" control center applet, the brightness controls disappear after less than one second.

When this happens, `gnome-control-center` prints the following to stderr:

> screen-cc-panel-WARNING **: Error getting brightness: Timeout was reached

The brightness controls used to work in v3.2.2. Adjusting brightness using hardware keys, as well as the automatic dim-on-inactivity, still works.

gnome-control-center 3.3.91-1, Arch Linux
Comment 1 Mantas Mikulėnas (grawity) 2012-03-11 12:12:52 UTC 
Update:

When this happens, `gnome-settings-daemon --debug` prints the following to stderr:

> power-plugin-CRITICAL **: abs_to_percentage: assertion `value < min' failed

> GLib-GIO-CRITICAL **: g_dbus_method_invocation_return_gerror: assertion `error != NULL' failed

> GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed


Also, this seems to have been fixed in g-s-d git.
Comment 2 Bastien Nocera 2012-03-11 13:14:50 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 671505 ***