brightness up/down keys reported on two devices on dell 1505/6400

Bug #324357 reported by James Westby
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

bug 207473 and bug 257827 look similar, but different things used to be blamed.

The issue here is that both the keyboard and the video driver report events for the
brightness hotkeys, leading to the brightness changing in double steps.

% sudo input-events 4
/dev/input/event4
   bustype : BUS_I8042
   vendor : 0x1
   product : 0x1
   version : 43841
   name : "AT Translated Set 2 keyboard"
   phys : "isa0060/serio0/input0"
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

waiting for events
15:55:19.620127: EV_MSC code=4 value=28
15:55:19.620152: EV_KEY KEY_ENTER released
15:55:19.620158: EV_SYN code=0 value=0
15:55:21.363426: EV_MSC code=4 value=133
15:55:21.363452: EV_KEY KEY_BRIGHTNESSDOWN pressed
15:55:21.363458: EV_SYN code=0 value=0
15:55:21.363464: EV_KEY KEY_BRIGHTNESSDOWN released
15:55:21.363468: EV_SYN code=0 value=0
15:55:22.417706: EV_MSC code=4 value=134
15:55:22.417730: EV_KEY KEY_BRIGHTNESSUP pressed
15:55:22.417735: EV_SYN code=0 value=0
15:55:22.417741: EV_KEY KEY_BRIGHTNESSUP released
15:55:22.417745: EV_SYN code=0 value=0
15:55:23.359260: EV_MSC code=4 value=133
15:55:23.359287: EV_KEY KEY_BRIGHTNESSDOWN pressed
15:55:23.359293: EV_SYN code=0 value=0
15:55:23.359299: EV_KEY KEY_BRIGHTNESSDOWN released
15:55:23.359303: EV_SYN code=0 value=0
15:55:24.257676: EV_MSC code=4 value=29
15:55:24.257702: EV_KEY KEY_LEFTCTRL pressed
15:55:24.257708: EV_SYN code=0 value=0
^C
% sudo input-events 6
/dev/input/event6
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x6
   version : 0
   name : "Video Bus"
   phys : "/video/input0"
   bits ev : EV_SYN EV_KEY

waiting for events
15:55:27.387925: EV_KEY KEY_BRIGHTNESSDOWN pressed
15:55:27.387946: EV_SYN code=0 value=0
15:55:27.387953: EV_KEY KEY_BRIGHTNESSDOWN released
15:55:27.387957: EV_SYN code=0 value=0
15:55:28.484491: EV_KEY KEY_BRIGHTNESSUP pressed
15:55:28.484509: EV_SYN code=0 value=0
15:55:28.484515: EV_KEY KEY_BRIGHTNESSUP released
15:55:28.484520: EV_SYN code=0 value=0
15:55:29.566762: EV_KEY KEY_BRIGHTNESSDOWN pressed
15:55:29.566780: EV_SYN code=0 value=0
15:55:29.566786: EV_KEY KEY_BRIGHTNESSDOWN released
15:55:29.566790: EV_SYN code=0 value=0
^C

Linux flash 2.6.28-6-generic #17-Ubuntu SMP Fri Jan 30 15:34:36 UTC 2009 i686 GNU/Linux

Ubuntu 2.6.28-6.17-generic

Thanks,

James

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Lsusb:
 Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux-image-2.6.28-6-generic 2.6.28-6.17
ProcCmdLine: root=UUID=ff3ea5fb-6c4f-4709-88d1-a28e90a377e3 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.28-6.17-generic
SourcePackage: linux

Revision history for this message
James Westby (james-w) wrote :
Revision history for this message
James Westby (james-w) wrote :

Assigning to Andy so he can review.

Thanks,

James

Changed in linux:
assignee: nobody → apw
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi James,

Just curious if this issue remains with Jaunty's final release for you? Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
James Westby (james-w) wrote :
Download full text (3.2 KiB)

Hi,

The problem still exists, but it has moved to a different index

