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 529671 - g-p-m should remember manually adjusted brightness
g-p-m should remember manually adjusted brightness
Status: RESOLVED FIXED
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.20.x
Other All
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-04-24 08:07 UTC by Alexander Hunziker
Modified: 2009-03-04 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Alexander Hunziker 2008-04-24 08:07:16 UTC
Please describe the problem:
If I'm working on battery power in a bright place, I keep having to adjust the brightness manually, because every time the display dims after a 30 second timeout, and then comes up again when I move the mouse, it only comes up to the level set in the preferences, and not the level i have set two minutes before. I think it should keep that value until the session end or until connected to AC

Steps to reproduce:
1. Set a brightness manually, working on battery
2. Do nothing, wait until display dims.
3. Move mouse, display gets brighter, but not as just set.


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Richard Hughes 2008-04-24 08:32:51 UTC
Can you please try with trunk and tell me what you think? I've re-written a large chunk of the brightness stuff there. Thanks.
Comment 2 Alexander Hunziker 2008-04-24 11:22:25 UTC
I don't have access to a trunk installation. It should be easy to verify for you though. if you need a better problem description, get back to me.
Comment 3 Alexander Hunziker 2008-10-14 08:08:09 UTC
I can confirm that brightness adjustion works more reliably for me, so the re-write seems to help. As to the problem originally described above, that still persists. Again, to explain:

* I'm working on battery, g-p-m sets brightness correctly to whatever is set in GConf. (call this level A)
* I'm in a place with lots of ambient light, so I manually set brightness to maximum.
* I'm not doing anything for 30 seconds, the display dims, as it should
* Upon moving the mouse, the display gets brighter again, but it goes to level A, instead of maximum brightness.
Comment 4 Josselin Mouette 2008-11-10 15:53:06 UTC
See also http://bugs.debian.org/505051 which looks like the same issue.
Comment 5 Rui Matos 2008-12-12 01:02:44 UTC
I also see the behaviour described in comment #3 in Fedora 10.
Comment 6 Rui Matos 2008-12-12 01:45:29 UTC
Here's some verbose output.

This is a Dell Latitude D630 with 8 levels of brightness. 7 is the maximum and I have the preference at 100%.

This log beggins with me setting the value to 4 from 7 and then waiting for the dimming. Then I move the mouse and brightness is set at full level again. Thus my direct instructions through the keyboard are ignored.

TI:01:31:32	TH:0x98a7660	FI:gpm-button.c	FN:gpm_button_filter_x_events,128
 - Key 232 mapped to key brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-button.c	FN:gpm_button_emit_type,88
 - emitting button-pressed : brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-manager.c	FN:button_pressed_cb,1000
 - Button press event type=brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-srv-screensaver.c	FN:button_pressed_cb,167
 - Button press event type=brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_button_pressed_cb,536
 - Button press event type=brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_get_hw,117
 - GetBrightness returned level: 4
TI:01:31:32	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_get_hw,117
 - GetBrightness returned level: 4
TI:01:31:32	TH:0x98a7660	FI:gpm-info.c	FN:button_pressed_cb,679
 - Button press event type=brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-button.c	FN:hal_device_condition_cb,392
 - condition=ButtonPressed, details=brightness-down
TI:01:31:32	TH:0x98a7660	FI:gpm-button.c	FN:gpm_button_emit_type,84
 - ignoring duplicate button brightness-down
TI:01:31:36	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=80, y=100, data=65280
TI:01:31:36	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=80, y=11, data=65280
TI:01:31:36	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=80, y=12632, data=65280
TI:01:31:41	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=85, y=100, data=65280
TI:01:31:41	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=85, y=11, data=65280
TI:01:31:41	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=85, y=12632, data=65280
TI:01:31:46	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=90, y=100, data=65280
TI:01:31:46	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=90, y=11, data=65280
TI:01:31:46	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=90, y=12632, data=65280
TI:01:31:51	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=95, y=100, data=65280
TI:01:31:51	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=95, y=11, data=65280
TI:01:31:51	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=95, y=12632, data=65280
TI:01:31:56	TH:0x98a7660	FI:gpm-screensaver.c	FN:gpm_screensaver_powersave_idle_changed,102
 - emitting powersave-idle-changed : (1)
TI:01:31:56	TH:0x98a7660	FI:gpm-idle.c	FN:powersave_idle_changed_cb,335
 - Received GS powesave idle changed: 1
