I was playing with CCSM key bindings and unity crashed. Sure CCSM is not supported, but IMHO unity should not crash in any situation :)
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.6.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Thu Mar 22 17:36:00 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0x7f81d07b14b7 <_ZN5unity2MT15GrabHandleGroup13forEachHandleERKSt8functionIFvRKN5boost10shared_ptrINS0_10GrabHandleEEEEE+7>: mov 0x20(%rdi),%rbx
PC (0x7f81d07b14b7) ok
source "0x20(%rdi)" (0x00000021) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
unity::MT::GrabHandleGroup::forEachHandle(std::function<void (boost::shared_ptr<unity::MT::GrabHandle> const&)> const&) () from /usr/lib/compiz/libunitymtgrabhandles.so
UnityMTGrabHandlesWindow::restackHandles() () from /usr/lib/compiz/libunitymtgrabhandles.so
UnityMTGrabHandlesScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libunitymtgrabhandles.so
CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20120228
FadeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libfade.so
Title: compiz crashed with SIGSEGV in unity::MT::GrabHandleGroup::forEachHandle()
UpgradeStatus: Upgraded to precise on 2012-02-23 (28 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare
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 #948252, 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.