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 483144 - Gconf key for battery brightness labeled incorrectly...
Gconf key for battery brightness labeled incorrectly...
Status: RESOLVED FIXED
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.20.x
Other Linux
: Normal minor
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-03 23:05 UTC by Tim Hull
Modified: 2008-06-30 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Tim Hull 2007-10-03 23:05:55 UTC
In gnome-power-manager 2.20.0, the gconf key for the battery brightness reduction percentage is labeled as such:

"The brightness of the display when on battery power. Possible values are between 0 and 100."

This is, of course, wrong, as setting this to 100 results in the brightness being reduced to minimum on battery.  The name of the key, brightness_battery, is also a similar misnomer.

Either the key/description should be changed, or this should be changed to an actual battery brightness value as opposed to a reduction percentage.
Comment 1 Richard Hughes 2007-10-04 19:31:08 UTC
Ahh, the description is wrong. Could you russle up a patch for the schema explaining that it's a reduction and then I'll commit that. Thanks.
Comment 2 Eddy Petrişor 2008-06-30 00:58:03 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 3 Eddy Petrişor 2008-06-30 01:09:58 UTC
Sorry, the entire list of bug was:
bug #478128,
bug #483134,
bug #483143,
bug #509211,
bug #530346,
bug #335673 and
bug #483144
Comment 4 Richard Hughes 2008-06-30 10:51:59 UTC
2008-06-30  Richard Hughes  <richard@hughsie.com>

	* data/gnome-power-manager.schemas.in:
	* src/gpm-backlight.c: (gpm_backlight_brightness_evaluate_and_set),
	(conf_key_changed_cb):
	* src/gpm-conf.h:
	Fix the name and description of the gconf key:
	/apps/gnome-power-manager/backlight/brightness_dim_battery
	Fixes #483144