Ubuntu
gnome-shell package

gnome-shell crashed with SIGABRT in g_assertion_message()

Bug #1424199 reported by PTra
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
GNOME Shell
Fix Released
Critical
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Shell crash after exiting a WINE application (Battlefield 1942, running Wine 1.7.37)

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-shell 3.14.3-0ubuntu2
Uname: Linux 3.19.0-031900-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Feb 21 16:08:24 2015
DisplayManager: gdm
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2015-02-09 (11 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150209)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 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
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
PTra (ptram1) wrote :
information type: Private → Public
information type: Public → Public Security
information type: Public Security → Private Security
information type: Private Security → Public
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 gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Bug Watch Updater (bug-watch-updater)
Changed in gnome-shell:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
dino99 (9d9)
tags: added: wily
Revision history for this message
dino99 (9d9) wrote :

This is also met with Wily i386 and a gnome-shell session. Usually it happen when using synaptic to apply upgrade: it comes when the upgrade is done, and so click on the 'applied change' dialogbox button.
That case does not occur everytime but says half time: i cant get more precise testcase, the applied upgrade change is fully done before closing the dialogbox.

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

An other crash that have happened with:
- wily i386
- gnome-shell session running synaptic & midori browser on workspace 1
- switch to workspace 2 and click on the Files (nautilus) icon : got the crash, gnome-shell session closed, and back to login

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

Feedback:

from tweak-tool > Appearance > icons

switching the selected theme mostly always push a crash

Looks like these endless crashes are due to some faulty theme/icon

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

An other crash case:

with Wily, some upgraded packages does not end with a crash. But each time a package upgrade is calling libc6-bin (lastest called process seen inside the install dialog box from synaptic) i'm getting a freeze for a few seconds then crash with the same reported here.
Glancing at libc6-bin inside the archive, that package does not exist anymore but Precise (but still exist in Debian Sid archive)
So that could be some script(s) calling it but not finding it indeed.

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

Crashes have stopped now on Wily; it was probably due to the gcc5 & libstdc++6 transition, which is now quite done.

tags: removed: wily
Bug Watch Updater (bug-watch-updater)
Changed in gnome-shell:
status: Confirmed → Fix Released
Apport retracing service (apport)
tags: added: wily
dino99 (9d9)
Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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