Version: (using KDE 4.1.2) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled From Sources Keyboard shortcuts assigned in "SystemSettings -> Keyboard & Mouse -> Shortcuts" do only stay active in the current session. I have XF86Mute/VolUp/VolDown assigned to the front-channel in kmix and these settings work until I log off and log in again. When I open SystemSettings in a new session the commands are still being shown but they are not working. To activate them again you have to disable the shortcut, click "Apply" and then enable the shortcut again. BTW: The keycodes are being mapped to XF86Foo-commands by xmodmap in .bashrc. I don't know if that matters.
This seems to be related to bug 160892 (keyboard shortcuts broken in KDE 4.1.x)
I've also noticed that KHotkeys does not work at all. The "Print" key does not launch ksnapshot, even though this action es enabled by default. Also XF86Standby, XF86ScreenSaver, etc. are not even being recognized as inputs.
confirmed here. You should apply key mapping before KDE launching. And xmodmap should be assigned in X, not bash. You could put it in .xinitrc, here is mine: xmodmap ~/.Xmodmap synclient TouchpadOff=1 xbindkeys & setxkbmap -keycodes evdev -model evdev exec startkde If you assigned the key mapping in KDE, such as changed keyboard layout in KDE, the shortcuts in "SystemSettings -> Keyboard & Mouse -> Shortcuts" will be messed up. recently using hotplugging in xorg, we are suggest to use the keyboard layout "Evdev-managed keyboard", it caused the problems like this (look http://kdemod.ath.cx/bbs/viewtopic.php?id=1358 and http://bbs.archlinux.org/viewtopic.php?pid=457862). the reason is same, so I forbiden keyboard layout, and set it in .xinitrc (see above). I think the bug 160892 and http://forums.opensuse.org/archives/sls-archives/archives-suse-linux/archives-general-questions/371491-keyboard-layout-shortcut-question.html is caused by the same reason.
Has jackphils comment worked for everyone here or does this problem still exist? If yes please reply here. If not just do nothing. If i get no feedback in the next two weeks i will close that bug. Thanks Mike
I did not observe this problem in KDE 4.2! I think we can close the bug.
And yes, I figured that we cannot assign key-mappings through a statement in .bashrc or .bash_profile. I now use ~/.kde/env/ for adding some keys from my multimedia keyboard.
$ setxkbmap -print xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+hu:2+inet(evdev)+terminate(ctrl_alt_bksp)" }; xkb_geometry { include "pc(pc104)" }; };
Created attachment 40829 [details] "xkbcomp :0 -" output Just as the previous outputs this is under KDE4 where the Up key does not work.
(In reply to comment #7) > $ setxkbmap -print > > xkb_keymap { > xkb_keycodes { include "evdev+aliases(qwerty)" }; > xkb_types { include "complete" }; > xkb_compat { include "complete" }; > xkb_symbols { include > "pc+us+hu:2+inet(evdev)+terminate(ctrl_alt_bksp)" }; > xkb_geometry { include "pc(pc104)" }; > }; Sorry, this is meant for https://bugs.kde.org/show_bug.cgi?id=172411.
(In reply to comment #8) > Created an attachment (id=40829) [details] > "xkbcomp :0 -" output > > Just as the previous outputs this is under KDE4 where the Up key does not work. Sorry, this is meant for https://bugs.kde.org/show_bug.cgi?id=172411.