263109 2011-01-14 08:30:41 +0000 Calculator key is wrongly recognized as "Launch (1)" 2012-02-18 14:05:12 +0000 1 1 10 Unmaintained khotkeys general 0.4 Arch Linux Linux RESOLVED DUPLICATE 257900 NOR normal --- 1 maarizwan kde bugs+kde burek021 leonardopl Tanktalus wstephenson 20 oldest_to_newest 1072973 0 maarizwan 2011-01-14 08:30:41 +0000 Version: 0.4 (using KDE 4.5.5) OS: Linux I want to bind speedcrunch to Calculator key on my multimedia keyboard. But when I assign "calculator" key, I see "Launch (1)" instead of "Calculator" key. Reproducible: Didn't try Steps to Reproduce: 1. open kmenuedit, assign 'calculator' key in the keyboard to any application. 2. though it takes the calculator key as 'launch (1)' but it won't work Actual Results: 3. assigned key doesn't work Expected Results: the application shortcut should have been launched by the assigned key. Solution: (which works for advanced users) at kde forum http://forum.kde.org/viewtopic.php?f=17&t=89602 ---herbiehancock wrote--- ~/.kde/share/config/kglobalshortcutsrc ~/.kde/share/config/khotkeysrc In both files I had to replace "Launch (1)" with "Calculator". Oddly enough I had to replace it with "Calculator", though the terminal application xev actually indicates the name "XF86Calculator" for that key. OS: Linux (i686) release 2.6.36-ARCH Compiler: gcc 1187891 1 wstephenson 2011-11-21 08:47:52 +0000 This is why it appears as 'Launch (1)' although it doesn't explain why it then doesn't work http://doc.qt.nokia.com/4.7/qt.html#Key-enum says: Qt::Key_Launch1 0x010000a3 On X11 this key is mapped to "Calculator" (XF86XK_Calculator) key for legacy reasons. Reproduced on openSUSE, not Arch specific 1228160 2 cfeck 2012-02-18 14:00:07 +0000 *** Bug 294318 has been marked as a duplicate of this bug. *** 1228163 3 cfeck 2012-02-18 14:00:30 +0000 *** Bug 293392 has been marked as a duplicate of this bug. *** 1228166 4 cfeck 2012-02-18 14:03:38 +0000 *** Bug 255329 has been marked as a duplicate of this bug. *** 1228168 5 cfeck 2012-02-18 14:05:12 +0000 *** This bug has been marked as a duplicate of bug 257900 ***