gnome-shell crashed with SIGSEGV in g_main_context_dispatch()

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

Bug Description

Gnome Shell crashed while doing a dist-upgrade on 12.04 beta. All the settings (i.e. extensions and theme) were reset.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.3.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sat Mar 17 09:20:00 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120209.2)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbb60a0f1bb: mov 0x20(%rdi),%r12
 PC (0x7fbb60a0f1bb) ok
 source "0x20(%rdi)" (0x0001ca63) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () 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/libclutter-1.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2012-03-17 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Antonio Froio (telespalla--bob) 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 this software better. This particular crash has already been reported and is a duplicate of bug #932569, 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
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.