gnome-shell crashed with SIGSEGV in g_main_context_dispatch()

Bug #959524 reported by Şahin Alp Taşkaya
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

It might be a duplicate, I am not sure.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.3.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: eaa7960ea592567b714ca16e1e8e0382
CheckboxSystem: da9af3b901b5569a389df6337f3d812f
CrashCounter: 1
Date: Mon Mar 19 19:14:26 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7ff5598831bb: mov 0x20(%rdi),%r12
 PC (0x7ff5598831bb) ok
 source "0x20(%rdi)" (0x0002daf8) 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-11 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Şahin Alp Taşkaya (sahin) 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.