Version: (using KDE KDE 3.1) Installed from: Mandrake RPMs I'm using the Win-key as a META modifier, to define some windows shortcuts based on the key (such as Win-1, Win-2 etc.). To make the key to work as a modifier (instead of F13), I used KControl->Accessibility->KeyboardLayout->Alt/Win to choose the "Meta is mapped to the Win-keys". This works fine, but once the machine is rebooted, the binding is lost, and I have to go and select the option again. In addition, it all is a bit confusing since the "Accessibility->"Keyboard Shortcuts"->"KDE Modifiers" shows that the "Win" KDE modifier is not bound to anything.
Bug 57039 From: Alex Gontmakher <gsasha@cs.technion.ac.il> To: pupeno@kde.org Date: 2003-06-26 19:27 Hi, I seem to be unable to change the bug info in Bugzilla, so I'm sending this to you as the person assigned for this bug. I think that I have traced down the reason for the problem. What happens is that the program /usr/bin/test-windows-key, called from startkde, changes the mapping of Win-key to F13. The program kxkb is able to restore the mapping. The solution is, therefore, either to avoid calling test-windows-key, or to call kxkb after test-windows-key in startkde. Regards, Alex
I can reproduce this bug with KDE HEAD, but I cannot find the call to /usr/bin/test-windows-key in the startkde script. I'm not sure what the test-windows-key program is supposed to do (I cannot find it on my computer). Maybe the test-windows-key program is specific to your distribution? Anyway, this is not a bug in kcmaccessibility, but in the KCM of kxkb -- or in the code that special cases the win key (which also breaks the sticky keys feature in kcmaccess, btw).
kxkb by itself does not handle win key (or any other key if you don't ask it to) please try to disable xkb options in kxkb, restart kde and see if it helps, if it does not try to disable kxkb altogether, restart kde and see if it helps 1) if it does not, the kxkb has nothing to do with it 2) if turning xkb options off helps just have it disabled 3) if turning kxkb off helps then it means that setting one of your layouts resets your win key configuration, then we probably have to look for some solution
Can't reproduce it with pre-3.5.2