You are not logged in.
Like the title says, iBus language input change does not work after an update.
I haven't changed anything. I am attaching my .bashrc below.
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
ibus-daemon -drx
And my 'Next Input Method' is Control+Return and my language toggle key is Control+Space.
I do get iBus icon popup whenever I press Control+Return, but after this the input language won't change with Control+Space.
And I get this error message when I try to setup my language on ibus-setup.
/usr/share/ibus-hangul/setup/main.py:298: DeprecationWarning: bind_textdomain_codeset() is deprecated gettext.bind_textdomain_codeset(config.gettext_package, "UTF-8")
Does anyone has this problem?
Last edited by redshoe (2019-12-24 22:43:19)
Offline
I experience the same recently.
Seeing /var/log/pacman.log, I found that ibus-hangul was upgraded from 1.5.1-2 to 1.5.2-1.
So tried to roll back to 1.5.1-2 and IME worked fine.
According to https://github.com/libhangul/ibus-hangul/releases , 1.5.2 has a critical problem, which is to blame for the problem we experience. 1.5.3 is already out and then the problem should go away.
Try to downgrade for the time being.
Offline
-
Last edited by dynaxis (2019-12-25 17:18:16)
Offline
I experience the same recently.
Seeing /var/log/pacman.log, I found that ibus-hangul was upgraded from 1.5.1-2 to 1.5.2-1.
So tried to roll back to 1.5.1-2 and IME worked fine.According to https://github.com/libhangul/ibus-hangul/releases , 1.5.2 has a critical problem, which is to blame for the problem we experience. 1.5.3 is already out and then the problem should go away.
Try to downgrade for the time being.
Thank you. Downgrading works. But do you get this weird Korean character mashup in your web browser tab like in the picture below? This happened with the ibus-hangul problem after an update.
This happens on search tab on gtk applications, not in website search tab.
Last edited by redshoe (2019-12-25 19:16:27)
Offline
@redshoe Sorry for the late reply. I've never experienced similar problems (at least yet). BTW, my locale is set to en_US.UTF8 rather than ko_KR.UTF8, which is usual for Koreans.
Offline