Ubuntu
ibus package

ibus-daemon crashed with SIGABRT in g_assertion_message()

Bug #1427730 reported by Eustachy Motyka on 2015-03-03

This bug report is a duplicate of: Bug #1048161: ibus-daemon crashed with SIGABRT in g_assertion_message(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ibus (Ubuntu)	New	Undecided	Unassigned

Bug Description

random error

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: ibus 1.5.9-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic i686
ApportVersion: 2.16.2-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Mar 3 16:20:20 2015
ExecutablePath: /usr/bin/ibus-daemon
InstallationDate: Installed on 2014-12-10 (83 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141209)
ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
ProcEnviron:
LANGUAGE=pl_PL
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=pl_PL.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
?? ()
?? ()
?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom debian-tor dip disk libvirtd lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Eustachy Motyka (eusmotyka) wrote on 2015-03-03:

Dependencies.txt Edit (9.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-03: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1048161, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.