ccsm crashed with SIGSEGV in ccsCanDisablePlugin()

[roost]

tried to disable composite plug in so that i could re enable it to fix a black box around my cairo dock. As soon as i clicked to uncheck composite plugin compfiz settings manager closed and system became unresponsive and had to hold power button in to reboot computer using ubuntu 11.10 beta 2 , compizconfig-settings-manager 0.9.5.92-0ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compizconfig-settings-manager 0.9.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 8 21:56:27 2011
ExecutablePath: /usr/bin/ccsm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ccsm
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd8c01a41c7 <ccsCanDisablePlugin+455>: movl $0x1,0x18(%r13)
 PC (0x7fd8c01a41c7) ok
 source "$0x1" ok
 destination "0x18(%r13)" (0x00000018) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compizconfig-settings-manager
StacktraceTop:
 ccsCanDisablePlugin () from /usr/lib/libcompizconfig.so.0
 ?? () from /usr/lib/python2.7/dist-packages/compizconfig.so
 ?? ()
 ?? ()
 PyEval_EvalFrameEx ()
Title: ccsm crashed with SIGSEGV in ccsCanDisablePlugin()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #833326, 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.