Thanks for fixing this, Sebastien! When I saw your oneliner in the queue, I did some tests. Without having your ibus-fix in place, I opened gnome-language-selector, selected "none" instead of "IBus", and re-logged in. That disables im-config's variable settings, and only the IM related variables which GNOME sets by default are present:
$ env | grep -E 'XMOD|_IM' QT_IM_MODULE=ibus XMODIFIERS=@im=ibus And it made Ctrl+Shift+U work. These are the variables with im-config enabled: $ env | grep -E 'XMOD|_IM' CLUTTER_IM_MODULE=xim QT4_IM_MODULE=xim QT_IM_MODULE=ibus XMODIFIERS=@im=ibus GTK_IM_MODULE=ibus I also tried to just edit ~/.profile and add: unset GTK_IM_MODULE That proved to be sufficient to bring Ctrl+Shift+U back. I'm not able to tell the significance of setting GTK_IM_MODULE to "ibus", but that's what we currently do through im-config, and Ubuntu is the only distro AFAIK which installs im-config by default. So the issue is kind of Ubuntu specific, and now we have an Ubuntu specific ibus- patch. My first reaction was to try to convince upstream to change their mind. I'm not as sure about that now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1760308 Title: Unicode input not working on Bionic with CTRL-SHIFT-U Status in ibus: Unknown Status in ibus package in Ubuntu: Fix Committed Status in ibus source package in Bionic: Fix Committed Bug description: I need to enter Unicode with Unicode escape codes and the Ubuntu prescribed way is to use CTRL-SHIFT-U and then enter some numbers to input. This doesn't do anything in the Ubuntu Bionic beta. Potentially related the ALT-TAB window switching is delayed in recognizing the occurrence of the keys being pressed such that I have to hold ALT-TAB instead of quickly hitting both simultaneously. This is from a system that was upgraded from a previous Ubuntu version without any issues. Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 The "Affects" package may not be accurate as I don't know what the cause application is for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1760308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
