after turning brightness off gpm does not respond to brightness up

Bug #147772 reported by Brian Murray on 2007-10-01
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)

Bug Description

Binary package hint: gnome-power-manager

I discovered that is possible to lower the brightness on my laptop, an HP DV6245US, using the brightness down key, Fn+F7, until a point where the brightness is zero or off. After which pressing the brightness up key, Fn+F8, does not increase the brightness of the screen back thereby rendering my session unusable. I think the brightness level should stop before it turns off.

It is possible to workaround this issue by switching to a different vty, Ctrl+Alt+F1, and then back to my desktop session by pressing Ctrl+Alt+F7. The brightness has then been restored to a normal level.

gnome-power-manager version 2.21.1-0ubuntu1

description: updated
Oliver Grawert (ogra) wrote :

could you check if you see the same:
g_value_set_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed
as in the log of the first comment in bug 136346 ?

Brian Murray (brian-murray) wrote :

09:43 < ogra> bdmurray, run gpm with --no-daemon --debug and redirect the
              output somewhere

Brian Murray (brian-murray) wrote :

I do see the same 'g_value_set_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed' message when running 'gnome-power-manager --no-daemon --debug power'.

description: updated
Brian Murray (brian-murray) wrote :

The attached log file contains gpm debug information from the following test case:

1) reduce brightness to zero
2) wait a bit
3) try to increase brightness - nothing happened
4) switch to tty1 and switch to X

Step 4 occurs at line 508 in attached file.

Brian Murray (brian-murray) wrote :

Using gnome-power-manager version 2.24.0-0ubuntu8 from Intrepid I am no longer able to lower the brightness to a point where the screen is no longer visible so I am setting the bug's status to Invalid.

Changed in gnome-power-manager:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments