Hot Keys Issue - Lenovo T500

Bug #368989 reported by Charles Profitt
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Information gathered at the request of slangseek per - https://wiki.ubuntu.com/Hotkeys/Troubleshooting
-----
xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'

keycode 36 = (keysym 0xff0d, Return), state = 0x10
keycode 122 = (keysym 0x1008ff11, XF86AudioLowerVolume), state = 0x10
keycode 122 = (keysym 0x1008ff11, XF86AudioLowerVolume), state = 0x10
keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x10
keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x10

note: keycode36 was not the result of a keypress, 122 was volume down and 123 volume up. There was no result for mute.
-----
hal-find-by-capability --capability input | xargs -n1 lshal -u | grep info.product
udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_4'
  button.has_state = true (bool)
  button.state.value = true (bool)
  button.type = 'radio' (string)
  info.addons.singleton = {'hald-addon-input'} (string list)
  info.callouts.add = {'hal-setup-keymap', 'debian-setup-keyboard'} (string list)
  info.capabilities = {'input', 'input.keys', 'input.switch', 'button', 'input.keymap'} (string list)
  info.category = 'input' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  info.product = 'ThinkPad Extra Buttons' (string)
  info.subsystem = 'input' (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_logicaldev_input_4' (string)
  input.device = '/dev/input/event9' (string)
  input.keymap.data = {'0x01:screenlock', '0x02:battery', '0x03:sleep', '0x04:radio', '0x06:switchvideomode', '0x07:f22', '0x08:f24', '0x0b:suspend', '0x0f:brightnessup', '0x10:brightnessdown', '0x11:kbdillumtoggle', '0x13:zoom', '0x14:volumeup', '0x15:volumedown', '0x16:mute', '0x17:prog1'} (string list)
  input.product = 'ThinkPad Extra Buttons' (string)
  input.x11_driver = 'evdev' (string)
  input.xkb.layout = 'us' (string)
  input.xkb.model = 'pc105' (string)
  input.xkb.rules = 'evdev' (string)
  linux.device_file = '/dev/input/event9' (string)
  linux.hotplug_type = 2 (0x2) (int)
  linux.subsystem = 'input' (string)
  linux.sysfs_path = '/sys/devices/virtual/input/input9/event9' (string)
-----
sudo input-events 9 resulted in no events
-----
acpi_listen resulted in no events
-----
contents of /sys/devices/platform/thinkpad_acpi/hotkey_mask:
0x038c7fff
----

I have attached a zip file with the requested files

Tags: hotkeys
Revision history for this message
Charles Profitt (cprofitt) wrote :
Revision history for this message
Charles Profitt (cprofitt) wrote :

Assigned to vorlon per his request

Changed in linux (Ubuntu):
assignee: nobody → vorlon
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Charles Profitt (cprofitt) wrote :

The behavior is:

volume up and volume down result in the OSD pop-up being displayed and the volume going up and down. Mute does not result in any OSD nor the volume icon in the upper panel showing mute, but sound is muted.

Revision history for this message
Steve Langasek (vorlon) wrote :

Charles,

Do you see these events when you run sudo input_events against the main keyboard device instead of the hotkeys device (device #4 in the tarball you attached, though this may change on each reboot)?

Recent Thinkpads are said to handle volume buttons differently than older models (cf. http://mjg59.livejournal.com/110870.html), which could explain why the volume up/down keys are behaving the way you describe, but doesn't explain why the mute button is inactive.

Changed in linux (Ubuntu):
assignee: Steve Langasek (vorlon) → nobody
Revision history for this message
Timothy Pearson (kb9vqf) wrote :

This is also an issue on the ThinkPad T400 series, which has identical mixer hardware AFAIK.

Revision history for this message
Aristid Breitkreuz (aristid-breitkreuz) wrote :

The bug is particularly annoying because pressing mute twice does NOT unmute. You need to press volume-up or volume-down to reenable sound. Nor does any mixer device even notice that sound is muted.

Revision history for this message
TomasHnyk (sup) wrote :

Steve: the output if input_events pasted below:

volume-up and volume-down are reported correctly, mute is not, also power button does not get reported.

drew@steve:~$ sudo input-events 4
/dev/input/event4
   bustype : BUS_I8042
   vendor : 0x1
   product : 0x1
   version : 43860
   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:24:12.989796: EV_MSC code=4 value=174
15:24:12.989820: EV_KEY KEY_VOLUMEDOWN (0x72) pressed
15:24:12.989826: EV_SYN code=0 value=0
15:24:13.053871: EV_MSC code=4 value=174
15:24:13.053898: EV_KEY KEY_VOLUMEDOWN (0x72) released
15:24:13.053904: EV_SYN code=0 value=0
15:24:13.549428: EV_MSC code=4 value=176
15:24:13.549453: EV_KEY KEY_VOLUMEUP (0x73) pressed
15:24:13.549458: EV_SYN code=0 value=0
15:24:13.588939: EV_MSC code=4 value=176
15:24:13.588967: EV_KEY KEY_VOLUMEUP (0x73) released
15:24:13.588974: EV_SYN code=0 value=0

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.