compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x0000000002a4d970 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
High
|
Unassigned |
Bug Description
Touched the touchpad mouse, compiz crashed and restarted.
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): 0x0000000002a4d970 ***
CrashCounter: 1
Date: Tue Oct 4 14:47:24 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
__libc_message (do_abort=2, fmt=0x7feb253280d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7feb25328278 "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): 0x0000000002a4d970 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nautilus:12705): Gtk-CRITICAL **: gtk_action_
(nautilus:12705): Gtk-CRITICAL **: gtk_action_
(nm-applet:12695): GLib-CRITICAL **: g_hash_
(gnome-
(gnome-
visibility: | private → public |
Changed in nux (Ubuntu): | |
importance: | Undecided → High |
milestone: | none → ubuntu-11.10 |
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.