TI:01:31:56	TH:0x98a7660	FI:gpm-idle.c	FN:gpm_idle_set_mode,98
 - Doing a state transition: 1
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_notify_system_idle_changed,624
 - we were active for 104,653605s
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_notify_system_idle_changed,627
 - changing powersave idle status to 1
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,379
 - 1. main brightness 1,000000
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,397
 - 2. battery scale 1,000000, brightness 1,000000
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,416
 - 3. idle scale 0,300000, brightness 0,300000
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,436
 - 4. ambient scale 1,000000, brightness 0,300000
TI:01:31:56	TH:0x98a7660	FI:gpm-brightness.c	FN:gpm_brightness_trust_cache,102
 - using cache for value 57 (probably okay)
TI:01:31:56	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_dim_hw,242
 - new_level_hw=2
TI:01:31:56	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_dim_hw_step,199
 - new_level_hw=2, last_set_hw=4
TI:01:31:56	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 4 of 7
TI:01:31:56	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 3 of 7
TI:01:31:56	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 2 of 7
TI:01:31:56	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,456
 - emitting brightness-changed : 30
TI:01:31:56	TH:0x98a7660	FI:gpm-info.c	FN:gpm_info_event_log,579
 - Adding 2 to the event log
TI:01:31:56	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f40, x=104, y=2, data=0
TI:01:31:56	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=100, y=100, data=65280
TI:01:31:56	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=100, y=11, data=65280
TI:01:31:56	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=100, y=12632, data=65280
TI:01:32:01	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=105, y=100, data=65280
TI:01:32:01	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=105, y=11, data=65280
TI:01:32:01	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=105, y=12632, data=65280
TI:01:32:04	TH:0x98a7660	FI:gpm-cell.c	FN:hal_device_property_modified_cb,273
 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0, key=battery.voltage.current, added=0, removed=0, finally=1
TI:01:32:06	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=110, y=100, data=65280
TI:01:32:06	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=110, y=11, data=65280
TI:01:32:06	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=110, y=12632, data=65280
TI:01:32:11	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6f70, x=115, y=100, data=65280
TI:01:32:11	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b6fa0, x=115, y=11, data=65280
TI:01:32:11	TH:0x98a7660	FI:gpm-array.c	FN:gpm_array_append,141
 - adding to 0x99b7020, x=115, y=12632, data=65280
TI:01:32:12	TH:0x98a7660	FI:gpm-screensaver.c	FN:gpm_screensaver_powersave_idle_changed,102
 - emitting powersave-idle-changed : (0)
TI:01:32:12	TH:0x98a7660	FI:gpm-idle.c	FN:powersave_idle_changed_cb,335
 - Received GS powesave idle changed: 0
TI:01:32:12	TH:0x98a7660	FI:gpm-idle.c	FN:gpm_idle_set_mode,98
 - Doing a state transition: 0
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_notify_system_idle_changed,596
 - we have just been idle for 16,219032s
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_notify_system_idle_changed,627
 - changing powersave idle status to 0
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,379
 - 1. main brightness 1,000000
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,397
 - 2. battery scale 1,000000, brightness 1,000000
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,416
 - 3. idle scale 1,000000, brightness 1,000000
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,436
 - 4. ambient scale 1,000000, brightness 1,000000
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness.c	FN:gpm_brightness_trust_cache,102
 - using cache for value 28 (probably okay)
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_dim_hw,242
 - new_level_hw=7
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_dim_hw_step,199
 - new_level_hw=7, last_set_hw=2
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 2 of 7
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 3 of 7
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 4 of 7
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 5 of 7
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 6 of 7
TI:01:32:12	TH:0x98a7660	FI:gpm-brightness-hal.c	FN:gpm_brightness_hal_set_hw,154
 - Setting 7 of 7
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_brightness_evaluate_and_set,456
 - emitting brightness-changed : 100
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_sync_policy,160
 - choosing sensible default
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_sync_policy,162
 - laptop, so use GPM_DPMS_METHOD_OFF
TI:01:32:12	TH:0x98a7660	FI:gpm-backlight.c	FN:gpm_backlight_sync_policy,194
 - BACKLIGHT parameters 0 0 540, method '4'
TI:01:32:12	TH:0x98a7660	FI:gpm-dpms.c	FN:x11_sync_server_dpms_settings,130
 - Syncing DPMS settings enabled=1 timeouts=0 0 0
TI:01:32:12	TH:0x98a7660	FI:gpm-manager.c	FN:idle_changed_cb,853
 - Idle state changed: NORMAL
TI:01:32:12	TH:0x98a7660	FI:gpm-info.c	FN:gpm_info_event_log,579
 - Adding 4 to the event log
Comment 7 Richard Hughes 2009-03-04 14:51:10 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.