jw2328@flash:/tmp/gnome-power-manager-2.26.1:10018:130% sudo input-events 4
/dev/input/event4
   bustype : BUS_I8042
   vendor : 0x1
   product : 0x1
   version : 43841
   name : "AT Translated Set 2 keyboard"
   phys : "isa0060/serio0/input0"
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

waiting for events
22:36:12.228463: EV_MSC code=4 value=28
22:36:12.228480: EV_KEY KEY_ENTER (0x1c) released
22:36:12.228483: EV_SYN code=0 value=0
22:36:13.021178: EV_MSC code=4 value=133
22:36:13.021197: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed
22:36:13.021200: EV_SYN code=0 value=0
22:36:13.021203: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) released
22:36:13.021206: EV_SYN code=0 value=0
22:36:13.064118: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed
22:36:13.064137: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) released
22:36:13.452761: EV_MSC code=4 value=134
22:36:13.452779: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed
22:36:13.452782: EV_SYN code=0 value=0
22:36:13.452785: EV_KEY KEY_BRIGHTNESSUP (0xe1) released
22:36:13.452788: EV_SYN code=0 value=0
22:36:13.500955: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed
22:36:13.500972: EV_KEY KEY_BRIGHTNESSUP (0xe1) released
22:36:13.913018: EV_MSC code=4 value=29
22:36:13.913038: EV_KEY KEY_LEFTCTRL (0x1d) pressed
22:36:13.913042: EV_SYN code=0 value=0
22:36:14.169892: EV_MSC code=4 value=29
22:36:14.169913: EV_KEY KEY_LEFTCTRL (0x1d) pressed
22:36:14.169917: EV_SYN code=0 value=0
22:36:14.200712: EV_MSC code=4 value=29
22:36:14.200735: EV_KEY KEY_LEFTCTRL (0x1d) pressed
22:36:14.200740: EV_SYN code=0 value=0
22:36:14.231532: EV_MSC code=4 value=29
22:36:14.231557: EV_KEY KEY_LEFTCTRL (0x1d) pressed
22:36:14.231561: EV_SYN code=0 value=0
22:36:14.262379: EV_MSC code=4 value=29
22:36:14.262404: EV_KEY KEY_LEFTCTRL (0x1d) pressed
22:36:14.262407: EV_SYN code=0 value=0
22:36:14.272831: EV_MSC code=4 value=46
22:36:14.272855: EV_KEY KEY_C (0x2e) pressed
22:36:14.272858: EV_SYN code=0 value=0
22:36:14.344756: EV_MSC code=4 value=46
22:36:14.344778: EV_KEY KEY_C (0x2e) released
22:36:14.344782: EV_SYN code=0 value=0
^C
jw2328@flash:/tmp/gnome-power-manager-2.26.1:10019:130% sudo input-events 5
/dev/input/event5
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x6
   version : 0
   name : "Video Bus"
   phys : "/video/input0"
   bits ev : EV_SYN EV_KEY

waiting for events
22:36:16.976130: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed
22:36:16.976145: EV_SYN code=0 value=0
22:36:16.976148: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) released
22:36:16.976151: EV_SYN code=0 value=0
22:36:17.316073: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed
22:36:17.316087: EV_SYN code=0 value=0
22:36:17.316091: EV_KEY KEY_BRIGHTNESSUP (0xe1) released
22:36:17.316093: EV_SYN code=0 value=0
22:36:18.027509: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed
22:36:18.027522: EV_SYN code=0 value=0
22:36:18.027526: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) released
22:36:18.027528: EV_SYN code=0 value=0
22:36:18.303346: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed
22:36:18.303359: EV_SYN code=0 value=0
22:36:18.303363: EV_KEY KEY_BRIGHTNESSUP (0xe1) released...

Read more...

Andy Whitcroft (apw)
Changed in linux (Ubuntu):
assignee: Andy Whitcroft (apw) → nobody
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.