Samsung Q210 - No "released" events on brightness change

Bug #393240 reported by Stephen Brandwood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal-info (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: hal-info

In reply to the original bug report:

https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/333352

The brightness keys make the brightness go up and down, but when using input-events, there is no "released" event for either key:

21:36:42.979320: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed
21:36:42.979325: EV_SYN code=0 value=0
21:36:43.266034: EV_MSC code=4 value=137
21:36:43.266064: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed
21:36:43.266068: EV_SYN code=0 value=0
21:36:43.619331: EV_MSC code=4 value=176

The result, is that when the brightness is turned down, it goes right down to zero or vise versa. The keyboard then becomes locked and I need to switch to the console and back to the desktop to fix it.

Thanks

Revision history for this message
Stephen Brandwood (sbrandwoo) wrote :

I now notice that a single press of FN + Brightness Up/Down is changing the brightness 1 notch, but only on the On Screen Display that appears in the top right of the screen, the brightness itself does not change! input-events is not showing any new release events now, making this problem slighty intermitent.

I tried acpi_listen and nothing interesting appeared to happen.

So:
 - No released events with input-events
 - Intermittent problem where brightness key appears to be un-released, locking keyboard and forcing brightness OSD to extreme low/high.
 - Brightness of screen never changes.

Any ideas?

(Samsung Q210 with Ubuntu 9.04)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.