compiz.real assert failure: *** glibc detected *** /usr/bin/compiz.real: double free or corruption (!prev): 0x09ba4008 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
tfztfr
ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/
CompizPlugins: [core,move,
CrashCounter: 1
Date: Mon Nov 2 12:08:04 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: ASUSTeK Computer Inc. U3S
NonfreeKernelMo
Package: compiz-core 1:0.8.4-0ubuntu2
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G86 [GeForce 8400M G] [10de:0428] (rev a1)
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
Signal: 6
SourcePackage: compiz
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
?? () from /lib/tls/
?? () from /lib/tls/
Title: compiz.real assert failure: *** glibc detected *** /usr/bin/
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video
dmi.bios.date: 01/28/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 305
dmi.board.
dmi.board.name: U3S
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: U3S
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-14-generic
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 #422391, 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.