https://bugs.kde.org/show_bug.cgi?id=365147
Dainius Masiliūnas <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #11 from Dainius Masiliūnas <[email protected]> --- Here's an interesting twist to this: I tend to bind my Windows key to COMPOSE via the keyboard KCM. So when I do Fn+F4 (the display button on my HP laptop), I actually get: KeyPress event, serial 40, synthetic NO, window 0x1200001, root 0xd5, subw 0x0, time 7890932, (788,550), root:(2162,579), state 0x0, keycode 133 (keysym 0xff20, Multi_key), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: True KeyPress event, serial 40, synthetic NO, window 0x1200001, root 0xd5, subw 0x0, time 7890938, (788,550), root:(2162,579), state 0x0, keycode 33 (keysym 0x70, p), same_screen YES, XLookupString gives 1 bytes: (70) "p" XmbLookupString gives 1 bytes: (70) "p" XFilterEvent returns: True KeyRelease event, serial 40, synthetic NO, window 0x1200001, root 0xd5, subw 0x0, time 7891049, (788,550), root:(2162,579), state 0x0, keycode 33 (keysym 0x70, p), same_screen YES, XLookupString gives 1 bytes: (70) "p" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x1200001, root 0xd5, subw 0x0, time 7892632, (788,550), root:(2162,579), state 0x0, keycode 133 (keysym 0xff20, Multi_key), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False If I press that in the shortcuts KCM, it just shows "p", and indeed binds just the letter "p" to mean switch display, and that's of course quite disastrous. If I unbind the COMPOSE key, then the shortcuts KCM indeed recognises the keypress as Meta+p. I don't suppose there's any way to deal with that apart from manually binding the display key to some other key combination... -- You are receiving this mail because: You are watching all bug changes.
