Bug 12509 - After upgrade from 3 to 4 chrome browser no longer accepts ibus/xim/other input methods
Summary: After upgrade from 3 to 4 chrome browser no longer accepts ibus/xim/other inp...
Status: RESOLVED DUPLICATE of bug 8731
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-02 05:37 CET by Ethan Merritt
Modified: 2014-02-28 00:40 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ethan Merritt 2014-02-02 05:37:12 CET 
I use ibus + Anthy to toggle between English and Japanese keyboard input.  This has worked reliably for me under Mageia 3 for all applications I have tried. For most applications no special procedure is necessary other than the keyboard hotkey configure in the ibus widget.  The chrome browser has been an exception, in that you must right-click to generate a pull-down menu and then select the new input method from a long list.

After upgrading from Mageia 3 to Mageia 4 the chrome browser no longer offers any input methods in the pull-down menu other than "simple" and "system". The normal hotkey has no effect (but then again it didn't under Mageia 3 either).  I did not upgrade the Chrome browser as part of the Mageia 3->4 upgrade, so this is the identical browser exectable that was working before.

My ~/.i18n file contains
    GTK_IM_MODULE=ibus
    QT_IM_MODULE=ibus
    XMODIFIERS=@im=ibus

I found a similar bug report against recent Ubuntu, but the fix suggested there (change the line in ~/.i18n to GTK_IM_MODULE=xim) had no effect on either of my test machines. 

It is still possible to cut-and-paste CJK input in the chrome browser.  The failure is in the keyboard input method.

The ibus related packages I have installed are
libibus-gir1.0-1.5.4-4.mga4
libusbmuxd2-1.0.8-4.mga4
libuser-0.60-2.mga4
ibus-qt4-1.3.1-10.mga4
libusb-compat0.1_4-0.1.5-2.mga4
libibus1.0_5-1.5.4-4.mga4
ibus-1.5.4-4.mga4
libusb1.0_0-1.0.17-2.mga4
libusb1.0-devel-1.0.17-2.mga4
libuser1-0.60-2.mga4
ibus-mozc-1.11.1522.102-6.mga4
ibus-anthy-1.5.4-1.mga4
ibus-ui-gtk3-1.5.4-4.mga4

I see the identical failure on two machines: i586 running Mageia 4, 
x86_64 running Cauldron.
Ethan Merritt 2014-02-02 05:38:51 CET

CC: (none) => eamerritt

Manuel Hiebel 2014-02-02 18:16:56 CET

CC: (none) => fundawang

Comment 1 Ethan Merritt 2014-02-28 00:40:41 CET 
This is the same as Bug 8731.

Work around is to set environmental variable

export GTK_IM_MODULE_FILE=/etc/gtk-2.0/gtk.immodules.lib64

For me the fix is to add this line to the bash wrapper that comes with the chrome browser:
   /opt/google/chrome/google-chrome

*** This bug has been marked as a duplicate of bug 8731 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.