ccsm crashed with SIGSEGV in ccsCanDisablePlugin()

[NofallYaqoo]

i think another bug ?
i dont know what exactly happened but my browser pop up and again i came here , two bugs in one day
what is happening to my OS's :(

NO NO, now i remember how this happened
i was opening (Ubuntu tweak)
and then this crash happened and i am very sure that's what exactly happened
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compizconfig-settings-manager 0.9.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Mar 17 09:17:43 2012
ExecutablePath: /usr/bin/ccsm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ccsm
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4f8d4a4 <ccsCanDisablePlugin+532>: movl $0x1,0xc(%eax)
 PC (0x04f8d4a4) ok
 source "$0x1" ok
 destination "0xc(%eax)" (0x0000000c) 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: Upgraded to oneiric on 2012-03-21 (1 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 this software 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.