gnome-shell crashed with SIGSEGV in g_slice_alloc()

Bug #840715 reported by Doug McMahon
556
This bug affects 128 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
High
Unassigned

Bug Description

Get this on beta 1 updated about 30 % of the time on fresh logins to GS

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-shell 3.1.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Sep 3 21:09:27 2011
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110831)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3aaf1d <g_slice_alloc+269>: mov (%edi),%edx
 PC (0x003aaf1d) ok
 source "(%edi)" (0x00000005) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libclutter-glx-1.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Doug McMahon (mc3man) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x8e64780) at /build/buildd/glib2.0-2.29.18/./glib/gslice.c:492
 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.29.18/./glib/gslice.c:795
 g_slice_alloc (mem_size=20) at /build/buildd/glib2.0-2.29.18/./glib/gslice.c:833
 g_slice_alloc0 (mem_size=20) at /build/buildd/glib2.0-2.29.18/./glib/gslice.c:854
 g_signal_emit_valist (instance=0x96f8460, signal_id=174, detail=0, var_args=0xbfa38a4c "\364\017\220") at /build/buildd/glib2.0-2.29.18/./gobject/gsignal.c:2967

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-i386-retrace
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Doug McMahon (mc3man)
visibility: private → public
Revision history for this message
David Kiliani (mail-davidkiliani) wrote :

I get this bug on amd64 with an intel GPU, so it is probably not related to architecture or graphics driver.

Revision history for this message
Jeroen Keiren (jkeiren) wrote :

I can confirm this bug on AMD64 with an ATI GPU (running fglrx drivers).

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please verify whether this bug still exists with the latest stable release: gnome-shell 3.2.1 in Ubuntu 11.10.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Doug McMahon (mc3man) wrote :

No longer is an issue here, will mark invalid

Changed in gnome-shell (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
keith burnett (ping-keith-gmail) wrote :

Appaport popped up when Gnome Shell crashed on me just now in 12.04 testing, updated to today's date.

Steps to reproduce: Running fglrx driver installed by jockey on a quad core xeon with VTX Radeon HD5450 graphics card. Load Firefox and scroll pages vigourously.

What I see: Screen freezes, then, after some seconds, alert reports that Gnome Shell crashed, top bar disappears and then reappears, appaport loads with a dump.

Revision history for this message
Andreas (andreas-g201) wrote :

Affects me with Ubuntu 12.04 daily and Virtualbox guest additions 4.1.8

Revision history for this message
Johannes Drummer (johannesdrummer) wrote :

Affects me with Ubuntu 12.04 amd64, radeon hd 6850M fglrx, display is attached via hdmi

Azyl (dj-azyl)
Changed in gnome-shell (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Azyl (dj-azyl) wrote :

I started receiving this errors only after installing the latest driver from amd,
The performance of the driver is ok, no more corruptions or glitches on gnome and i can enjoy my video card.

I am running ubuntu 12.04 radeon hd 4330 on Dell inspiron 1545 and i am running gnome shell 3.2.2.1 so i don't think the bug is invalid.

The bug is the one described by keith burnett.

Thanks and please let me know if there is anymore info that i can possibly provide to help.

Revision history for this message
Juha Siltala (topyli) wrote :

Happened to me on an old MacBook.

Revision history for this message
Samuel Dorsaz (akira86) wrote :

And too on a MacBookPro with ubuntu 12.04 - 32bits

Géza Búza (medve)
tags: added: precise
Revision history for this message
MedO (smaxein) wrote :

Happened just now on a freshly upgraded Precise, EeePC 901 (32 bit, Intel graphics), gnome-shell 3.2.2.1-0ubuntu1.

Revision history for this message
Christian B (masterblah777-d) wrote :

This affects me as well, but on gnome-shell version 3.3.9 in Precise.

Jeremy Bícha (jbicha)
Changed in gnome-shell (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Nikolaus Filus (nfilus) wrote :

I am also affected on precise beta1. Similar bug reports are bug #949899 and bug #945349

Revision history for this message
tifoefs (tifoefs) wrote :

Running ubuntu 12.04 with Ati Radeon video card.

Revision history for this message
Martin-Éric Racine (q-funk) wrote :

Has been happening a lot since Precise beta-1.

It mostly seems to happen whenever a package that installed glib or dconf settings gets upgraded. Presumably, something in GNOME tries to run a massive update of gsettings via dpkg triggers at the end of the APT run and it crashes the currently running gnome-shell.

Changed in gnome-shell (Ubuntu):
importance: Medium → High
Revision history for this message
GonzO (gonzo) wrote :

Happening to me on Gnome-Shell 3.4.

Revision history for this message
Ray Perigo (immerohnegott) wrote :

Just happened on 3.4/Precise beta 2 while running a dist-upgrade in a terminal. Shell froze, but the audio from an .avi in Totem continued (video was at the correct point when system resumed function).

Revision history for this message
v.miheer (v-miheer) wrote :

I am trying to use Alt+Ctrl+T to open terminal.
It is defined in shortcuts.
I changed it to Ctrl+T and pressed it.
It opened new tab in running firefox instance.
And shell became irresponsible for couple of seconds.

Revision history for this message
dmiranda (dmiranda) wrote :

Just happened on 3.4/Precise beta 2 while running a dist-upgrade in a terminal

dino99 (9d9)
tags: removed: oneiric
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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