xorg glx module is missing

[Tomasz Sterna]

After todays upgrade of my Hardy installation, Compiz stopped working.
After some searching for the reason, it turned out that there is no GLX extension supported anymore.
After some more searching it turned out, that the xorg glx module is missing.

smoku@wing:~$ grep glx /var/log/Xorg.0.log
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules//libglx.so
dlopen: /usr/lib/xorg/modules//libglx.so: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules//libglx.so
(II) UnloadModule: "glx"
(EE) Failed to load module "glx" (loader failed, 7)

[Timo Aaltonen (tjaalton)]

Are you using nvidia? There are newer packages available which add a correct symlink to the nvidia library. You can do it yourself by moving /usr/lib/xorg/modules/libglx.so to /usr/lib/xorg/modules/extensions/.

[Leon (leonbo)]

Reinstalling nvidia did not work for me. This did:

cd /usr/lib/xorg/modules/
ln extensions/libglx.so.169.09 libglx.so.169.09

[Michael Kuhn (suraia)]

I can confirm this, even with the latest packages, on amd64.
From a quick look at the source package it seems that there is an extra file for the links on amd64 which apparently wasn't corrected.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-restricted-modules-2.6.24 - 2.6.24.9-8.24

---------------
linux-restricted-modules-2.6.24 (2.6.24.9-8.24) hardy; urgency=low

  * This time fix the libglx.so link path for amd64, and while at it do
    the same for lintian overrides. (LP: #192253)

 -- Timo Aaltonen <email address hidden> Sat, 16 Feb 2008 09:38:46 +0200

[Tomasz Sterna (smoku)]

Yes, I am using nvidia. Reinstalling nvidia-glx-new did not help.

smoku@wing:~$ uname -a
Linux wing 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

smoku@wing:~$ dpkg -l | grep 'nvidia\|restricted'
ii linux-restricted-modules-2.6.22-14-generic 2.6.22.5-14.1 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restricted-modules-2.6.24-2-386 2.6.24.3-2.9 Non-free Linux 2.6.24 modules on 386
ii linux-restricted-modules-2.6.24-2-generic 2.6.24.3-2.9 Non-free Linux 2.6.24 modules on x86/x86_64
ii linux-restricted-modules-2.6.24-3-generic 2.6.24.4-3.10 Non-free Linux 2.6.24 modules on x86/x86_64
ii linux-restricted-modules-2.6.24-4-386 2.6.24.6-4.15 Non-free Linux 2.6.24 modules on 386
ii linux-restricted-modules-2.6.24-4-generic 2.6.24.6-4.15 Non-free Linux 2.6.24 modules on x86/x86_64
ii linux-restricted-modules-2.6.24-5-generic 2.6.24.6-5.16 Non-free Linux 2.6.24 modules on x86/x86_64
ii linux-restricted-modules-2.6.24-7-generic 2.6.24.9-8.21 Non-free Linux 2.6.24 modules on x86/x86_64
ii linux-restricted-modules-2.6.24-8-generic 2.6.24.9-8.22 Non-free Linux 2.6.24 modules on x86/x86_64
ii linux-restricted-modules-common 2.6.24.9-8.22 Non-free Linux 2.6.24 modules helper script
ii linux-restricted-modules-generic 2.6.24.8.8 Restricted Linux modules for generic kernels
ii nvidia-glx-new 169.09+2.6.24.9-8.22 NVIDIA binary XFree86 4.x/X.Org 'new' driver
ii nvidia-kernel-common 20051028+1ubuntu8 NVIDIA binary kernel module common files
rc restricted-manager 0.33.1 manage non-free hardware drivers - GNOME fro
rc restricted-manager-core 0.33.1 manage non-free hardware drivers
ii ubuntu-restricted-extras 12 Commonly used restricted packages

[josejoe (jsschulz)]

After doing this fix, my current custom themes no longer apply. It says they are selected and working, but visually they are gone,.

[Cleber Santz (clebersantz)]

Same problem here, fixed with correction of broken link libglx.so

$ uname -a
Linux n4shost 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux

$ lspci | grep nVidia
02:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2)

[Timo Aaltonen (tjaalton)]

no need to confirm anything anymore. Just wait until your package mirror has the updated packages and upgrade.

josejoe: some other update did that, the driver version was not changed and it can't break like that anyway.

[thecure (keith-k)]

Running Hardy... This AM after updates same problem. Leon's solution worked for me.

"Reinstalling nvidia did not work for me. This did:

cd /usr/lib/xorg/modules/
ln extensions/libglx.so.169.09 libglx.so.169.09"

[Nael Masood (neochaos)]

I was going to reply that this isn't an amd64-exclusive problem; I'm running the x86 version of hardy and the nVidia driver there had the broken link, too.

[Anders Kaseorg (andersk)]

This still isn't fixed in nvidia-glx-new 169.09+2.6.24.9-8.24 (which Launchpad says is the current version). The package contains a symlink named
  /usr/lib/xorg/modules/extensionslibglx.so
instead of
  /usr/lib/xorg/modules/extensions/libglx.so

[Joost Hink (johink-quicknet)]

After:

cd /usr/lib/xorg/modules/
ln extensions/libglx.so.169.09 libglx.so.169.09

This fixed it for me:

cd /usr/lib/xorg/modules/
sudo rm libglx.so
sudo ln extensions/libglx.so.169.09 libglx.so

And rebooting. (Running x86 version of Hardy, nvidia fx5200)

[mattismyname (mattismyname)]

I confirm this issue on my Hardy system as well. Still exists as of today.

[mattismyname (mattismyname)]

Joost-

Is there a reason you created a hardlink (ln) instead of a symbolic link (ln -s)?

Thanks!

-Matt

[Joost Hink (johink-quicknet)]

Matt-

Not really just my ignorance and very basic understanding of the linux commands

[Francesco "Zeirus" Sorrentino (zeirus)]

I've applicated the Joost Hink's solution:

cd /usr/lib/xorg/modules/
sudo rm libglx.so
sudo ln extensions/libglx.so.169.09 libglx.so

And rebooting.

Now it's all rights! ;)

[Daniel Hahler (blueyed)]

Fixed in 2.6.24.9-8.25:

linux-restricted-modules-2.6.24 (2.6.24.9-8.25) hardy; urgency=low

  * nvidia-glx.links.amd64.in: sigh, add a missing slash. (LP: 192253)

 -- Timo Aaltonen <email address hidden> Sun, 17 Feb 2008 09:34:01 +0200