GNOME Bugzilla – Bug 661287
Screen brightness never updated to the native value, patch included
Last modified: 2011-11-24 23:31:52 UTC
Created attachment 198632 [details] [review] fixes gsd-power-manager.c Hello, System: Gnome 3.2, Arch Linux, Samsung NC10, Linux 3.0 I get a bunch of warning messages in my .xsession-errors (gnome-settings-daemon:1297): power-plugin-WARNING **: failed to restore ...backlight to 100: out of brightness range: 100, has to be 8 -> 0 This happens every time the mode of power manager goes from `dim' to `normal'. A quick glance at your source code reveals that you initialize the undimmed brightness value to 100 at invocation of the power-manager and never update the value to the native one if there's a policy to ignore dimming. The range of brightness values on Samsung NC10 goes from 0 to 8. From what I gather, these ranges vary from system to system. The solution is therefore to update the brightness value even if there's a policy to ignore dimming. While I cannot duplicate bug #660755, I guess this bug is related to it. A patch is attached to this message. __ Elias Toivanen
Gnome-settings-daemon was writting the same error to my .xsession-errors. Compiling gnome-settings-daemon with the attached patch solved the issue. System: Gnome 3.2, Arch, Samsung R719, linux 3.0
I think this issue is fixed with this commit: http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=67785fa2b1043bd5397669f92abbd210dbf23f24 It's in gnome-settings-daemon 3.2.1.
Please test with gnome-settings-daemon 3.2.1.
(In reply to comment #3) > Please test with gnome-settings-daemon 3.2.1. This bug has indeed been resolved in 3.2.1 and it hasn't reappeared in 3.2.2 I'm currently using. As far as I'm concerned, this bug is fixed.
I can confirm this is fixed in 3.2.2.