unity-applications-daemon crashed with SIGSEGV in dee_model_remove()

[Eddie Colon]

All I did was download a program called LibreCAD from the software center. When I used dash , to open this program for the first time, the unity launcher crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-applications 5.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 5 19:36:23 2012
ExecutablePath: /usr/lib/unity-lens-applications/unity-applications-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
ProcCmdline: /usr/lib/unity-lens-applications/unity-applications-daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x9a6978: mov (%edi,%esi,4),%eax
 PC (0x009a6978) ok
 source "(%edi,%esi,4)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-lens-applications
StacktraceTop:
 ?? () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libdee-1.0.so.4
 dee_model_remove () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libdee-1.0.so.4
 dee_model_remove () from /usr/lib/libdee-1.0.so.4
Title: unity-applications-daemon crashed with SIGSEGV in dee_model_remove()
UpgradeStatus: Upgraded to precise on 2012-02-05 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Phil. V (philip.v)]

Thanks for your bug report. This still has the coredump attached, which can contain sensitive information, so I'm going to mark this as private until the retracer does its work and removes the attachment.

[Apport retracing service (apport)]

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