/usr/lib32/libGL.so.1 prevents Doom 3 from starting

[Dmitry Pankratov]

Ubuntu 11.10 AMD64.

After updating to the latest ia32-libs (version 20090808ubuntu22) doom3 executable does not start properly.
Error message is: Couldn't get a visual.

I have tracked it down to /usr/lib32/libGL.so.1 library which causes this issue. In the previous version if the package this library is absent.

After deleting it and running ldconfig the game runs normally.

[Adam Conrad (adconrad)]

Is one of the binary drivers being used here? They used to divert /usr/lib32/libGL.so.1 out of the way to avoid these sorts of issues, but perhaps something regressed along the way.

[Dmitry Pankratov (dremon)]

Nvidia proprietary driver is actually installed, version 280.13-0ubuntu3.

[Scott Ritchie (scottritchie)]

Yeah it doesn't look like nvidia does this diversion anymore, perhaps it should.

[Steve Langasek (vorlon)]

It absolutely should not. The *native* nvidia and mesa drivers cooperate correctly - the newly introduced /usr/lib32/libGL.so.1 does *not* follow the same (carefully designed and tested) method of selecting the GL driver via update-alternatives.

I think you should revert your recent changes to mesa handling in ia32-libs. We are not ever going to have fully working 32-bit support for mesa + nvidia GL via ia32-libs, so we might as well stick with the previous known set of bugs - which also resulted in smaller ia32-libs package anyway.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Scott Ritchie (scottritchie)]

Do you think the existing libgl.so symlink that was there should be removed as well?

[Steve Langasek (vorlon)]

On Fri, Sep 16, 2011 at 10:30:55PM -0000, Scott Ritchie wrote:
> Do you think the existing libgl.so symlink that was there should be
> removed as well?

I think restoring the previous behavior is the best option at this point.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[Launchpad Janitor (janitor)]

This bug was fixed in the package ia32-libs - 20090808ubuntu24

---------------
ia32-libs (20090808ubuntu24) oneiric; urgency=low

  * Remove libllvm2.9 and DRI driver manual symlinks (LP: #851947)
  * Freshen packages
 -- Scott Ritchie <email address hidden> Wed, 28 Sep 2011 17:37:52 -0700

[Robert Hooker (sarvatt)]

Now we have no 32 bit accelerated GL for anyone except the ones using proprietary drivers. Is there no chance we could add multiarch libpciaccess so libgl1-mesa-dri:i386 is installable?

[Steve Langasek (vorlon)]

On Fri, Sep 30, 2011 at 02:38:04AM -0000, Robert Hooker wrote:
> Now we have no 32 bit accelerated GL for anyone except the ones using
> proprietary drivers.

LD_LIBRARY_PATH=/usr/lib32/mesa ?

> Is there no chance we could add multiarch libpciaccess so
> libgl1-mesa-dri:i386 is installable?

I don't think that can be justified as a freeze exception - given that this
is a problem that's been around for more than a full release cycle already.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[Pastor (sinel1980)]

The Bug#852873 (https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/852873) is set to be duplicate of this bug. But the solution written here to delete /usr/lib32/libGL.so.1 results on my Kubuntu x64 with error saying there's not this file when i try to run wine 3d games.
The working solution is from 852873 bug to set LD_LIBRARY_PATH (in my case it is for example command in shell: LD_LIBRARY_PATH=/usr/lib32/nvidia-current wine wow.exe)

[Dmitry Pankratov (dremon)]

Have you performed "sudo ldconfig" after file deletion?

[Albert Pool (albertpool)]

I have this issue after uninstalling proprietary drivers. When running with nvidia 280 it's fine.

[Albert Pool (albertpool)]

Uninstalling nvidia-current breaks this. So I guess the uninstall script of nvidia-current is to blame as well.