Comment 4 for bug 1056615

==6009== Invalid read of size 8
==6009== at 0x9252EA9: ccsGNOMEIntegrationBackendReadISAndSetSettingForType (ccs_gnome_integration.c:170)
==6009== by 0x925301A: ccsGNOMEIntegrationBackendReadOptionIntoSetting (ccs_gnome_integration.c:235)
==6009== by 0x9251CB6: readSetting (gconf.c:496)
==6009== by 0x7C83D5A: ccsReadPluginSettingsDefault (main.c:3461)
==6009== by 0x7C7748A: ccsLoadPluginSettings (compiz.cpp:3263)
==6009== by 0x7C82AC1: ccsContextNew (main.c:545)
==6009== by 0x7A541F9: __pyx_tp_new_12compizconfig_Context (compizconfig.c:4174)
==6009== by 0x4DB5E7: ??? (in /usr/bin/python2.7)
==6009== by 0x4E9F35: PyObject_Call (in /usr/bin/python2.7)
==6009== by 0x498469: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==6009== by 0x498601: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==6009== by 0x49F1BF: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==6009== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==6009==
==6009==
==6009== Process terminating with default action of signal 11 (SIGSEGV)
==6009== Access not within mapped region at address 0x0
==6009== at 0x9252EA9: ccsGNOMEIntegrationBackendReadISAndSetSettingForType (ccs_gnome_integration.c:170)
==6009== by 0x925301A: ccsGNOMEIntegrationBackendReadOptionIntoSetting (ccs_gnome_integration.c:235)
==6009== by 0x9251CB6: readSetting (gconf.c:496)
==6009== by 0x7C83D5A: ccsReadPluginSettingsDefault (main.c:3461)
==6009== by 0x7C7748A: ccsLoadPluginSettings (compiz.cpp:3263)
==6009== by 0x7C82AC1: ccsContextNew (main.c:545)
==6009== by 0x7A541F9: __pyx_tp_new_12compizconfig_Context (compizconfig.c:4174)
==6009== by 0x4DB5E7: ??? (in /usr/bin/python2.7)
==6009== by 0x4E9F35: PyObject_Call (in /usr/bin/python2.7)
==6009== by 0x498469: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==6009== by 0x498601: PyEval_EvalFrameEx (in /usr/bin/python2.7)
==6009== by 0x49F1BF: PyEval_EvalCodeEx (in /usr/bin/python2.7)
==6009== If you believe this happened as a result of a stack
==6009== overflow in your program's main thread (unlikely but
==6009== possible), you can try to increase the size of the
==6009== main thread stack using the --main-stacksize= flag.
==6009== The main thread stack size used in this run was 8388608.