Bug 162801 - Default menu shortcuts get precedence over user shortcuts (using alt+<letter>).
Summary: Default menu shortcuts get precedence over user shortcuts (using alt+<letter>).
Status: RESOLVED DUPLICATE of bug 185788
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeui (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-29 13:31 UTC by Peter Rockai
Modified: 2010-08-31 04:51 UTC (History)
2 users (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 Peter Rockai 2008-05-29 13:31:13 UTC
In 4.1 beta 1, it appears that setting shortcuts to alt+<letter> has no effect 
(at least those overlapping with menu shortcuts, like alt+h).

Works fine in 3.5.9.

I am mostly guessing about the component, please move as appropriate.
Comment 1 Dario Andres 2008-12-26 15:31:59 UTC
Keyboard Shortcuts were reworked a lot for KDE4.2.

Here using:

Qt: 4.4.3
KDE: 4.1.86 (KDE 4.1.86 (KDE 4.2 >= 20081221))
kdelibs svn rev. 901624 / kdebase svn rev. 901624
on ArchLinux x86_64 - Kernel 2.6.27.10
I can select Alt+Letter for a global shortcut ( like launching KRunner) , and it works OK.

Can anyone else confirm this?
Comment 2 kiputnik 2009-08-15 20:40:30 UTC
Still unfixed as of KDE 4.3.
Also, bug 185788 is a duplicate of this one.

To those of you that miss the functionality from KDE 3 there is a workaround. It involves swapping your keys, so that Alt actually triggers Super and vice versa:
setxkbmap -model pc104
xmodmap -e 'remove mod1 = Alt_L'
xmodmap -e 'remove mod1 = Meta_L'
xmodmap -e 'remove mod4 = Super_L'
xmodmap -e 'keycode 64 = Super_L'
xmodmap -e 'keycode 133 = Alt_L'
xmodmap -e 'add mod1 = Alt_L'
xmodmap -e 'add mod4 = Super_L'

It has it's drawbacks, though. (Like, reconfiguring Alt+Tab to be actually Super+Tab)
Comment 3 Christoph Feck 2010-08-31 04:51:20 UTC

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