Dear Maintainer,
* What led up to the situation?
I installed ibus-libpinyin to enable pinyin input.
* What exactly did you do (or not do) that was effective (or
ineffective)?
1. Restart GNOME session and computer
2. Fiddle with settings through ibus-setup
3. Installed ibus-gtk, ibus-gtk3
* What was the outcome of this action?
The ibus candidate window still appears at the bottom instead of near the input
field itself.
* What outcome did you expect instead?
Candidate window appearing just slightly below input field like in this picture
(https://user-
images.githubusercontent.com/105929/37892260-355078e8-3112-11e8-809d-48bad7c3a395.png).
I found two askubuntu posts detailing the same thing with no working solutions.
https://askubuntu.com/questions/549900/ibs-chinese-pinyin-input-candidates-
appear-at-bottom-of-screen
https://askubuntu.com/questions/725239/the-ibus-candidate-window-appears-at-
the-bottom-of-wps-office
I couldn't reproduce it in GNOME session w/ ibus 1.5.19-4+b1 and ibus-libpinyin.
I can reproduce this in a Cinammon and i3 desktops, but it's true that somehow GNOME is not affected by this problem.
Hi, As I see ... it looks like this is im-config bug. ^^^^^^^^^^^^^^^^^^^^^^ This is not expected. ibus should have been here if you want to use it via X. (Wayland is another story) Maybe this comes from your old setting. New systemd based Gnome/wayland except for Gnome/ibus/Wayland and Gnome/uim/Wayland have issue to initialize input method. Gnome start up code sets this independent of im-config. This is what I use and GTK_IM_MODULE is unset here. Uim under Gnome/wayland has special start up code via desktop file in im-config which takes care. KDE and non-Gnome GTK desktops ... They are still in the same old X system. They should work fine. Please configure your im-config setting to use ibus again. You may have done so before installing needed GTK3 library.
Yeah, so I can confirm this still occurs even if I'm using straight out ibus here. This was just a test I did to figure out another bug (solved through .Xmodmap removal). I can still reproduce with this environment: $ env | grep -e XMOD -e IM_ GTK_IM_MODULE=ibus QT4_IM_MODULE=ibus XMODIFIERS=@im=ibus CLUTTER_IM_MODULE=ibus QT_IM_MODULE=ibus I ran im-config and it created the following .xinputrc: $ cat .xinputrc # im-config(8) generated on Wed, 16 Oct 2019 16:49:29 -0400 run_im ibus # im-config signature: 6a80770f907c57e20cf92edb0751da12 - I don't actually know what's setting those IM_MODULE variables above. I don't have anything in my $HOME that sets those variables directly. Yeah, that's what I figured as well. But I should mention that the widget is different in GNOME vs (say) Emacs or rxvt. In GNOME it matches the default GNOME theme (grey/black/blue and rounded corners) while in my regular desktop, it's this white/gray thing. It doesn't seem like the same widget at all. I'm not sure I understand what you mean here, but I can confirm I reconfigured im-config and the problem still occurs. I'd be happy to provide more information, screenshots or tests as needed. I have a test user with a blank home which is especially useful to test with, and I can run tests in a virtual machine as well if that's useful. A.
I still can't reproduce it in Cinamon desktop in a new account with the same im-config settings. Something should be different in the reproducing desktop.