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

Bug #902528 reported by Thomas A. Liggett
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
New
Undecided
Unassigned

Bug Description

12.04 daily build 12/9/11
Opening home folder
places crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-places 4.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CasperVersion: 1.293
Date: Sat Dec 10 13:38:03 2011
ExecutablePath: /usr/bin/unity-2d-places
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111209.1)
ProcCmdline: /usr/bin/unity-2d-places
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x5e8892: movl $0x0,0xc(%eax)
 PC (0x005e8892) ok
 source "$0x0" ok
 destination "0xc(%eax)" (0x00000084) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QMetaObject::activate(QObject*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
Title: unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Thomas A. Liggett (tomcjeagle-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.