Hi, I was working on something that has nothing to do with Gnome-shell when it crashes.
This bug https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/850365 seems very similar, but as it is expired, I’m filling another bug report. Remove it if it’s not useful.
I’m restarting and I’ll check if it re-launchs well.
Martin.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-shell 3.2.2.1-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CheckboxSubmission: 01a18e0a74cbde3d34a62f62830ed079
CheckboxSystem: f134069bba098730d27f59b402920826
CrashCounter: 1
Date: Fri Feb 10 12:15:38 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
Segfault happened at: 0x7f8951167003: mov 0x50(%rdi),%rbp
PC (0x7f8951167003) ok
source "0x50(%rdi)" (0x00000050) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.5
?? () from /usr/lib/gnome-shell/libgnome-shell.so
?? () from /usr/lib/gnome-shell/libgnome-shell.so
g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #850365, 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.