compiz crashed with SIGSEGV in nux::GraphicsDisplay::StartDndDrag()

[camillo imbimbo]

fresh install of 12.10. first login. compiz crash while I opened terminal window to update software and clicked dash

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3249-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic i686
ApportVersion: 2.4-0ubuntu8
Architecture: i386
Date: Tue Aug 21 02:53:30 2012
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb4b2f2eb <_ZN3nux15GraphicsDisplay12StartDndDragERKNS0_15_DndSourceFuncsEPv+203>: mov (%eax),%eax
 PC (0xb4b2f2eb) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 nux::GraphicsDisplay::StartDndDrag(nux::GraphicsDisplay::_DndSourceFuncs const&, void*) () from /usr/lib/libnux-graphics-3.0.so.0
 nux::InputArea::StartDragAsSource() () from /usr/lib/libnux-3.0.so.0
 nux::WindowCompositor::MouseEventCycle(nux::Event&) () from /usr/lib/libnux-3.0.so.0
 nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/libnux-3.0.so.0
 nux::WindowThread::DoProcessEvent(nux::Event&) () from /usr/lib/libnux-3.0.so.0
Title: compiz crashed with SIGSEGV in nux::GraphicsDisplay::StartDndDrag()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceSource:
 #0 0xb4b2f2eb in ?? ()
 #1 0x09503ac0 in ?? ()
 #2 0xb437a5c2 in ?? ()
 #3 0x08809e10 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Daniel van Vugt (vanvugt)]

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 910575, 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.