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 489176 - Display brightness sliders are inconsistant
Display brightness sliders are inconsistant
Status: RESOLVED OBSOLETE
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-preferences
2.20.x
Other All
: Normal minor
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-22 21:38 UTC by Jorge Castro
Modified: 2012-03-16 11:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Jorge Castro 2007-10-22 21:38:37 UTC 
The display brightness slider in the "On AC Power" tab measures brightness, but the same slider in the "On Battery Power" tab measures how much to dim the display. This is confusing.

Other information:
Comment 1 Richard Hughes 2007-11-02 18:55:19 UTC 
I've fixed this in trunk:

2007-11-02  Richard Hughes  <richard@hughsie.com>

	* data/gnome-power-manager.schemas.in:
	* data/gpm-prefs.glade:
	* src/gpm-backlight.c: (gpm_backlight_brightness_evaluate_and_set):
	* src/gpm-conf.h:
	* src/gpm-prefs-core.c: (prefs_setup_battery):
	Don't have a slider for brightness reduction on battery - it confuses
	too many people. Switch to a checkbox and leave gconf for power users
	to tweak this if they want. Fixes #489176

Can you please checkout trunk and tell me what you think? Thanks.
Comment 2 Pacho Ramos 2008-09-10 12:34:53 UTC 
I think that would be better simply set all sliders to select brightness value, not dim. This would be very clear and would still allow users to easily change the value without having to use gconf-editor (I think that changing brightness value shouldn't be considered as a "power user" task)

Thanks
Comment 3 Tobias Mueller 2009-03-27 22:01:26 UTC 
Hey Richard,

you've set this bug to NEEDINFO in comment #1. The question there has been answered in comment #2. I am thus reopening. Feel free to close if it's not an issue anymore :)