Version: unspecified (using KDE 4.6.3) OS: Linux If I create a new shortcut, it will not work if the key's name is XF86WWW or XF86Launch1, ... ; but it will if it's XF86Terminal or XF86Launch0 (for instance) Reproducible: Always Steps to Reproduce: Systemsettings > Shortcuts & Gestures > Custom Shortcut Edit > New > Global Shortcut > Command/URL - Action : kwrite (for the example) - Trigger ==> I use a special key (multimedia key) of my keyboard The name of that key is defined in a xmodmap file (it is mandatory, otherwise it is not recognized at all) : => the file ~/.xmodmap.kde contains "keycode 195 = XF86WWW" => I run "xmodmap .xmodmap.kde" at KDE startup Actual Results: In the "Trigger" window, the key "WWW" is displayed ==> the key seems recognized ; however, after applying the modification the shortcut doesn't work ! If I try another name for the key (file .xmodmap.kde modified): => it will work with -> XF86Terminal -> XF86Launch0 -> XF86Launch3 -> XF86Launch8 -> etc... => it will NOT work with -> XF86Mail -> XF86Launch1 -> XF86Launch2 -> XF86Launch5 -> etc... Expected Results: Should work whatever the key's name ! rem: it's weird that for instance XF86Launch3 works but NOT XF86Launch5 ??? What the difference ?? rem: the key's names that worked or not were different with my previous installation (Fedora 14 instead of 15), although it was also KDE 4.6.3
Could not replicate using 4.6.2.
Which additional info can I give to help to pinpoint the problem ? (log file, ... ?)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Sorry, I'm not able to test anymore, I have a new keyboard since my last comment in 2011. (I have no problem with my new keyboard)
Thanks for the update!