[envy] nvidia-glx fails to install during upgrade

Bug #98504 reported by scorpioxy
6
Affects Status Importance Assigned to Milestone
Software Updater
Invalid
Undecided
Unassigned
linux-restricted-modules-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

During my upgrade to Feisty using update-manager, the following message was displayed:

<Quote>
Could not install '/var/cache/apt/archives/nvidia-glx_1.0.9755+2.6.20.4-13.12_i386.deb'
The upgrade has aborted. Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport.
subprocess pre-installation script returned error exit status 2
</Quote>

This led to the update procedure to abort but after finishing the installation of the packages(so technically, the upgrade was compete). This led to failure in X during next reboot which caused me to manually remove the previous nvidia-glx and then install the new one and do a dpkg-reconfigure of restricted-modules(due to a missing nvidia.ko).

I had previously used the "envy" tool to install the nvidia driver.

Revision history for this message
scorpioxy (alaasalman) wrote :

Attached are the /var/log/dist-upgrade/ files.

Revision history for this message
Michael Vogt (mvo) wrote :

Closing the update-manager task, its just the messenger here.

Changed in update-manager:
status: Unconfirmed → Confirmed
status: Confirmed → Rejected
Revision history for this message
Michael Vogt (mvo) wrote :

Here is the error:

Unpacking linux-restricted-modules-2.6.20-13-386 (from .../linux-restricted-modules-2.6.20-13-386_2.6.20.4-13.12_i386.deb) ...
rver-xorg-video-vmware_1%3a10.15.0-0ubuntu1_i386.deb) ...
Preparing to replace nvidia-glx 1.0.9746 (using .../nvidia-glx_1.0.9755+2.6.20.4-13.12_i386.deb) ...
dpkg-divert: `diversion of /usr/lib/xorg/modules/libglx.so to /usr/lib/nvidia/libglx.so.xlibmesa by nvidia-glx' clashes with `diversion of /usr/lib/xorg/modules/extensions/libglx.so to /usr/lib/nvidia/libglx.so.xlibmesa by nvidia-glx'
dpkg: error processing /var/cache/apt/archives/nvidia-glx_1.0.9755+2.6.20.4-13.12_i386.deb (--unpack):
 subprocess pre-installation script returned error exit status 2

I suspect "envy" is responsbile for the failure, but I'm not familiar with this tool.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

scorpioxy:
Can you indicate whether you had previously installed envy on this machine?

Setting to needsinfo pending reply from scorpioxy.

Changed in linux-restricted-modules-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
scorpioxy (alaasalman) wrote :

Yes i had previously installed envy and used it to install the nvidia driver. This is mentioned in the bug description.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

scorpioxy:
Indeed you did. My apologies about that - I've been staring at hundreds of bugs over the past few days. Setting back to unconfirmed. This is probably a dup of other "upgrade fails after using envy" bugs like bug #107915

Changed in linux-restricted-modules-2.6.20:
status: Needs Info → Unconfirmed
Revision history for this message
scorpioxy (alaasalman) wrote :

No problem. Thanks for all the hard work. Anything i can do to help, let me know.

bug #107915 on the surface resembles this bug except that his log of the upgrade process contains several additional issues. Plus there's the issue that here, it complained about the diversion and then returned the pre-installation error code. Oh, and also his computer froze(so he says at the top) while mine simply aborted the upgrade process. We do seem to have envy in common so maybe envy is writing out the pre-installation script in a wrong way after the driver compilation. I tried to look at the envy source code, but i am not a python person so i couldn't quite understand it.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

scorpioxy:
I *think* it's simply a dependency chain problem. If you pull up the nvidia-glx deb before you run the updater you should be able to work around the issue (you this this at your own risk though!)...

There are other updater/envy bugs (like Bug #105115 ) that might be a better fit for your issue.

Revision history for this message
scorpioxy (alaasalman) wrote :

Thanks, but like i said in my bug report, i fixed the issue a long time ago. I've been running feisty for a while now and i am no longer using envy. I reported this bug so that you know that something was causing upgrades to fail and if it is really envy's fault, then the author should be informed. Feel free to close this bug if you think that it is already reported and will be taken care of in another bug report.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Rejecting this bug as there are others that are very similar still open.

Changed in linux-restricted-modules-2.6.20:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.