Version: 2.1 (using KDE 3.5.6, Debian Package 4:3.5.6.r1.dfsg.1-2 (4.0)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.20.1-slh-smp-2 My keyboard has some special keys which I define with xmodmap through a bash-script in ~/.kde/Autostart: # Logitech Wireless Keyboard EX 110 xmodmap -e 'keycode 234=F21' #back xmodmap -e 'keycode 162=F22' #play xmodmap -e 'keycode 164=F23' #stop and so on. In kcontrol's hotkey section I have defined a group "special keys" and defined actions for all of those keys, like starting amarok, kjots and so on. Everything works fine in KDE 3.5.5. But now that I have updated to KDE 3.5.6 those keys don't work anymore: I can use them in the hotkeys section to define actions (which means they are recognized) but when I pressing the keys no applications start, nothing happens. Actions for keys not defined through xmodmap do work.
I have the same problem. At first I thought it was my keyboard because during the update the batteries of the keyboard gave up and after I replaced them the extra keys didn't work anymore. But I have tested it with another installation (same distribution, Debian Sid), with KDE 3.5.5 everything works. I also use xmodmap to define the extra keys.
I am having a similar problem but with a Sun keyboard. I have the extra UNIX keys mapped but KDE will not accept many of them. It will not accept SunCopy, SunPaste, SunCut, Undo, Redo, etc. when setting Application Shortcuts. It does work, however, for the global shortcuts. Also, I am able to map the Find key and Stop key.
For me the problem seems to be solved with KDE version 3.5.6.dfsg.2-2, I now can use the keys again.
Is this still an issue in 4.2?
This is definitely a problem in 4.2, even worse than 3.5.10. I am using a Sun USB type 6 keyboard for my PC and on 3.5.x I was able to map some of the keys, i.e. front, volume-, volume+, etc. In 4.2 I am unable to map keys like "find" and a dialog pops up saying "The key you pressed isn't supported by Qt." I get this, for example, when I try and map Find (keycode 122). xev reports the key properly.
Ok, then this is a Qt bug, and we need a nice little testcase written up to send to their bug people.
I don't know if this is related, but I just found that xmodmap + kde shortcuts don't work very well. I want to use xmodmap to completely remap my laptop keyboard (to a Dvorak-like layout). There's no issue with the remapping, but afterwards my global KDE shortcuts stop to work. If you want to reproduce: 1. Assign Alt+A to a global shortcut (for example, switch desktop) 2. Map another key to 'A' (xmodmap -e 'keycode 67 = a' maps F1 to a) 3. Hit Alt+F1. It doesn't work. However, pressing F1 inputs 'a', as expected. I thought this was a KDE4 bug because I haven't had any problems before. Then I realized that I use a Dvorak keyboard (well, you can switch between QWERTY and Dvorak), so I haven't remapped very much on my KDE 3.5.7 computer. -- To summarize: - Global shortcuts don't work with keys remapped with xmodmap. - I can reproduce this in KDE 3.5.7 and KDE 4.2. - I don't get dialogs or anything. It just doesn't work. - It seems like normal shortcuts (not global) work fine with remapped keys.
*** Bug 183726 has been marked as a duplicate of this bug. ***
Shouldn't this now be assigned to some other application than kcontrol?
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Kcontrol has been replaced by System Settings in Plasma. Please give the latest version of that a try, and open a new bug in "systemsettings" if you continue to have an issue. Thank you!