compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x00000000052e06f0 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
On launching an application, compiz often blows up and restarts with all apps in one desktop.
This may be a dupe, but posting just in case since the address looks different.
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-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** compiz: double free or corruption (!prev): 0x00000000052e06f0 ***
CrashCounter: 1
Date: Wed Oct 5 09:50:46 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
__libc_message (do_abort=2, fmt=0x7f57c40d30d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7f57c40d3278 "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): 0x00000000052e06f0 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev root sambashare
XsessionErrors:
(SparkleShare:
(nautilus:7586): Gtk-CRITICAL **: gtk_action_
(nautilus:7586): Gtk-CRITICAL **: gtk_action_
(indicator-
(SparkleShare:
visibility: | private → public |
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.