Version: (using Devel) Installed from: Compiled sources Compiler: GCC 4.2.2 OS: Linux When I set special keys (multimedia keys on my keyboard, XF86VolumeMute, etc., KDE refers to them as "Volume Mute", "Volume Down", "Volume Up", "Media Next") in systemsettings (Keyboard & Mouse config), they get written to kglobalshortcutsrc. When I log out and back in, and check systemsettings, the keys are no longer set. Only the special keys (not normal modifier+character) that I set are set to nothing. The config file contains the keys. I set the Immutable attribute on it so that it could not be modified, after i set my keys, and logged out and back in. While the keys were still listed in the file, they were not shown in systemsettings. If i export the key profile and import it after login, the keys are set again. They work after being set until I log out and back in; my X keymap is modified by a script I have in Autostart (set to "Pre-KDE Startup") to include the keycodes for those keys.
Importing the keymap also allows my Up/Down arrows to work.
*** Bug 165065 has been marked as a duplicate of this bug. ***
*** Bug 165104 has been marked as a duplicate of this bug. ***
It looks like Hotkeys for keys that "don't exist" when the Session starts are deactivated. I copied my .Xmodmap to /etc/X11/Xmodmap and added a line to /usr/share/config/kdm/Xstartup to make sure it gets loaded. My hotkeys now work across logins. It would be nice if KDE would load the .Xmodmap automatically before the rest of the session is started ...
I can set up the multimedia keys to handle the Amarok (Play/Pause, Next, Previous, Stop) and those work as expected when the Amarok window is opened and focused. While amarok is only in the systray, these keys have no effect, which sucks a bit, because it used to work in KDE 3.x.
Hi Andriy The problem seems to be that kxkb's kdeinit demon is started to late during kde startup. Could you check with Lubos if it is possible to start it sooner? <debase-workspace/kcontrol/kxkb kcontrol/kxkb/kxkb.desktop Mike
Hi Michael, I am not sure why kxkb should be started sooner. Could you please explain? Thanks, Andriy
Please check again with a recent trunk. Should work there.
Should be fixed. If not reopen please.