ibus-daemon crashed with SIGABRT in g_assertion_message()

Bug #1048161 reported by dino99
400
This bug affects 65 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Expired
High
Unassigned
ibus (Ubuntu)
Invalid
High
Unassigned
Trusty
Expired
Undecided
Unassigned
Utopic
Expired
Undecided
Unassigned
Vivid
Expired
Undecided
Unassigned

Bug Description

i was logged on quantal i386 as gnome-classic, and that crash have happened after i clicked on x to close midori-gtk3

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: ibus 1.4.1-7ubuntu1
Uname: Linux 3.6.0-030600rc5-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Sun Sep 9 10:45:43 2012
ExecutablePath: /usr/bin/ibus-daemon
ProcCmdline: /usr/bin/ibus-daemon --xim
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 admin avahi-autoipd cdrom couchdb dialout dip disk fax fuse haldaemon lpadmin netdev plugdev polkituser proxy root rtkit sambashare ssh tape tty users video whoopsie www-data

Revision history for this message
dino99 (9d9) wrote :
visibility: private → public
description: updated
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 : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ibus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ibus (Ubuntu):
status: New → Confirmed
Revision history for this message
Baokai Lei (leibaokai) wrote :

ibus just crashed on me with the same obscure message:
"SIGABRT in g_assertion_message()"

I'm using Quantal x64 with latest updates and Kde 4.9.2.

On closing Aegisub, ibus suddenly crashed - seemed pretty random.
Didn't have this happening before.

Just looked it up in Synaptic, and ibus version is the same: 1.4.1-7ubuntu1

Revision history for this message
dino99 (9d9) wrote :

On QQ i386 & gnome-classic that issue has not be met since a while, seems to be fixed now.

Revision history for this message
Baokai Lei (leibaokai) wrote :

The bug can't be fixed, as it's still the very same version of ibus.
Seem it appears only on rare conditions when closing an application.

tags: added: running-unity
Revision history for this message
Baokai Lei (leibaokai) wrote :

I'm running Kde, not Unity (nor any other Gnome stuff), but ibus still crashed, so I doubt it's in any way related to Unity.

Revision history for this message
Ma Hsiao-chun (mahsiaochun) wrote :

Anyone willing to try IBus 1.4.2?
It contains several bug fixings from the upstream.
https://github.com/ibus/ibus/commits/1.4.y

tags: added: trusty
Changed in ibus (Ubuntu):
assignee: nobody → Aron Xu (happyaron)
importance: Medium → High
Revision history for this message
Sebastien Bacher (seb128) wrote :

That's still an issue in trusty, Aron, could you look at it?

tags: added: utopic
tags: added: bugpattern-needed
tags: added: vivid
dino99 (9d9)
tags: removed: quantal
Revision history for this message
Will Cooke (willcooke) wrote :

Aron, please take a look at this.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Can be a duplicated of bug #1380982.

Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Please:
  1. Test if <https://github.com/ibus/ibus/commits/1.4.y> doesn't have this bug.
  2. If it has it, report to <https://code.google.com/p/ibus/issues/list>. Then paste the new report URL here.
  3. After testing the above, set this bug status back to "confirmed".

Thank you.

Changed in ibus (Ubuntu):
status: Confirmed → Incomplete
Changed in hundredpapercuts:
status: Confirmed → Incomplete
no longer affects: ibus
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ibus (Ubuntu Trusty):
status: New → Confirmed
Changed in ibus (Ubuntu Utopic):
status: New → Confirmed
Changed in ibus (Ubuntu Vivid):
status: New → Confirmed
dino99 (9d9)
Changed in ibus (Ubuntu Trusty):
status: Confirmed → Incomplete
Changed in ibus (Ubuntu Utopic):
status: Confirmed → Incomplete
Changed in ibus (Ubuntu Vivid):
status: Confirmed → Incomplete
Revision history for this message
Daniel Holbach (dholbach) wrote :

dino: why exactly did you change the status to incomplete?

Changed in ibus (Ubuntu Vivid):
status: Incomplete → Confirmed
Changed in ibus (Ubuntu Utopic):
status: Incomplete → Confirmed
Changed in ibus (Ubuntu Trusty):
status: Incomplete → Confirmed
Changed in ibus (Ubuntu):
status: Incomplete → Confirmed
Changed in hundredpapercuts:
status: Incomplete → Confirmed
Revision history for this message
dino99 (9d9) wrote :

hello Daniel,

as per #9 & #16 above i have done it. note that such 'sigabrt' is mostly related to the compile process and libs have been highly improved and tested to get better quality both with ubuntu & debian since a while.
 So if users avoid some unstable dependencies coming from the bleeding edge, and/or have their settings borked due to using such packages, that error now have gone.
Reopening such report does not help i think.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Ok, sorry, I must have missed that part. Can somebody maybe put together an updated package for the releases above so it can be tested more easily?

Changed in ibus (Ubuntu):
status: Confirmed → Incomplete
Changed in ibus (Ubuntu Trusty):
status: Confirmed → Incomplete
Changed in ibus (Ubuntu Utopic):
status: Confirmed → Incomplete
Changed in ibus (Ubuntu Vivid):
status: Confirmed → Incomplete
dino99 (9d9)
description: updated
Changed in hundredpapercuts:
status: Confirmed → Incomplete
Revision history for this message
Aron Xu (happyaron) wrote :

Just a note, I can never reproduce this bug reliably even tried on several releases of Ubuntu, and I have to admit that the problem exist because it does appear "sometimes".

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ibus (Ubuntu Utopic) because there has been no activity for 60 days.]

Changed in ibus (Ubuntu Utopic):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for One Hundred Papercuts because there has been no activity for 60 days.]

Changed in hundredpapercuts:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ibus (Ubuntu Trusty) because there has been no activity for 60 days.]

Changed in ibus (Ubuntu Trusty):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ibus (Ubuntu Vivid) because there has been no activity for 60 days.]

Changed in ibus (Ubuntu Vivid):
status: Incomplete → Expired
dino99 (9d9)
Changed in ibus (Ubuntu):
status: Incomplete → Invalid
assignee: Aron Xu (happyaron) → nobody
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.