Ubuntu
ibus package

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

Bug #1431479 reported by PEDRON Alexandre on 2015-03-12

This bug report is a duplicate of: Bug #1380982: ibus-ui-gtk3 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

Happened right after booting

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
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Thu Mar 12 18:25:51 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
InstallationDate: Installed on 2014-06-01 (284 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
ProcEnviron:
LANGUAGE=fr_FR
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.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
?? ()
?? ()
?? ()
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

Tags:

Revision history for this message

PEDRON Alexandre (pedron-alexandre) wrote on 2015-03-12:

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

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-12: 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 #1380982, 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.