compi1z crashed with SIGSEGV in Glib::Source::prepare_vfunc() "ON EVERY BOOT"

[REWard]

THIS ERROR COMES UP EVERY TIME THE SYSTEM IS BOOTED UP. JUST AFTER THE DESKTOP SCREEN APPEARS. I HAVE LOADED THE ATI/AMD VIDEO DRIVER, WHICH IS NOW ACTIVATED AND THE ERROR STILL CAME UP.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.0~bzr2995-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 1.94-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,imgpng,regex,gnomecompat,snap,move,vpswitch,unitymtgrabhandles,grid,mousepoll,place,wall,session,animation,workarounds,fade,expo,scale,ezoom,unityshell]
CompositorRunning: compiz
CrashCounter: 1
Date: Tue Mar 6 16:41:48 2012
DistUpgraded: Log time: 2012-03-06 10:57:44.641065
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.911, 3.2.0-18-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV670 [Radeon HD 3870] [1002:9501] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited Sapphire Radeon HD 3870 PCIe 2.0 [174b:e620]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
JockeyStatus:
 xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
 xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use)
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=7e8fb122-d1d9-4c1c-bf04-c42f1497388e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fcf3a1d99ef <_ZN4Glib6Source13prepare_vfuncEP8_GSourcePi+15>: mov (%rdi),%rax
 PC (0x7fcf3a1d99ef) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 Glib::Source::prepare_vfunc(_GSource*, int*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_pending () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/compizconfig/backends/libgconf.so
Title: compiz crashed with SIGSEGV in Glib::Source::prepare_vfunc()
UpgradeStatus: Upgraded to precise on 2012-03-06 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/15/2006
dmi.bios.vendor: Award BIOS for Intel
dmi.bios.version: GC11010N.86A.0313.2006.0915.1840
dmi.board.name: D101GGC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD35788-310
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardBIOSforIntel:bvrGC11010N.86A.0313.2006.0915.1840:bd09/15/2006:svn:pn:pvr:rvnIntelCorporation:rnD101GGC:rvrAAD35788-310:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs 20090808ubuntu33
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[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 #932125, 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.