This is resolved by setting: "run_im none" in the $HOME/.xinputrc file (that can be done via the im-config command).
In other words, involved input methods eat that. It seems that the (involved) input systems use that for switching among particular input (sub)methods; I have found on an older (Xubuntu 14.04 LTS) system that e.g. ibus input method uses Control+space, with the same stuff (on Control+space here though) being seen at xev then. The ibus system at least shows a configuration in system tray where one can change the binding (and the main thing: to see that it is eaten by it), while I got no hint at Xubuntu 16.04 LTS (and not using any advanced input method). The eating of the Control+something is useless when not needing east- asia-centered input systems, and especially when there is no switching configured that the Control+something can be used for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713342 Title: Control+e does not generate key events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1713342/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
