gnome-shell crashed with SIGABRT in g_assertion_message()

[Martin Schaaf]

Crashed on closing scorche3d.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-shell 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun Dec 11 23:26:52 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7fce5f623540 "gjs_object_instance_constructor", message=0x35b0320 "assertion failed: (unthreadsafe_template_for_constructor.info == NULL || strcmp(g_base_info_get_name( (GIBaseInfo*) priv->info), g_base_info_get_name( (GIBaseInfo*) unthreadsafe_template_for_construct"...) at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x0, file=0x7fce5f622e1e "gi/object.c", line=671, func=0x7fce5f623540 "gjs_object_instance_constructor", expr=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1436
 gjs_object_instance_constructor (context=0x2d60b70, argc=0, vp=0x7fce4c9591d8) at gi/object.c:668
 CallJSNative (vp=<optimized out>, argc=<optimized out>, native=<optimized out>, cx=0x2d60b70) at jscntxtinlines.h:701
 CallJSNativeConstructor (vp=<optimized out>, argc=<optimized out>, native=<optimized out>, cx=0x2d60b70) at jscntxtinlines.h:720
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (89 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #867645, 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.