32 bit compatible GL library missing.

[Nikolas Reist]

When installing the nvidia-current package the 32 bit compatibility is not set in /usr/lib32 (mesa is used instead). This does not allow applications that would need 3D acceleration to function correctly if they are 32 bit. Also there are no packages listed for this library in synaptic. I am not sure if it was overlooked or omitted but certain apps that are native will not run properly without it.

ProblemType: Bug
Architecture: amd64
Date: Fri Mar 26 23:52:39 2010
DistroRelease: Ubuntu 10.04
DkmsStatus:
 nvidia-current, 195.36.15, 2.6.32-16-generic, x86_64: installed
 nvidia-current, 195.36.15, 2.6.32-17-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: nknow Unknow
NonfreeKernelModules: nvidia
Package: nvidia-current 195.36.15-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=f4a96679-6051-458a-9c0f-3efa161a1c33 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: nvidia-graphics-drivers
Uname: Linux 2.6.32-17-generic x86_64
dmi.bios.date: 06/17/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MCP72P
dmi.board.vendor: nVIDIA
dmi.board.version: Unknow
dmi.chassis.asset.tag: Unknow
dmi.chassis.type: 3
dmi.chassis.vendor: Unknow
dmi.chassis.version: Unknow
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/17/2009:svnnknow:pnUnknow:pvr:rvnnVIDIA:rnMCP72P:rvrUnknow:cvnUnknow:ct3:cvrUnknow:
dmi.product.name: Unknow
dmi.sys.vendor: nknow
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-17-generic

[Robert Hooker (sarvatt)]

Can you please paste the output of

sudo update-alternatives --config gl_conf

and the contents of

/etc/ld.so.conf.d/GL.conf

As well as the output of

ls /usr/lib32/nvidia-current/

Sorry for the trouble and thanks! What native 32 bit app are you having problems with? This is not a problem on any of my systems so I think the configuration got messed up somehow on your machine.

[Nikolas Reist (zeroability)]

Ah, ok. I saw that buried in the regular /usr/lib/ and I guess it didn't occur to me that it would be that way under /usr/lib32. I didn't get a chance to verify that because I ended up installing a different os on my development machine so I wouldn't have to re-assign the library files to all applications that were not delivered by the repositories and use OpenGL. I really shouldn't have to. Was this an nVidia change or a Canonical change? The app was the native x86 version of Quake 4. The whole /usr/lib(x)/nvidia-current idea is probably not a good one unless all Linux Distributions are changing to this format. Even then, you are going to need to do a massive re-train of how to assign these libraries for legacy applications (meaning applications that were either developed before 10.04 or not following this library configuration). This will flood your forums and support system with a serious amount of posts and inquiries over one minor feature change. Is that acceptable?

[Robert Hooker (sarvatt)]

The location of libGL and such is handled through ld.so.conf. If something needs a 32 bit libGL it will know to look at /usr/lib32/nvidia-current/libGL.so.1. Mesa's is located at /usr/lib/mesa/libGL.so.1. If it was trying to use mesa then the drivers weren't properly installed which we would need the info I requested to figure out why that happened and fix it.

[Nikolas Reist (zeroability)]

From a fresh installation using VirtualBox:

sudo apt-get update
sudo apt-get upgrade
restart
sudo apt-get install nvidia-current
ls -la /usr/lib32/libGL* not found
sudo apt-get install mesa-utils ia32-libs
ls -la /usr/lib32/libGL*
lrwxrwxrwx 1 root root 15 2010-03-28 19:59 /usr/lib32/libGL.so -> mesa/libGL.so.1
lrwxrwxrwx 1 root root 11 2010-03-28 19:59 /usr/lib32/libGLU.so -> libGLU.so.1
lrwxrwxrwx 1 root root 20 2010-03-28 19:59 /usr/lib32/libGLU.so.1 -> libGLU.so.1.3.070701
-rw-r--r-- 1 root root 456380 2010-02-19 09:25 /usr/lib32/libGLU.so.1.3.070701

mesa-utils is required by another native application - playonlinux.

I had previously (when it was installed) downloaded the nvidia-current source and extracted the libGL-<nvidia-current version> and put it in the /usr/lib32 folder and attempted to symlink it to libGL.so and libGL.so.1. ldconfig did not properly update which it was my understanding that it was supposed to but I am not sure. Something is getting broken after mesa-utils install takes place so maybe it is a mesa-utils issue. At any rate there is a problem because the normal auto library linking that should be taking place is not.

[Robert Hooker (sarvatt)]

Ah the problem is because you installed nvidia-current with apt-get instead of using jockey, it requires manual intervention to set up the libGL alternatives at the moment if you do it that way. If you do not want to use the jockey gui (aka system - preferences - hardware drivers) then you can use
sudo jockey-text -e xorg:nvidia-current

or if X isn't available at all and you want to use apt-get, then after installing you can run
sudo update-alternatives –config gl_conf
(pick the nvidia-current option)
sudo ldconfig
then finally
sudo nvidia-xconfig

[Nikolas Reist (zeroability)]

I'm sorry if this seemed misleading. My initial install attempt was through jockey (i.e. ubuntu told me I had available restricted drivers and I chose the most recent version) when I had it running as a logical os. It produced these same results during the logical installation. Whether logical, or virtual and regardless of Jockey or apt-get, the results were identical. Something breaks how the 32 bit libGL is defined. Besides, regardless of how I choose to install a video driver in my system it should produce the same results.

[Nikolas Reist (zeroability)]

I would say that since the LTS has been released, this is a Beta bug, and there has been no activity that it is either fixed or abandoned. Please close the bug.

Thanks,

[Chris Halse Rogers (raof)]

Marking as invalid; this should be fixed in Lucid and subsequent releases.

[Jessie Morris (jessieamorris)]

This still affects me in 12.04. This has not been fixed. Come on people.

[Jim Salter (jrssnet)]

This is still affecting me as well. 12.04-LTS, clean install.