*** glibc detected *** /usr/bin/compiz.real: corrupted double-linked list:
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-180 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
this may be the same as bug#392850 similar message in output of xsession error file on /home/user/
I do run an nvidia card and it says that the driver is in use so I see no issue there but with this install I am using 185 driver and used to be 180 if that makes any difference but I do not see a choice method for this system as there are few articles on it
Description: Ubuntu karmic (development branch)
Release: 9.10
Installed: 1:0.8.3+
Candidate: 1:0.8.3+
Version table:
*** 1:0.8.3+
500 http://
100 /var/lib/
if any additional info needed please let me know
ProblemType: Bug
Architecture: amd64
CompizPlugins: [core,move,
Date: Sun Oct 11 09:55:51 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Beta amd64 (20090929.2)
MachineType: Gigabyte Technology Co., Ltd. EP43-UD3L
NonfreeKernelMo
Package: compiz 1:0.8.3+
PackageArchitec
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G96 [GeForce 9400 GT] [10de:065b] (rev a1)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0-1ubuntu2
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SourcePackage: compiz
Uname: Linux 2.6.31-11-generic x86_64
dmi.bios.date: 02/25/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: EP43-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: EP43-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.31-11-generic
It definitely crashes inside nvidia's libGL but it's different looking enough to probably be a new bug instead of a dupe of that one.