ibus-daemon crashed with SIGABRT in g_assertion_message()

Bug #1252666 reported by KroArtem
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Unfortunately, no valuable information. I was starting VCMI when saw this crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: ibus 1.5.3-6ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Nov 19 13:12:54 2013
ExecutablePath: /usr/bin/ibus-daemon
InstallationDate: Installed on 2012-08-08 (467 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
MarkForUpload: True
ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 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-daemon crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to saucy on 2013-10-20 (29 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

Revision history for this message
KroArtem (kroartem) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ibus (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.