compiz assert failure: *** glibc detected *** compiz: free(): corrupted unsorted chunks: 0x08f1a050 ***
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nux (Ubuntu) |
New
|
High
|
Unassigned | ||
Bug Description
Closed Firefox by the Close button in the window decoration, desktop hanging some seconds before Firefox actually closing, then this crash report.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-
ApportVersion: 1.23-0ubuntu2
Architecture: i386
AssertionMessage: *** glibc detected *** compiz: free(): corrupted unsorted chunks: 0x08f1a050 ***
Date: Thu Oct 6 08:31:52 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
Title: compiz assert failure: *** glibc detected *** compiz: free(): corrupted unsorted chunks: 0x08f1a050 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors:
(nautilus:3383): Gtk-CRITICAL **: gtk_action_
(nautilus:3383): Gtk-CRITICAL **: gtk_action_
| visibility: | private → public |
| Changed in nux (Ubuntu): | |
| importance: | Undecided → High |
| milestone: | none → ubuntu-11.10 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-i386-retrace |
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 #868293, 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.