compiz.real assert failure: *** glibc detected *** /usr/bin/compiz.real: corrupted double-linked list: 0x090273d8 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Was settings Appearance properties to None from Custom.
ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/
CompizPlugins: [core,move,
Date: Mon Oct 19 22:45:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
NonfreeKernelMo
Package: compiz-core 1:0.8.4-0ubuntu1
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8400 GS] [10de:0404] (rev a1)
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
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 cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/31/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F2 v01.04
dmi.board.
dmi.board.name: 2820h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq dc5800 Microtower
dmi.sys.vendor: Hewlett-Packard
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 #443361, 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.