ibus-daemon crashed with SIGSEGV

[tctwyan]

1) Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

2) ibus:
  已安裝：1.5.3-6ubuntu2
  候選： 1.5.3-6ubuntu2
  版本列表：
 *** 1.5.3-6ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
        100 /var/lib/dpkg/status
The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: ibus 1.5.3-6ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
Date: Tue Sep 17 00:27:40 2013
ExecutablePath: /usr/bin/ibus-daemon
ExecutableTimestamp: 1378932553
InstallationDate: Installed on 2013-06-25 (84 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/bin/ibus-daemon --replace --xim --panel disable
ProcCwd: /home/aaron
SegvAnalysis:
 Segfault happened at: 0x80504ef: cmp %eax,(%edx)
 PC (0x080504ef) ok
 source "%eax" ok
 destination "(%edx)" (0xaaaaaaaa) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: ibus
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: ibus-daemon crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-09-11 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 bus_dbus_impl_dispatch_message_by_rule (dbus=dbus@entry=0x950e848, message=message@entry=0x95448c0, skip_connection=skip_connection@entry=0xb6503238) at dbusimpl.c:1901
 bus_dbus_impl_connection_filter_cb (dbus_connection=0x9543000, message=0x95448c0, incoming=0, user_data=0x950e848) at dbusimpl.c:1578
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.