unity-2d-launcher crashed with SIGSEGV in QScriptDeclarativeClass::pushCleanContext()

[sam tygier]

Binary package hint: unity-2d

in livecd in testdrive/kvm-qemu shortly after boot

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-launcher 3.8.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
Uname: Linux 3.0-1-generic x86_64
Architecture: amd64
Date: Tue Jun 21 22:36:06 2011
ExecutablePath: /usr/bin/unity-2d-launcher
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110621)
ProcCmdline: unity-2d-launcher
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /usr/lib/libQtScript.so.4
 QScriptDeclarativeClass::pushCleanContext(QScriptEngine*) () from /usr/lib/libQtScript.so.4
 ?? () from /usr/lib/libQtDeclarative.so.4
 ?? () from /usr/lib/libQtDeclarative.so.4
 ?? () from /usr/lib/libQtDeclarative.so.4
Title: unity-2d-launcher crashed with SIGSEGV in QScriptDeclarativeClass::pushCleanContext()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 globalExec (this=0xabf430, exec=0xab1908, _thisObject=<value optimized out>, args=..., callee=0x0, calledAsConstructor=<value optimized out>, clearScopeChain=true) at api/qscriptengine_p.h:885
 QScriptEnginePrivate::pushContext (this=0xabf430, exec=0xab1908, _thisObject=<value optimized out>, args=..., callee=0x0, calledAsConstructor=<value optimized out>, clearScopeChain=true) at api/qscriptengine.cpp:2765
 QScriptDeclarativeClass::pushCleanContext (engine=0xac81e0) at bridge/qscriptdeclarativeclass.cpp:410
 QDeclarativeExpressionPrivate::scriptValue (this=0xe7ca30, secondaryScope=0x0, isUndefined=0x0) at qml/qdeclarativeexpression.cpp:597
 QDeclarativeExpressionPrivate::value (this=0xe7ca30, secondaryScope=0x0, isUndefined=0x0) at qml/qdeclarativeexpression.cpp:628

[Alberto Mardegan (mardy)]

Thank you for reporting this bug.

Since there haven't been any more reports of this crash since a few months, we'll hopefully consider it to be no longer reproducible in the latest version.