Obsolete
Status Update
No update yet.
Comments
yu...@chromium.org
[Empty comment from Monorail migration]
ma...@chromium.org
[Empty comment from Monorail migration]
pa...@gmail.com
Looks like after the latest update, everything works normally. I am now running mozc version 2.16.2003.102 and it works in Chrome. Thank you very much for looking into this.
ma...@chromium.org
Thanks for the update. Please feel free to file a new bug for any further issues with chrome in future.
pa...@gmail.com
Looks like I celebrated too early. Today I restarted my computer, and booted it back up only to find out that Mozc does not work with Chrome yet again.
I figured out that in order to make Mozc work again with Chrome, is to just simply reinstall it.
However, after a reboot, Mozc ceases to work until I reinstall it again. Really strange. I'm sorry to bother you again.
I figured out that in order to make Mozc work again with Chrome, is to just simply reinstall it.
However, after a reboot, Mozc ceases to work until I reinstall it again. Really strange. I'm sorry to bother you again.
yu...@chromium.org
Is this really specific to ibus-mozc? For example, can you see the same issue with ibus-anthy or ibus-kkc with the same procedure (after setting it as the default IME and reboot your machine)?
ma...@chromium.org
[Empty comment from Monorail migration]
pa...@gmail.com
All right, looks like it's not specific to ibus-mozc. Neither ibus-anthy nor ibus-kkc worked with Chrome after setting as the default IME and rebooting the computer.
yu...@chromium.org
Thank you for the confirmation. Updated the issue summary accordingly.
ra...@chromium.org
[Empty comment from Monorail migration]
pa...@gmail.com
Update:
I was able to work out a way around it.
In my ~/.profile, I changed...
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
ibus-daemon -drx
to...
export GTK_IM_MODULE=xim
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=xim
ibus-daemon -drx
I was able to work out a way around it.
In my ~/.profile, I changed...
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
ibus-daemon -drx
to...
export GTK_IM_MODULE=xim
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=xim
ibus-daemon -drx
sh...@chromium.org
Tried iBus-based Chinese Pinyin IME, it works fine on Chrome 39.0.2171.95 with GTK_IM_MODULE=ibus & QT_IM_MODULE=ibus.
la...@google.com
[Empty comment from Monorail migration]
cj...@cynic.net
I'm seeing this issue on a pair of Ubuntu 18.04 systems: Chrome running locally works fine with GTK_IM_MODULE and QT_IM_MODULE set to "ibus", but when running Chrome on a remote Ubuntu 18.04 system using SSH X11 fowarding, I must set those two variables to "xim". (urxvt runs fine on the remote system with those set to "ibus".)
is...@google.com
This issue was migrated from crbug.com/chromium/437764?no_tracker_redirect=1
[Monorail components added to Component Tags custom field.]
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem:
1. Open up Google Chrome
2. Switch to Mozc (running under IBus)
3. Switch input mode to 'Hiragana'
4. Try to type Japanese
What is the expected behavior?
Text output in Japanese.
What went wrong?
Mozc doesn't work at all with Chrome.
Did this work before? Yes Before a certain Chrome update, although, I cannot precisely tell which one.
Chrome version: 39.0.2171.71 Channel: stable
OS Version: x86_64 Linux 3.17.4-1-ARCH
Flash Version: Shockwave Flash 15.0 r0
Output from 'locale' command. Could be helpful, perhaps.
LANG=en_US.utf8
LC_CTYPE=en_US.utf8
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
IBus version: 1.5.9
Mozc version: 1.15.1917.102