As /usr/lib/libGL.so is just a symlink, I noted down the destination and
then removed /usr/lib/libGL.so. After this the aptitude upgrade for the
package succeeds. Turns out the new link is identical to the old one,
so it was only a case of the script being confused somehow.
Nothing more needed h
I take it this bug must not be widespread... Still does anyone have any
suggestions? Would it be safe to just backup libGL.so and then try
again? The specific error being...
Preparing to replace nvidia-glx-173-dev 173.14.20-0ubuntu3 (using
.../nvidia-glx-173-dev_173.14.20-0ubuntu4_i386.deb) ..
Ah, that's a different question...
Regarding Karmic and nvidia-173.14.20, no I have never used the basic
nvidia installer. I have only used aptitude and synaptic.
I think when I first installed kubuntu 9.04 on my machine back in May I
had some nvidia problems and I tried several things to get th
No. I showed what I did. Namely...
$ sudo aptitude full-upgrade
--
package nvidia-glx-173-dev 173.14.20-0ubuntu3 failed to install/upgrade:
subprocess new pre-installation script returned error exit status 2
https://bugs.launchpad.net/bugs/456075
You received this bug notification because you
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/34021469/AptOrdering.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34021470/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/34021471/CurrentDmesg.txt
** Att
Public bug reported:
$ sudo aptitude full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages will be upgraded:
nvidia-glx-173-dev
1 packages upgraded, 0 new
6 matches
Mail list logo
