gnome-shell crashed with SIGSEGV in g_slice_alloc()

Bug #841480 reported by Gerhard Bogner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

gnome-shell crashed a short while after login (while upgrading packages in synaptic)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-shell 3.1.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 5 04:00:52 2011
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f27cc0b7505 <g_slice_alloc+293>: mov (%rbx),%rdx
 PC (0x7f27cc0b7505) ok
 source "(%rbx)" (0x63206f6964754165) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/gnome-shell/libgnome-shell.so
Title: gnome-shell crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to oneiric on 2011-08-21 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

Revision history for this message
Gerhard Bogner (bogi788) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #840715, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.