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

Bug #832221 reported by xe2xpk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
New
Undecided
Unassigned

Bug Description

this happens when trying to open the update-manager

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-places 4.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Tue Aug 23 12:41:43 2011
ExecutablePath: /usr/bin/unity-2d-places
ProcCmdline: unity-2d-places
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8ace8a: movl $0x0,0xc(%eax)
 PC (0x008ace8a) ok
 source "$0x0" ok
 destination "0xc(%eax)" (0x0000002c) 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: Upgraded to oneiric on 2011-08-23 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
xe2xpk (skorlowsky) wrote :
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #831663, so it 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. Feel free to continue to report any other bugs you may find.

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.