ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

[David Richardson]

on 14.10

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: ibus 1.5.8-2ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Aug 20 09:35:05 2014
ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
InstallationDate: Installed on 2014-05-29 (82 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message (domain=domain@entry=0x41ca51 "_TYPE_CHECK_VALUE_TYPE (value, TYPE_APPLICATION)", file=file@entry=0x41de90 " %s", line=line@entry=2567, func=func@entry=0x41eec0 "\300TA", message=message@entry=0x24e17c0 "assertion failed: (i >= 0 && i < m_engines.length)") at /build/buildd/glib2.0-2.41.2/./glib/gtestutils.c:2291
 g_assertion_message_expr (domain=0x41ca51 "_TYPE_CHECK_VALUE_TYPE (value, TYPE_APPLICATION)", file=0x41de90 " %s", line=2567, func=0x41eec0 "\300TA", expr=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gtestutils.c:2306
 panel_status_icon_popup_menu_cb (button=<optimized out>, activate_time=<optimized out>, status_icon=<optimized out>, self=0x22a2280) at panel.c:4429
 _panel_status_icon_popup_menu_cb_gtk_status_icon_popup_menu (_sender=<optimized out>, button=<optimized out>, activate_time=<optimized out>, self=0x22a2280) at panel.c:517
 ?? ()

[Launchpad Janitor (janitor)]

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