Can't install/upgrade package nvidia-glx-180-dev with jaunty

[LGB [Gábor Lénárt]]

I can't upgrade package nvidia-glx-180-dev with up-to-date jaunty on 32 bit x86 machine:

root@oxygene:~# apt-get install nvidia-glx-180-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  nvidia-glx-180-dev
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/158kB of archives.
After this operation, 0B of additional disk space will be used.
Reading changelogs... Done
(Reading database ... 792787 files and directories currently installed.)
Preparing to replace nvidia-glx-180-dev 180.37-0ubuntu1 (using .../nvidia-glx-180-dev_180.37-0ubuntu2_i386.deb) ...
dpkg-divert: rename involves overwriting `/usr/lib/libGL.so' with
  different file `/usr/lib/nvidia/libGL.so.xlibmesa', not allowed
dpkg: error processing /var/cache/apt/archives/nvidia-glx-180-dev_180.37-0ubuntu2_i386.deb (--unpack):
 subprocess pre-installation script returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/nvidia-glx-180-dev_180.37-0ubuntu2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[LGB [Gábor Lénárt] (lgb)]

It seems that /usr/lib/nvidia/libGL.so.xlibmesa is a dead symlink:

lgb@oxygene:~$ ls -la /usr/lib/nvidia/libGL.so.xlibmesa
lrwxrwxrwx 1 root root 15 2009-03-03 00:22 /usr/lib/nvidia/libGL.so.xlibmesa -> libGL.so.180.35

libGL.so.180.35 does not exists (no, I haven't installed binary nvidia driver directly from nvidia or so, just ubuntu packages). I've just deleted that "dead" symlink, then the package configures normally, without error.

But this problem needs manual workaround as you can see.

[Bryce Harrington (bryce)]

Hi lgb,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.