compiz.real assert failure: *** glibc detected *** /usr/bin/compiz.real: double free or corruption (!prev): 0x090efda0 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
laptop x71sl
ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/
CompizPlugins: [core,ccp,
CrashCounter: 1
Date: Wed Sep 2 18:03:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: ASUSTeK Computer Inc. X71SL
NonfreeKernelMo
Package: compiz-core 1:0.8.2-0ubuntu16
PccardctlIdent:
PccardctlStatus:
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G98 [GeForce 9300M GS] [10de:06e9] (rev a1)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=pl_PL.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git200908
libdrm2 2.4.12+
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-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/05/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.
dmi.board.name: X71SL
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X71SL
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-9-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.