compiz assert failure: *** glibc detected *** compiz: double free or corruption (out): 0x00000000032a6280 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Enable scale-plugin in ccsm results in crash. Crash means, screen flickers, all open apps disappear, desktop is empty for a few seconds, then all open apps gather on first workspace. Afterwards all is functional again.
Similar bug 862938 is marked as fixed.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
AssertionMessage: *** glibc detected *** compiz: double free or corruption (out): 0x00000000032a6280 ***
CrashCounter: 1
Date: Sun Nov 20 18:45:49 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, no user)
LANG=de_DE.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
__libc_message (do_abort=2, fmt=0x7f46357a50d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7f46357a5258 "double free or corruption (out)", ptr=<optimized out>) at malloc.c:6283
__GI___libc_free (mem=<optimized out>) at malloc.c:3738
?? () from /usr/lib/
?? () from /usr/lib/
Title: compiz assert failure: *** glibc detected *** compiz: double free or corruption (out): 0x00000000032a6280 ***
UpgradeStatus: Upgraded to oneiric on 2011-10-28 (23 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #743638, 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.