ibus-ui-gtk3 crashed with SIGABRT

Bug #1235567 reported by Ferenc J. Stefan
284
This bug affects 54 people
Affects Status Importance Assigned to Milestone
ibus
Unknown
Unknown
ibus (Ubuntu)
Fix Released
High
Aron Xu

Bug Description

Restarted system after installing updates was greeting me with that message

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: ibus 1.5.3-6ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sat Oct 5 08:17:10 2013
Disassembly: => 0x7f62f38f4f77: Cannot access memory at address 0x7f62f38f4f77
ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
InstallationDate: Installed on 2013-06-12 (114 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: ibus-ui-gtk3 crashed with SIGABRT
UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Ferenc J. Stefan (vagabond) wrote :
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
tags: added: apport-failed-retrace
tags: removed: need-amd64-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
Aron Xu (happyaron)
information type: Private → Public
Changed in ibus (Ubuntu):
importance: Undecided → High
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This bug needs to:

1. Be notified to http://code.google.com/p/ibus/issues/list.
2. The notification link to be pasted into the "ibus" project in this report.

Once this has been done, this bug will be ready to be worked on by a developer.

tags: added: trusty
Revision history for this message
Laura Czajkowski (czajkowski) wrote :

This is currently appearing on start up on latest utopic after running updates.

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

@ Laura Czajkowski:

If in the future you see that a bug is affecting a particular release, you only have to add its name to the tag list.

Thank you :-)

tags: added: utopic
Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

adding upstream bugreport

Changed in ibus:
importance: Undecided → Unknown
status: New → Unknown
Changed in ibus (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

seems fixed after installing ibus-dbg along with the utopic updates accumulated for a week or so installed just now at 09:40 GMT on the 20th october. Unsure whether it was the ibus-dbg and it's dependencies or the latest utopic updates that fixed things.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Hey Aron, could you look at that?

Changed in ibus (Ubuntu):
assignee: nobody → Aron Xu (happyaron)
Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

ok, I spoke too soon about it being fixed. The problem is back again. I've created a fully-symbolised backtrace using apport. Find it attached.

Revision history for this message
Vince (vincent-vanackere) wrote :

From upstream bug :
"It seems you have a bug from the previous internal patch.
Please run 'ibus reset-config' and 'ibus restart' command."

At least it looks like this fixed the bug for me.

(also this may be fixed upstream, see https://github.com/ibus/ibus/commit/bb818e438599f080a0cffb0b7573d9a646cf3b1a)

Revision history for this message
John Manning (fandjmanning) wrote : RE: [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT

Hi

Thanks for the update, however I'm not sure how to read these reports. It appears from the details below that I'm running Ubunutu 13.10, when I'm actually running 14.10 (are the details below related to the original fault found?)

Anyway I think I've cure the problem by going back a version with my kernel. Now on 3.16. No problems so far.

I was getting a couple of other spurious messages on boot, prior to the desktop appearing, and they have gone as well. They were related to USB something not found or busy.

Regards
John M

> Date: Fri, 2 Jan 2015 05:11:11 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT
>
> >From upstream bug :
> "It seems you have a bug from the previous internal patch.
> Please run 'ibus reset-config' and 'ibus restart' command."
>
> At least it looks like this fixed the bug for me.
>
> (also this may be fixed upstream, see
> https://github.com/ibus/ibus/commit/bb818e438599f080a0cffb0b7573d9a646cf3b1a)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1235567
>
> Title:
> ibus-ui-gtk3 crashed with SIGABRT
>
> Status in IBus:
> Unknown
> Status in ibus package in Ubuntu:
> Triaged
>
> Bug description:
> Restarted system after installing updates was greeting me with that
> message
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.10
> Package: ibus 1.5.3-6ubuntu2
> ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
> Uname: Linux 3.11.0-11-generic x86_64
> ApportVersion: 2.12.5-0ubuntu1
> Architecture: amd64
> Date: Sat Oct 5 08:17:10 2013
> Disassembly: => 0x7f62f38f4f77: Cannot access memory at address 0x7f62f38f4f77
> ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
> InstallationDate: Installed on 2013-06-12 (114 days ago)
> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MarkForUpload: True
> ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> Signal: 6
> SourcePackage: ibus
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: ibus-ui-gtk3 crashed with SIGABRT
> UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ibus/+bug/1235567/+subscriptions

Revision history for this message
Aron Xu (happyaron) wrote :

Should be fixed in 1.5.10 in wily.

Changed in ibus (Ubuntu):
status: Triaged → Fix Released
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.