gnome-shell crashed with SIGABRT in raise()

Bug #846175 reported by Ramiro Queso
390
This bug affects 42 people
Affects Status Importance Assigned to Milestone
folks
Fix Released
Critical
folks (Ubuntu)
Fix Released
High
Unassigned
gnome-shell (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-shell 3.1.90.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 9 22:22:22 2011
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=es_BO:es
 PATH=(custom, no user)
 LANG=es_BO.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 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
 folks_persona_set_individual () from /usr/lib/libfolks.so.25
Title: gnome-shell crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: admin
XsessionErrors:
 (empathy:1790): Gtk-CRITICAL **: gtk_tree_path_compare: assertion `b->depth > 0' failed
 (empathy:1790): Gtk-CRITICAL **: gtk_tree_path_compare: assertion `b->depth > 0' failed

Revision history for this message
Ramiro Queso (rqueso) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f256b0a8270 "folks_persona_set_individual", message=0x2c07db0 "assertion failed: (_tmp6_)") at /build/buildd/glib2.0-2.29.90/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x7f256b0a115e "folks", file=0x7f256b0a7ecc "persona.c", line=777, func=0x7f256b0a8270 "folks_persona_set_individual", expr=<optimized out>) at /build/buildd/glib2.0-2.29.90/./glib/gtestutils.c:1436
 folks_persona_set_individual (self=0x2b49d40, value=0x275fd20) at persona.c:777
 _folks_individual_disconnect_from_persona (replacement_individual=0x275fd20, persona=0x2b49d40, self=0x2bee930) at individual.c:4820
 _folks_individual_set_personas (self=0x2bee930, personas=0x0, replacement_individual=0x275fd20) at individual.c:6183

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
visibility: private → public
tags: added: bugpattern-needed
Revision history for this message
Jigar Shah (jigar-shah1984) wrote :

The occurance is pretty random, but can be usually seen while accessing applications on different workspaces. For example selecting an application in one workspace from another will sometimes cause the screen to freeze and gnome-shell to crash and restart.

Revision history for this message
Joe Barnett (thejoe) wrote :

I've noticed this with considerably less randomness; seems to happen (almost) every time an IM status change occurs through the top-right-user-menu or through the empathy UI

Revision history for this message
Timo Reimerdes (timorei) wrote :

Indeed - I switched to pidgin for testing this, and no more crashes occur.

Revision history for this message
Jigar Shah (jigar-shah1984) wrote : Re: [Bug 846175] Re: gnome-shell crashed with SIGABRT in raise()

It haapens to me whenever I restart the system, or wake up the system
from suspended mode

On Thu 15 Sep 2011 10:51:35 AM CDT, Joe Barnett <email address hidden> wrote:

> I've noticed this with considerably less randomness; seems to happen
> (almost) every time an IM status change occurs through the top-right-
> user-menu or through the empathy UI
>

Changed in folks:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
Joe Barnett (thejoe) wrote :

I've built a local libfolks* with the changes from the linked upstream bug, and haven't seen gnome-shell/empathy crash since.

http://git.gnome.org/browse/folks/commit/?id=1f85f89051e63b05e271b418687c242a83e2f296

and

http://git.gnome.org/browse/folks/commit/?id=406bc1264d3f19c54ea0c929e93814d263a90cc1

(possible that only the first one actually needed)

Changed in folks:
importance: Medium → Unknown
status: Invalid → Unknown
Changed in folks:
importance: Unknown → Critical
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in folks (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

The fix is included in https://launchpad.net/ubuntu/+source/folks/0.6.3-0ubuntu1 ; closing this as fix released, please re open though if you are still seeing the exact same problem, thanks all.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
Changed in folks (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
status: Triaged → Fix Released
Revision history for this message
ekkasit yaemyuan (ekkasitidentity) wrote :

thank

To post a comment you must log in.