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 483143 - Brightness not restored to previous value on leaving idle...
Brightness not restored to previous value on leaving idle...
Status: RESOLVED FIXED
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-03 23:01 UTC by Tim Hull
Modified: 2009-03-04 14:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
My GPM info from the .sh script (2.51 KB, text/plain)
2008-03-29 09:22 UTC, lists
Details

Description Tim Hull 2007-10-03 23:01:12 UTC
In gnome-power-manager 2.20, the system brightness is not restored to its previous value on leaving the idle state.  This seems like a logical thing to do - otherwise, we end up with the screen possibly becoming brighter (or worse, actually becoming more *dim*) once the system exits the idle state.

This issue has been confirmed on the latest release of gnome-power-manager as shipped with Ubuntu "Gutsy".
Comment 1 Jochem Kossen 2007-10-07 13:20:19 UTC
Link to the relevant Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137598
Comment 2 lists 2008-03-29 09:22:49 UTC
Created attachment 108208 [details]
My GPM info from the .sh script

I'm not entirely sure that the description covers my bug. My computer (unpredictably and not very related to time) dims the backlight occasionally. When I then move the mouse etc, the brightness doesn't change at all. That leaves it as permanently dimmed unless I use the hotkeys to raise it again.
Comment 3 Eddy Petrişor 2008-06-30 00:53:50 UTC
Hello,

1) I hate all these brightness related bugs, especially since they represent a regression.
2) There are several bugs that overlap(#478128, #483134, #483143, #509211)  ; IMHO, there should be ONLY ONE

I have reported this in Debian bug #467264 and I explained why the current (and former) behaviour is(was) wrong and how they should actually behave.


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467264


To summarize:
- AC and battery settings MUST not interact with each other
- the battery *brightness*slider* should be *brought*back* (one should be able to set the default battery brightness level, no matter what automatic dimming effect is added)
- dimming on idle should *really*dim*or*do*nothing*, if dimming is not possible; is should NEVER bright up the display
- using the *brightness* *keys* should be a clear adjustment of the default brightness level and it should *always* have precedence over anything automatically computed or commanded
- DO NOT DIM WHILE ACTIVE


If anyone cares, here is the summary I made in the debian bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467264#33
Comment 4 Eddy Petrişor 2008-06-30 01:09:37 UTC
Sorry, the entire list of bug was:
bug #478128,
bug #483134,
bug #483143,
bug #509211,
bug #530346,
bug #335673 and
bug #483144
Comment 5 Kamil Páral 2008-09-03 09:03:48 UTC
I confirm this bug in Gnome 2.22.3. The brightness is dimmed on idle, but after activity the previous brightness value is not restored (instead some other value is set, in my case much brighter value). This is extremely annoying.
Comment 6 Brittany Dunlap 2008-12-23 13:20:57 UTC
I'm using Gnome 2.24.1 and still have this brightness issue. Even when activating a virtualbox session screen brightness falls to zero. That happens with OpenCity as well.

My laptop does not have a physical brightness slider such as those on older IBM laptops.

I don't know if it's a bug with xbacklight as well as gnome-power-manager but when I manually set brightness to 100 after auto-dimming it does not work but setting it to 99 then to 100 works.
Comment 7 Richard Hughes 2009-03-04 14:43:44 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.