unity-2d-places crashed with SIGSEGV in QMetaObject::activate()

Bug #829022 reported by Fabio Marconi
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

Hello
Clicked on the Emacs icon in the dash and apport popup this.
Everythings seems working without problems
Thanks
Fabio

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-places 4.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Thu Aug 18 22:18:06 2011
ExecutablePath: /usr/bin/unity-2d-places
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110816)
ProcCmdline: unity-2d-places
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0ef9bb93a9: movq $0x0,0x18(%rax)
 PC (0x7f0ef9bb93a9) ok
 source "$0x0" ok
 destination "0x18(%rax)" (0x7f0ef9f36c30) in non-writable VMA region: 0x7f0ef9f1b000-0x7f0ef9f3a000 r--p /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4.7.3.dpkg-new
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4.7.3.dpkg-new
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4
Title: unity-2d-places crashed with SIGSEGV in QMetaObject::activate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
description: updated
description: updated
visibility: private → public
Changed in unity-2d:
importance: Undecided → Critical
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 clearValues (this=0x7f0ef9f36c18) at qml/qdeclarativeboundsignal.cpp:243
 QDeclarativeBoundSignal::qt_metacall (this=0x29e5620, c=<optimized out>, id=<optimized out>, a=0x7ffff5f58d10) at qml/qdeclarativeboundsignal.cpp:181
 QMetaObject::activate (sender=0x31df2e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7ffff5f58d10) at kernel/qobject.cpp:3278
 QDeclarativeVMEMetaObject::metaCall (this=0x31df620, c=<optimized out>, _id=32, a=0x7ffff5f58d10) at qml/qdeclarativevmemetaobject.cpp:639
 QDeclarativeVMEMetaObject::metaCall (this=0x2e01d30, c=QMetaObject::InvokeMetaMethod, _id=32, a=0x7ffff5f58d10) at qml/qdeclarativevmemetaobject.cpp:673

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-amd64-retrace
Changed in unity-2d (Ubuntu):
status: New → Confirmed
Changed in unity-2d:
status: New → Confirmed
Changed in unity-2d (Ubuntu):
importance: Medium → Critical
Revision history for this message
Florian Boucault (fboucault) wrote :

ThreadStackTrace.txt is especially interesting because it indicates that the crash occurred while loading an SVG file.

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.