nautilus crash on hitting a key on window

[Halton Huo]

Binary package hint: nautilus

I just upgrade my system from 10.04 to 10.10.

Steps to reproduce:
1) launch nautilus
2) click on the empty place on the nautilus window which means does not select any file/folder.
3) hit a key like 'm'

Excepted result:
  The file/folder start from m

Actual result:
  nautilus core dump

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic i686
Architecture: i386
Date: Wed Aug 25 17:22:15 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nautilus

[Halton Huo (halton-huo)]

The core file is big (~65M). So I'd like to paste the backtrace here.

(gdb) where
#0 0x08132293 in ?? ()
#1 0x008740fc in g_cclosure_marshal_VOID__STRING ()
   from /usr/lib/libgobject-2.0.so.0
#2 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3 0x0087cde5 in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0x0087e45c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#5 0x0087ebc2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#6 0x0025a152 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x0087371c in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#8 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#9 0x0087cde5 in ?? () from /usr/lib/libgobject-2.0.so.0
#10 0x0087e45c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#11 0x0087e745 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#12 0x002c3a07 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x0087371c in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#14 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#15 0x0087cde5 in ?? () from /usr/lib/libgobject-2.0.so.0
#16 0x0087e45c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#17 0x0087ebc2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#18 0x07d4e17b in ?? () from /usr/lib/gtk-2.0/2.10.0/immodules/im-ibus.so
#19 0x0087371c in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#20 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#21 0x0087cde5 in ?? () from /usr/lib/libgobject-2.0.so.0
#22 0x0087e45c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#23 0x0087ebc2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#24 0x03c56a7d in ?? () from /usr/lib/libibus.so.2
#25 0x03c64d74 in ibus_marshal_BOOLEAN__POINTER () from /usr/lib/libibus.so.2
#26 0x00862827 in ?? () from /usr/lib/libgobject-2.0.so.0
#27 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#28 0x0087ca36 in ?? () from /usr/lib/libgobject-2.0.so.0
#29 0x0087e2db in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#30 0x0087ebc2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#31 0x03c4b30d in ibus_proxy_handle_signal () from /usr/lib/libibus.so.2
#32 0x03c4bb34 in ?? () from /usr/lib/libibus.so.2
#33 0x03c64d74 in ibus_marshal_BOOLEAN__POINTER () from /usr/lib/libibus.so.2
#34 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#35 0x0087cde5 in ?? () from /usr/lib/libgobject-2.0.so.0
#36 0x0087e2db in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#37 0x0087ebc2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#38 0x03c49b98 in ?? () from /usr/lib/libibus.so.2
#39 0x03c64d74 in ibus_marshal_BOOLEAN__POINTER () from /usr/lib/libibus.so.2
#40 0x00862827 in ?? () from /usr/lib/libgobject-2.0.so.0
#41 0x008641b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#42 0x0087ca36 in ?? () from /usr/lib/libgobject-2.0.so.0
#43 0x0087e2db in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#44 0x0087ebc2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#45 0x03c481d4 in ?? () from /usr/lib/li...

[Sebastien Bacher (seb128)]

The stacktrace shows that the crash is an ibus one

[Sebastien Bacher (seb128)]

Could you install libglib2.0-dbgsym ibus-gtk-dbgsym libibus2-dbgsym and get a new stacktrace?