Hi,
I have a problem with a shortcut assignment : I would like to assign the shortcut Ctrl+² to "keep window above others".
I use an azerty keyboard. When I input the shortcut, kde makes as if I had input the following : Ctrl+`, and when I press Ctrl+², it does noting, but it works when i press Ctrl+` (witch is Ctrl+alt gr+7 in my french keyboard) . So i tried to get my Ctrl+² shortcut with "import sheme", but the shortcut doesn't work : it is correctly saved in kde shortcuts, but when i press it, it does noting.
Any idea ?

Does "xev" recognise the key correctly, and have you reassigned the shortcut to ensure it is recognising the same sets of keys?

This is what I get from xev for Ctrl+² :

Code: Select all

KeyPress event, serial 35, synthetic NO, window 0x2c00001,
    root 0xb9, subw 0x0, time 6283063, (456,770), root:(458,791),
    state 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 35, synthetic NO, window 0x2c00001,
    root 0xb9, subw 0x0, time 6283528, (456,770), root:(458,791),
    state 0x14, keycode 49 (keysym 0x60, grave), same_screen YES,
    XKeysymToKeycode returns keycode: 16
    XLookupString gives 1 bytes: (00) ""
    XmbLookupString gives 1 bytes: (00) ""
    XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x2c00001,
    root 0xb9, subw 0x0, time 6283687, (456,770), root:(458,791),
    state 0x14, keycode 49 (keysym 0x60, grave), same_screen YES,
    XKeysymToKeycode returns keycode: 16
    XLookupString gives 1 bytes: (00) ""
    XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x2c00001,
    root 0xb9, subw 0x0, time 6284120, (456,770), root:(458,791),
    state 0x14, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


and just for ² :

Code: Select all

KeyPress event, serial 35, synthetic NO, window 0x2c00001,
    root 0xb9, subw 0x0, time 6466752, (-470,709), root:(372,730),
    state 0x10, keycode 49 (keysym 0xb2, twosuperior), same_screen YES,
    XLookupString gives 2 bytes: (c2 b2) "²"
    XmbLookupString gives 2 bytes: (c2 b2) "²"
    XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x2c00001,
    root 0xb9, subw 0x0, time 6466904, (-475,726), root:(367,747),
    state 0x10, keycode 49 (keysym 0xb2, twosuperior), same_screen YES,
    XLookupString gives 2 bytes: (c2 b2) "²"
    XFilterEvent returns: False


have you reassigned the shortcut to ensure it is recognising the same sets of keys?

I am not sure what you mean. I tried others shortcuts, like Ctrl+&, and it works correctly. In fact, it is only the shortcut Ctrl+² which doesn't work.

That xev output appears to be valid and correct. By reassign I mean set that particular shortcut back to it's defaults, and then try to set it again.

I tried to reassign the shortcut (and reboot during the process), but it did not solve the problem.

Are you attempting to reconfigure a global or application shortcut? Also, is it possible there is another application running which is intercepting the key press and preventing KDE from reacting correctly?

I use xbindkeys for configuring my mouse, but not for the keyboard.
And I try to define a global shortcut thanks to
System setting -> Shortcuts and gestures -> Global keyboard shortcuts -> KDE component : KWin

I see. Unfortunately i'm not aware why that particular global shortcut could be assigned successfully, but not triggered.
It is quite possibly a bug in the global shortcut handling. If you wish, you could try assigning the key combination to an in-application shortcut and see if it works there.

I tried in a plugin for firefox, and Ctrl+² is detected as Ctrl+~, but it works fine.

Okay. Could you try in another KDE application, such as KWrite for instance?

With Kwrite, i get the same behavior than for general KDE shortcut.

Okay - this is a bug in the general KDE shortcut system then. Please file a bug report at bugs.kde.org. It is rather unusual Firefox misidentifies your keypresses though - that misrecognition could quite well be behind the failure of the KDE system to properly detect the shortcuts being activated.

Ok, thank you for your time.
I submit the bug : https://bugs.kde.org/show_bug.cgi?id=324488