keyboard shortcut ctrl-multimedia_key not running gnome-terminal

Bug #48255 reported by Vladimír Lapáček on 2006-06-03
18
Affects Status Importance Assigned to Milestone
Metacity
In Progress
Medium
metacity (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Hello,

I have a small problem with setting a keyboard shortcut in the gnome-keybinding-properties to run gnome-terminal. I am using Thinkpad R50e and I would like to fire the terminal with CTRL+Access IBM key. However, if I set it so nothing happens. I would suppose that it is because the Access IBM key is not recognized but if I set this shortcut for anything else e.g. web browser it works perfectly.

Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use? What event xev generates for that keyboard combinaison?

Changed in control-center:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Vladimír Lapáček (vil) wrote :

I am using current Dapper. xev gives me the following output for pressing this combo:

KeyPress event, serial 26, synthetic NO, window 0x3600001,
    root 0x4c, subw 0x0, time 2663910527, (384,260), root:(394,325),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 29, synthetic NO, window 0x3600001,
    root 0x4c, subw 0x0, time 2663910976, (384,260), root:(394,325),
    state 0x4, keycode 159 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x4c, subw 0x0, time 2663910976, (384,260), root:(394,325),
    state 0x4, keycode 159 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x4c, subw 0x0, time 2663911228, (384,260), root:(394,325),
    state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:

Sebastien Bacher (seb128) wrote :

That's probably a duplicate of the upstream "using multimedia keys for non-multimedia actions doesn't work fine" which exists for ages. According to the bug flow we get and the number of people working on it and interested on the keyboard issues that bug will probably not be worked soon

Changed in control-center:
status: Needs Info → Unconfirmed
Vladimír Lapáček (vil) wrote :

Could you please show me which upstream bug it is? I am just currious ;) Thanks

Sebastien Bacher (seb128) wrote :

I didn't find one matching exactly that one with some quick queries on bugzilla but I know that's a known issue for ages now (since acme, which is the code for multimedia keys, has been merged to the shortcuts dialog probably)

Sebastien Bacher (seb128) wrote :

That action is managed by metacity and using ctrl-"multimedia-key" doesn't work, I've forwarded the bug upstream: http://bugzilla.gnome.org/show_bug.cgi?id=409800

Changed in control-center:
status: Unconfirmed → Confirmed
Changed in metacity:
status: Unknown → In Progress
Duncan Lithgow (duncan-lithgow) wrote :

I am having the same issue trying to assign the windows key on my HP dv8220ea to run a terminal. Is this the same bug? SUPER_L isn't really a media key - and it worked in Feisty (now running Gutsy)

Duncan Lithgow (duncan-lithgow) wrote :

Or could I be seeing bug #12153? "Keyboard > keyboard settings > Alt/win" is set to default (Super is mapped to the win-keys).

Changed in metacity (Ubuntu):
status: Confirmed → Triaged
Changed in metacity:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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