unity-2d-launcher crashed with SIGSEGV in QScriptValue::engine()

Bug #801161 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d
Confirmed
Critical
Unassigned
unity-2d (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

On an Oneiric i386 20110623 daily-live system with unity-2d/unity-2d-launcher 3.8.8-0ubuntu1, I clicked the home button (above the launcher, at the upper-left corner of the screen), searched for "gnome-terminal" (without the quotes), and clicked on the Terminal in the search results, to run it. The Terminal opened, then its icon disappeared momentarily from the launcher, then the launcher disappeared and reappeared (with the icon for the running Terminal correctly displayed) and I was informed that unity-2d-launcher crashed with SIGSEGV in QScriptValue::engine().

In case it's relevant, when this occurred I was also experiencing what appears to be bug 797676, as well as the additional problems detailed in https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/797676/comments/3.

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 i686
Architecture: i386
Date: Thu Jun 23 11:09:13 2011
ExecutablePath: /usr/bin/unity-2d-launcher
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110623)
ProcCmdline: unity-2d-launcher
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x138ebd4 <_ZNK12QScriptValue6engineEv+4>: mov (%eax),%eax
 PC (0x0138ebd4) ok
 source "(%eax)" (0x2404c704) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QScriptValue::engine() const () from /usr/lib/libQtScript.so.4
 ?? () from /usr/lib/libQtDeclarative.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 QScriptValue::engine()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 data (this=0x2404c704) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:140
 qGetPtrHelper<QExplicitlySharedDataPointer<QScriptValuePrivate> > (this=0x2404c704) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2340
 d_func (this=0x2404c704) at api/qscriptvalue.h:211
 QScriptValue::engine (this=0x2404c704) at api/qscriptvalue.cpp:1819
 QDeclarativeObjectScriptClass::newQObject (this=0x8a8b518, object=0x8e667b0, type=136) at qml/qdeclarativeobjectscriptclass.cpp:122

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-2d (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in unity-2d (Ubuntu):
importance: Medium → Critical
Changed in unity-2d:
importance: Undecided → Critical
Changed in unity-2d (Ubuntu):
status: New → Confirmed
Changed in unity-2d:
status: New → Confirmed
milestone: none → 4.4
Changed in unity-2d:
milestone: 4.4 → 4.6
Changed in unity-2d:
milestone: 4.6 → 4.8
Changed in unity-2d:
milestone: 4.8 → 4.10
Changed in unity-2d:
milestone: 4.10 → none
Revision history for this message
Florian Boucault (fboucault) wrote :

Latest occurence of the crash was with unity-2d-launcher 4.8.0-0ubuntu1 on the 2011-09-18.

Revision history for this message
Florian Boucault (fboucault) wrote :

Previous comment was based on bug #853313

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.