Bug 515350

1. Have you used im-chooser to enable IBus?
2. Can you see ibus blue icon at the systray?
3. When you run im-chooser again, is the check box turned on?

If not for any of the above questions, please attach your .xsession-errors and make sure if $HOME/.xinputrc points to ibus.conf.

1. Yes, I have.
2. The icon is there. I can right-click on it and that brings IBus
   preferences dialog.
3. The "Enable input method feature" checkbox is on.

[zaitcev@niphredil ~]$ ls -ld .xinputrc 
lrwxrwxrwx 1 zaitcev zaitcev 33 2009-07-31 19:55 .xinputrc -> /etc/X11/xinit/xinput.d/ibus.conf
[zaitcev@niphredil ~]$ 

There's nothing interesting in .xsession-errors, but I'll attach it
just in case.

Created attachment 356093 [details]
.xsession-errors

BTW, just in case too:

[zaitcev@niphredil ~]$ ps auxww| grep ibus
zaitcev   5792  0.1  0.1 136864  3148 ?        S    22:05   0:00 /usr/bin/ibus-daemon --xim
zaitcev   5793  0.1  0.1 141432  3472 ?        S    22:05   0:00 /usr/libexec/ibus-gconf
zaitcev   5794  0.7  1.2 295636 24228 ?        S    22:05   0:00 python /usr/share/ibus/ui/gtk/main.py
zaitcev   5796  0.0  0.3 218488  6328 ?        S    22:05   0:00 /usr/libexec/ibus-x11 --kill-daemon
zaitcev   5797  0.6  0.6 208264 11876 ?        S    22:05   0:00 python /usr/share/ibus-anthy/engine/main.py --ibus
zaitcev   5818  0.0  0.0  89068   832 pts/2    S+   22:06   0:00 grep ibus
[zaitcev@niphredil ~]$

Please try below command, and tell us if the ibus can work in gedit. thanks
GTK_IM_MODULE=ibus gedit

Is this related to bug 514720?

The "GTK_IM_MODULE=ibus gedit" has no effect: Ctrl-Space does not work in it.

Regarding bug 514720, I cannot tell for sure, but I know that nothing
segfaults here. My kernel logs all segfaults and I only have one such
(from libvirtd at system boot-up). So there are no crashes in X or GNOME.

Please upload /etc/gtk-2.0/{i386, i686 or x86_64}-redhat-linux-gnu/gtk.immodules.

I see, it's empty:

