ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #66634
[Bug 571746] Re: ld ignores entry in ld.so.conf telling where to find libGL.so.1 from nvidia-current
apport information
** Tags added: apport-collected
** Description changed:
Actually I'm not sure if this is a linker related issue or if it relates
to the nvidia-current package.
After upgrading to the lucid release candidate, ld wants to link with
the libGL.so.1 from /usr/lib, rather than with the one from /usr/lib
/nvidia-current, although in /etc/ld.so.conf, one can find the entry:
include /etc/ld.so.conf.d/*.conf and nvidia-current is installed
properly. Even when editing ld.so.conf so that their are lines
surrounding the above mentioned line telling the linker to search for
shared objects in /usr/lib/nvidia-current, the behavior wouldn't be as
expected.
Only when setting LD_LIBRARY_PATH to /usr/lib/nvidia-current , ld knows
where to find libGL.so.1(i.e. in /usr/lib/nvidia-current).
Searching the internet for similar topics, I found this post and maybe
it relates to my problem: http://www.mail-archive.com/mesa3d-
dev@xxxxxxxxxxxxxxxxxxxxx/msg11607.html
As I know, that this issue is probably tough to reproduce, I attached
the output of the following commands / content of the following files:
lsb_release -rd
lsconfig -p
lspci
/etc/ld.so.conf
/etc/ld.so.conf.d/GL.conf -> /etc/alternatives/gl_conf
+ ---
+ Architecture: i386
+ DistroRelease: Ubuntu 10.04
+ DkmsStatus:
+ nvidia-current, 195.36.15, 2.6.31-19-generic, i686: installed
+ nvidia-current, 195.36.15, 2.6.32-21-generic, i686: installed
+ blcr, 0.8.2, 2.6.31-19-generic, i686: installed
+ virtualbox-ose, 3.1.6, 2.6.31-19-generic, i686: installed
+ virtualbox-ose, 3.1.6, 2.6.32-21-generic, i686: installed
+ GdmLog1:
+ Fatal server error:
+ Server is already active for display 0
+ If this server is no longer running, remove /tmp/.X0-lock
+ and start again.
+ GdmLog2:
+ Fatal server error:
+ Server is already active for display 0
+ If this server is no longer running, remove /tmp/.X0-lock
+ and start again.
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. R560
+ NonfreeKernelModules: nvidia
+ Package: nvidia-graphics-drivers (not installed)
+ ProcCmdLine: root=UUID=43824c72-360a-4202-8555-ad9615fcd5f1 ro quiet splash
+ ProcEnviron:
+ LANGUAGE=
+ PATH=(custom, user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
+ Tags: lucid lucid
+ Uname: Linux 2.6.32-21-generic i686
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
+ dmi.bios.date: 12/09/2008
+ dmi.bios.vendor: Phoenix Technologies Ltd.
+ dmi.bios.version: 09LA.7027.20081209.JJC
+ dmi.board.name: R560
+ dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.chassis.version: N/A
+ dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
+ dmi.product.name: R560
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ glxinfo:
+ Error: couldn't find RGB GLX visual or fbconfig
+ name of display: :0.0
+ system:
+ distro: Ubuntu
+ codename: lucid
+ architecture: i686
+ kernel: 2.6.32-21-generic
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/46519208/BootDmesg.txt
--
ld ignores entry in ld.so.conf telling where to find libGL.so.1 from nvidia-current
https://bugs.launchpad.net/bugs/571746
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
References