Keyboard shortcut setting from USB headphones problematic

Bug #76289 reported by Chris Boyle
2
Affects Status Importance Assigned to Milestone
control-center (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

I have Speed-Link SL-8795 headphones with buttons on a mid-cable block; two of these buttons (marked VOL- and VOL+) show up as a USB input device. When I try to assign these to "Play (or play/pause)" and "Skip to next track" respectively, they show up as 0xae and 0xb0 and function properly (modulo a restart of some applications) but if I logout and login again, this state is not restored properly. The settings appear as I left them, but the buttons do nothing. Setting them again makes them work for the rest of that session; I must do this on each login.

It may also be relevant (and may merit splitting to a new bug) that whenever the settings appear as 0xae and 0xb0 and are working (i.e. I have set them during this session), setting them again makes them appear as XF86AudioPlay and XF86AudioNext and stop working. Further attempts to set them will toggle between these two states (hex codes and working vs names and not working).

Tags: keyboard
Revision history for this message
Chris Boyle (cmb) wrote : Version information

Ubuntu 6.10 Edgy Eft, up to date as of 18/12/2006 15:30.

ii gnome-control-center 2.16.1-0ubuntu4 utilities to configure the GNOME desktop
ii xserver-xorg 7.1.1ubuntu6.2 the X.Org X server

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. The value switching between hexcode and label is a known bug. Could you try to run "xev" and note the key event displayed when pressing the buttons when it doesn't work and when it works? Do you plug your headphone before or after login?

Changed in control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Chris Boyle (cmb) wrote : Re: [Bug 76289] Re: Keyboard shortcut setting from USB headphones problematic

Not working, VOL-
KeyPress event, serial 40, synthetic NO, window 0xa00001,
    root 0x118, subw 0x0, time 2867322592, (160,-16), root:(165,35),
    state 0x0, keycode 174 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

Not working, VOL+
KeyPress event, serial 40, synthetic NO, window 0xa00001,
    root 0x118, subw 0x0, time 2867355260, (177,-25), root:(182,26),
    state 0x0, keycode 176 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

Working, VOL-
KeyPress event, serial 36, synthetic NO, window 0xa00001,
    root 0x118, subw 0x0, time 2867047139, (159,-18), root:(164,33),
    state 0x0, keycode 174 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

Working, VOL+
KeyPress event, serial 36, synthetic NO, window 0xa00001,
    root 0x118, subw 0x0, time 2867048547, (159,-18), root:(164,33),
    state 0x0, keycode 176 (keysym 0x1008ff17, XF86AudioNext), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

I connect the headphones before login and leave them connected for days at a
time. Disconnecting and reconnecting while logged in does not change the state
(I tested both states).

--
Chris Boyle
http://cmb.is-a-geek.org/

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for the reply, marking unconfirmed again and adding a keyboard tag, it'll probably take some time before having somebody looking at that problem, it looks like few people have interest or knowledge to reply on those multimedia key bugs at the moment

Changed in control-center:
status: Needs Info → Unconfirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still get the issue in hardy or intrepid?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in control-center:
status: New → Invalid
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.