unity-2d-launcher crashed with SIGSEGV in exit()

[Mauricio Pretto]

.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-launcher 4.12.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CheckboxSubmission: 8bcf25883b2f450a0298239f3e03ceaa
CheckboxSystem: c69722ecac764861be52925fa50b4dcc
Date: Fri Sep 30 15:31:17 2011
ExecutablePath: /usr/bin/unity-2d-launcher
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110919)
ProcCmdline: unity-2d-launcher
SegvAnalysis:
 Segfault happened at: 0x7fca93fe77d3: mov (%rdx),%rcx
 PC (0x7fca93fe77d3) ok
 source "(%rdx)" (0x2311b200) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 exit () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: unity-2d-launcher crashed with SIGSEGV in exit()
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (3 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1671): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:1671): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (gwibber-service:1922): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

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