Bug 237614 - Unable to use Meny key in shortcuts
Summary: Unable to use Meny key in shortcuts
Status: RESOLVED DUPLICATE of bug 165542
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: shortcuts (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-14 13:39 UTC by Magnus Johansson
Modified: 2011-12-21 22:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Johansson 2010-05-14 13:39:44 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian stable Packages

In Mepis 8.0 using KDE 3.5.10 I was able to create keyboard shortcuts including the Menu key, e.g. opening the K menu with Ctrl+Menu. This is not possible in Mepis 8.5 using KDE 4.3.4.
Comment 1 Thomas Lübking 2010-05-14 17:52:07 UTC
what is the menu key? 

keycode 115 ("mod4" the key between left ctrl and alt, probably has a windows logo) is a meta key (iirc always has been)
you'll have to eg. modmap it to another key (like F13, as you probably don't have F13-F20) if you want to use it as full key

try "xmodmap -e "keycode 115 = F13", then try assign this key to whatever. (you can automize this via eg. ~/.kde/share/autostart/
add a file "xprofile.desktop"

-- snip --
[Desktop Entry]
Exec=/bin/sh $HOME/.xprofile
#Hidden=true
Name=xprofile
Type=Service
X-KDE-StartupNotify=false
X-KDE-autostart-phase=0
-- end snip --

and "$HOME/.xprofile"
containing the above command or
xmodmap ~/.Xmodmap (which you'll have to fill with the required aliases, at least "keycode 115 = F13" (w/o the quotes)
Comment 2 Magnus Johansson 2010-05-14 23:40:17 UTC
Thomas, the Menu key has a small image of a drop-down menu and a mouse pointer arrow on it, and the key is most often placed to the left of the right Ctrl key. Its key code is 117.
Comment 3 Thomas Lübking 2010-05-15 00:47:45 UTC
... and keysym 0xff67, you're right.
Qt seems to (internally) bind it to the context event (ie. you get the rmb instead, i was not able to add it by editing kglobalshortcutsrc)
Comment 4 Magnus Johansson 2010-05-21 09:56:00 UTC
(In reply to comment #3)
> ... and keysym 0xff67, you're right.
> Qt seems to (internally) bind it to the context event (ie. you get the rmb
> instead, i was not able to add it by editing kglobalshortcutsrc)

Would you report it as a bug to the Qt developers?
Comment 5 Martin Flöser 2010-05-23 16:34:09 UTC
definately not a kwin bug. I hope I found the correct product/component combination (is there a cheat sheet?). If not please assign to correct one.
Comment 6 Christoph Feck 2011-12-21 22:35:01 UTC

*** This bug has been marked as a duplicate of bug 165542 ***