compiz crashed with SIGABRT in raise()

[mdmcginn]

Began when I switched to Quantal beta. Started working yesterday, then stopped after today's upgrades. Unity taskbar freezes then disappears. Can open files but windows have no minimize/maximize/close buttons. Running "unity&" in a terminal starts it up again and lets me work.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.2+bzr3377-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.5.3-0ubuntu1
Architecture: i386
CheckboxSubmission: 23f9165fb5269142dfde45beba11cbff
CheckboxSystem: edda5d4f616ca792bf437989cb597002
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CrashCounter: 1
Date: Sat Sep 29 19:48:24 2012
DistUpgraded: 2012-09-23 07:12:51,565 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.1.18, 3.2.0-31-generic-pae, i686: installed
 virtualbox, 4.1.18, 3.5.0-15-generic, i686: installed
 virtualbox, 4.1.18, 3.5.0-16-generic, i686: installed
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1348156199
GraphicsCard:
 Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2a08]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: HP Pavilion 061 PS500AA-ABA A824N
ProcCmdline: compiz --sm-client-id 1034b929b65e45a9ed132509101020684200000016960046
ProcCwd: /home/michael
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=2d538d30-263b-48c6-9250-81f4004b1215 ro vga=789 quiet splash vt.handoff=7
Signal: 6
SourcePackage: compiz
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-09-23 (6 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 02/16/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.18
dmi.board.name: Goldfish2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.18:bd02/16/2005:svnHPPavilion061:pnPS500AA-ABAA824N:pvr0nB1211RE101GOLDF00:rvnASUSTeKComputerINC.:rnGoldfish2:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: PS500AA-ABA A824N
dmi.product.version: 0nB1211RE101GOLDF00
dmi.sys.vendor: HP Pavilion 061
version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu2

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