compiz crashed with SIGSEGV in unity::dash::ResultRendererHorizontalTile::Render()

[Jono Bacon]

This was an automated crash that happened when I clicked on the BFB and the dash displayed but I could not dismiss it.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Sep 9 08:45:37 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x404025f <_ZN5unity4dash28ResultRendererHorizontalTile6RenderERN3nux14GraphicsEngineERNS0_6ResultENS0_14ResultRenderer19ResultRendererStateERNS2_4RectEii+463>: mov 0x8(%eax),%eax
 PC (0x0404025f) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 unity::dash::ResultRendererHorizontalTile::Render(nux::GraphicsEngine&, unity::dash::Result&, unity::dash::ResultRenderer::ResultRendererState, nux::Rect&, int, int) () from /usr/lib/compiz/libunityshell.so
 unity::dash::ResultViewGrid::Draw(nux::GraphicsEngine&, bool) () from /usr/lib/compiz/libunityshell.so
 nux::View::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/libnux-1.0.so.0
 nux::Layout::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/libnux-1.0.so.0
 unity::PlacesGroup::DrawContent(nux::GraphicsEngine&, bool) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in unity::dash::ResultRendererHorizontalTile::Render()
UpgradeStatus: Upgraded to oneiric on 2011-07-13 (57 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #845697, 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.