compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x00007fa248593900 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nux |
Fix Released
|
Undecided
|
Unassigned | ||
Unity |
Fix Released
|
Critical
|
Jason Smith | ||
nux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
Critical
|
Jason Smith |
Bug Description
Dont know what happened
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
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** compiz: double free or corruption (!prev): 0x00007fa248593900 ***
CrashCounter: 1
Date: Thu Sep 29 21:41:14 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
__libc_message (do_abort=2, fmt=0x7fa26815a0d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7fa26815a278 "double free or corruption (!prev)", ptr=<optimized out>) at malloc.c:6283
__GI___libc_free (mem=<optimized out>) at malloc.c:3738
nux::IOpenGLSu
nux::IOpenGLTe
Title: compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x00007fa248593900 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in unity: | |
status: | New → Confirmed |
Changed in nux: | |
status: | New → Confirmed |
Changed in nux: | |
status: | Invalid → Fix Released |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in nux (Ubuntu): | |
status: | Invalid → Fix Released |
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.