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 661037 - idle for a few seconds, touch mouse, screen dims dramatically
idle for a few seconds, touch mouse, screen dims dramatically
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: power
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-06 00:20 UTC by Andy Grover
Modified: 2011-11-01 16:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andy Grover 2011-10-06 00:20:54 UTC
F16 beta, on a Lenovo E220s. 

Screen settings are

dim screen to save power: disabled
Turn off after: 30 minutes
lock:on
Lock screen after: screen turns off

I see the first 5 messages (up until "setting up blank callback") and then as soon as I move the mouse or hit a key I get the last three lines, and the screen dims down to almost unusable. Brightness slider in control panel never moves, but I can get screen brightness back by adjusting the slider.

(gnome-settings-daemon:2817): power-plugin-DEBUG: idletime alarm: 1
(gnome-settings-daemon:2817): power-plugin-DEBUG: normal to dim
(gnome-settings-daemon:2817): power-plugin-DEBUG: Doing a state transition: dim
(gnome-settings-daemon:2817): power-plugin-DEBUG: not dimming due to policy
(gnome-settings-daemon:2817): power-plugin-DEBUG: setting up blank callback for 1800s
(gnome-settings-daemon:2817): power-plugin-DEBUG: idletime reset
(gnome-settings-daemon:2817): power-plugin-DEBUG: Doing a state transition: normal
(gnome-settings-daemon:2817): power-plugin-DEBUG: X not idle
Comment 1 christophe.gueret 2011-10-06 11:13:00 UTC
I have exactly the same issue with Archlinux x64 and Gnome 3.2 on my Macbook pro.
The fix I found for now is an endless loop that forces the brightness back to its maximum through /sys.
Comment 2 Andy Grover 2011-10-06 16:39:15 UTC
I had luck downgrading to 3.1.92, if that's an option for you:

https://bugzilla.redhat.com/show_bug.cgi?id=743791
Comment 3 christophe.gueret 2011-10-06 17:01:36 UTC
I went for a more radical solution and delete the files related to the power plugin.
Comment 4 christophe.gueret 2011-11-01 16:29:20 UTC
The problem is gone with 3.2.1