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

[Sunil Rana]

I saw two icons for ubuntu one in dash and I licked on the first one and I got this error. I also noticed that there are now two icons for the same in system settings also which was not the case when I had checked just after installing ubuntu. I guess it happens after update or so. thanks

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-places 4.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Sep 25 03:28:52 2011
ExecutablePath: /usr/bin/unity-2d-places
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110922)
ProcCmdline: /usr/bin/unity-2d-places
SegvAnalysis:
 Segfault happened at: 0x2e16b2: movl $0x0,0xc(%eax)
 PC (0x002e16b2) ok
 source "$0x0" ok
 destination "0xc(%eax)" (0x0000020c) 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 admin cdrom dialout lpadmin plugdev sambashare vboxsf

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu 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.