Compiz crashed on closing Banshee

[bastubis]

This happens on 11.10 with various packages - this time it was Banshee but it also happens frequently with Firefox and even more frequently with Libre Office. If running fullscreen (I had Banshee fullscreen) Banshee freezes when I click the close button then 'compiz closed unexpectedly', then compiz restarts. Firefox in fullscreen often does the same thing. If not running fullscreen, the buttons frequently disappear and don't reappear on mouseover, f4 doesn't work, and all I can do is file -> quit -- if I'm lucky as sometimes the desktop freezes altogether, I lose the keyboard/mouse and have to shut it down with the power button.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: i386
AssertionMessage: *** glibc detected *** compiz: double free or corruption (!prev): 0xb3db4800 ***
CrashCounter: 1
Date: Sat Oct 1 01:34:52 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
 __kernel_vsyscall ()
 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
Title: compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0xb3db4800 ***
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 #857738, 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.