[zaitcev@niphredil ~]$ ls  -l /etc/gtk*/*/gtk.immodules 
-rw-r--r-- 1 root root 587 2009-08-03 12:50 /etc/gtk-2.0/i386-redhat-linux-gnu/gtk.immodules
-rw-r--r-- 1 root root   0 2009-08-03 12:49 /etc/gtk-2.0/x86_64-redhat-linux-gnu/gtk.immodules
[zaitcev@niphredil ~]$ 

And the i386 one only contains references to SCIM:

[zaitcev@niphredil ~]$ cat /etc/gtk-2.0/i386-redhat-linux-gnu/gtk.immodules
# GTK+ Input Method Modules file
# Automatically generated file, do not edit
# Created by /usr/bin/gtk-query-immodules-2.0-32 from gtk+-2.17.6
#
# ModulesPath = /root/.gtk-2.0/2.10.0/i386-redhat-linux-gnu/immodules:/root/.gtk-2.0/2.10.0/immodules:/root/.gtk-2.0/i386-redhat-linux-gnu/immodules:/root/.gtk-2.0/immodules:/usr/lib/gtk-2.0/2.10.0/i386-redhat-linux-gnu/immodules:/usr/lib/gtk-2.0/2.10.0/immodules:/usr/lib/gtk-2.0/i386-redhat-linux-gnu/immodules:/usr/lib/gtk-2.0/immodules
#
"/usr/lib/gtk-2.0/immodules/im-scim-bridge.so" 
"scim-bridge" "SCIM Bridge Input Method" "" "" "" 

[zaitcev@niphredil ~]$

If I run gtk-query-immodules-2.0-64, it crashes. However, if I run it
piped to terminal, it produes the file gtk.immodules, then crashes.
If I run it with output redirected, it crashes without producing
the output. I speculate that it happens because stdio buffers output
if it's not directed to terminal, and the program crashes before
exit() flushes the output.

Here's what gdb says (all debuginfos installed):

(gdb) where
#0  0x00007ffff2402620 in ?? ()
#1  0x00007ffff3b5cb32 in exit () from /lib64/libc.so.6
#2  0x00007ffff3b44b94 in __libc_start_main () from /lib64/libc.so.6
#3  0x0000000000400fb9 in _start ()
(gdb) quit

*** Bug 515036 has been marked as a duplicate of this bug. ***

I think this bug is in gtk2.

Not a very useful stacktrace, unfortunately. It doesn't segfault here, of course...

I have two systems, gtk-query-immodues-2.0-64 crashes on one (above)
and does not crash on the other. Resulting file on the one that does NOT
crash:

# GTK+ Input Method Modules file
# Automatically generated file, do not edit
# Created by /usr/bin/gtk-query-immodules-2.0-64 from gtk+-2.17.6
#
# ModulesPath = /root/.gtk-2.0/2.10.0/x86_64-redhat-linux-gnu/immodules:/root/.gtk-2.0/2.10.0/immodules:/root/.gtk-2.0/x86_64-redhat-linux-gnu/immodules:/root/.gtk-2.0/immodules:/usr/lib64/gtk-2.0/2.10.0/x86_64-redhat-linux-gnu/immodules:/usr/lib64/gtk-2.0/2.10.0/immodules:/usr/lib64/gtk-2.0/x86_64-redhat-linux-gnu/immodules:/usr/lib64/gtk-2.0/immodules
#
"/usr/lib64/gtk-2.0/2.10.0/immodules/im-ibus.so" 
"ibus" "IBus (Intelligent Input Bus)" "ibus" "" "ja:ko:zh" 

I can only say that
 1. the system does not have SCIM installed
 2. the file is shorter, so maybe the longer one overflows a buffer somewhere

Indeed, if I remove all SCIM packages, gtk-query-immodules-2.0-64 runs
to completion without a crash.

rpm -e scim-bridge-0.4.16-2.fc12.x86_64 scim-tables-russian-0.5.9-2.fc12.x86_64 scim-1.4.9-2.fc12.x86_64 scim-bridge-gtk-0.4.16-2.fc12.i686 scim-libs-1.4.9-2.fc12.i686 scim-libs-1.4.9-2.fc12.x86_64 scim-bridge-gtk-0.4.16-2.fc12.x86_64 scim-gtk-1.4.9-2.fc12.x86_64 scim-qtimm-0.9.4-13.fc12.x86_64 scim-anthy-1.2.7-3.fc12.x86_64 scim-tables-0.5.9-2.fc12.x86_64 scim-lang-japanese-1.4.9-2.fc12.x86_64

This is how gtk.immodules would've looked if not for crash:

# GTK+ Input Method Modules file
# Automatically generated file, do not edit
# Created by gtk-query-immodules-2.0-64 from gtk+-2.17.7
#
# ModulesPath = /root/.gtk-2.0/2.10.0/x86_64-redhat-linux-gnu/immodules:/root/.gtk-2.0/2.10.0/immodules:/root/.gtk-2.0/x86_64-redhat-linux-gnu/immodules:/root/.gtk-2.0/immodules:/usr/lib64/gtk-2.0/2.10.0/x86_64-redhat-linux-gnu/immodules:/usr/lib64/gtk-2.0/2.10.0/immodules:/usr/lib64/gtk-2.0/x86_64-redhat-linux-gnu/immodules:/usr/lib64/gtk-2.0/immodules
#
"/usr/lib64/gtk-2.0/2.10.0/immodules/im-ibus.so" 
"ibus" "IBus (Intelligent Input Bus)" "ibus" "" "ja:ko:zh" 

"/usr/lib64/gtk-2.0/immodules/im-scim-bridge.so" 
"scim-bridge" "SCIM Bridge Input Method" "" "" "" 

"/usr/lib64/gtk-2.0/immodules/im-scim.so" 
"scim" "SCIM Input Method" "scim" "/usr/share/locale" ""

I guess the real cause of this issue is bug 517001.

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