package nvidia-glx None failed to install/upgrade: subprocess post-removal script returned error exit status 2

Bug #130208 reported by Jeff Anderson
86
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: nvidia-glx

Attempting to purge nvidia-glx via synaptic (Not Installed (residual configuration) ) when nvidia-glx-new is install causes this bug.

ProblemType: Package
Architecture: i386
Date: Fri Aug 3 12:25:51 2007
Dependencies:

DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-removal script returned error exit status 2
NonfreeKernelModules: nvidia
Package: nvidia-glx None
PackageArchitecture: i386
SourcePackage: linux-restricted-modules-2.6.22
Title: package nvidia-glx None failed to install/upgrade: subprocess post-removal script returned error exit status 2
Uname: Linux valhalla 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux

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

Jeff:
Thank you for your bug report. Did you install either of Envy/Automatrix or manually install the NVIDIA drivers?

Changed in linux-restricted-modules-2.6.22:
status: New → Incomplete
Revision history for this message
Jeff Anderson (jander99) wrote : Re: [Bug 130208] Re: package nvidia-glx None failed to install/upgrade: subprocess post-removal script returned error exit status 2

Manual install via aptitude.

Thanks.

Sitsofe Wheeler wrote:
> Jeff:
> Thank you for your bug report. Did you install either of Envy/Automatrix or manually install the NVIDIA drivers?
>
> ** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
> Status: New => Incomplete
>
>

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

Jeff:
From the regular repositories?

Revision history for this message
Jeff Anderson (jander99) wrote :

Correct. Enabled universe and multiverse for all the ubuntu repos.
Here's a copy of my sources.list. I have no additions to that in
sources.list.d/ I figure this is something to do with files being owned
by nvidia-glx-new that nvidia-glx is trying to get rid of.

Sitsofe Wheeler wrote:
> Jeff:
> >From the regular repositories?
>
>

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://us.archive.ubuntu.com/ubuntu/ gutsy main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ gutsy main restricted universe multiverse

deb http://us.archive.ubuntu.com/ubuntu/ gutsy-updates main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ gutsy-updates main restricted universe multiverse

deb http://us.archive.ubuntu.com/ubuntu/ gutsy-backports main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ gutsy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu gutsy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy-security main restricted universe multiverse

deb http://archive.ubuntu.com/ubuntu gutsy-proposed main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu gutsy-proposed main restricted universe multiverse

deb http://packages.medibuntu.org/ gutsy free non-free
deb-src http://packages.medibuntu.org/ gutsy free non-free

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

Jeff:
That doesn't count as a "manual" install : ) Setting bug back to new as information was supplied.

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → New
Revision history for this message
mcbutner (butner) wrote :

I'm not sure if this is related, but this was the only place my search turned up anything relevant. I'm having an issue purging the below package. Because it's apparently marked in my database for removal, any other updates I wish to process fail because this runs first.

(Reading database ... 100063 files and directories currently installed.)
Removing ecj-gcj ...
gcj-dbtool-4.1: symbol lookup error: gcj-dbtool-4.1: undefined symbol: _Jv_charClass
dpkg: error processing ecj-gcj (--remove):
 subprocess post-removal script returned error exit status 2
Removing ecj ...
Errors were encountered while processing:
 ecj-gcj
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up gjdoc (0.7.7-7build1) ...
gcj-dbtool-4.1: symbol lookup error: gcj-dbtool-4.1: undefined symbol: _Jv_charClass
dpkg: error processing gjdoc (--configure):
 subprocess post-installation script returned error exit status 2

Revision history for this message
Jonathan Michaels (jhmichaels) wrote :

Having the same problem.

Best guess is that nvidia-glx and nvidia-glx-new are stepping on each others toes. Doesn't affect performance but shows up as a residual config.

Revision history for this message
Kirk Turner (gameldar) wrote :

I'm having the same issue. Looking at the nvidia-glx.postrm in /var/lib/dpkg/info shows that it is trying to revert back to the xlibmesa version of the Open GL libraries, however they are currently owned by nvidia-glx-new.

Perhaps the attached patch can fix this - by checking if the files are owned by nvidia-glx?

Revision history for this message
mrAshley (launchpad-mrashley) wrote :

I am having the same problem. In the meantime is it possible for someone to post how one can just get rid of the residual config item?

Revision history for this message
Kirk Turner (gameldar) wrote :

A possible workaround (I've removed mine by applying the patched version to /var/lib/dpkg/info/nvidia-glx.postrm so I can't test this) however it might work by:

1. removing nvidia-glx-new
2. purging/removing nvidia-glx
3. reinstall nvidia-glx-new

There may be a catch with this (which results in the same error occurring) - in that the files will be owned by xlibmesa instead of nvidia-glx. In this case you can try reinstalling nvidia-glx, then purging/removing (the setting up of the ownership of these files is done by the preinst script).

Revision history for this message
Martin Heitzer (martin-heitzer) wrote :

Same problem here.

Revision history for this message
Martin Heitzer (martin-heitzer) wrote :

The workaround of Kirk Turner fixes the bug for me.

Revision history for this message
Kirk Turner (gameldar) wrote :

Here is the debdiff for this patch. It is slightly different to the previous one given that it is working for all the nvidia drivers - and does an explicit check for the package name matching.

Changed in linux-restricted-modules-2.6.22:
status: New → Confirmed
Revision history for this message
Teddyber (teddyber) wrote :

may i help by saying that i solved that same problem on my machine with these commands :

sudo dpkg-divert --remove /usr/X11R6/lib/libGL.so.1
sudo dpkg-divert --remove /usr/X11R6/lib/libGL.so.1.2
sudo dpkg-divert --remove /usr/lib/xorg/modules/libGLcore.so
sudo apt-get install nvidia-glx-new

Timo Aaltonen (tjaalton)
Changed in linux-restricted-modules-2.6.22:
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  [ Timo Aaltonen ]
  * nvidia-glx*:
    - When using the nvidia-settings binary for storing
      values in xorg.conf it clutters up the file with unneeded settings,
      and some are just plain wrong nowadays (the mouse device for
      instance). So, don't ship the version included in the drivers, instead
      Suggest nvidia-settings -package (again), and fix the issues there.
    - Don't ship nvidia-settings.desktop, only the .png file.
      Nvidia-settings will include the desktop-file.
  * rules:
    - Enable fglrx for -rt (LP: #182242)
  * rules, control.stub.in:
    - Enable -server flavor. (LP: #153011)
  * dvb:
    - Add dvb-usb-bluebird-01.fw (LP: #90723)
    - Add dvb-fe-tda10046.fw (LP: #107090)
  * ati: Update fglrx to 8-02. (LP: #173663, #189772)
  * {nvidia-glx,nvidia-glx-dev,xorg-driver-fglrx}.postrm.in
    - Check that the diverted file actually belongs to the current package
      before trying to remove the diversion. Thanks to Kirk Turner and
      Alberto Milone for patches, and Michael Vogt for review!
      (LP: #36625, #130208, #175789)
  * nvidia-glx.{preinst,postrm}.in, rules:
    - Fix the path of libglx.so.
  * rules:
    - Unexport CFLAGS and LDFLAGS to cope with the new dpkg-buildpackage.

  [ Alberto Milone ]
  * debian/lrm-video: Add support for EnvyNG.

 -- Timo Aaltonen <email address hidden> Thu, 14 Feb 2008 17:57:44 +0200

Changed in linux-restricted-modules-2.6.24:
status: Confirmed → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi jander99,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.22:
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → Invalid
Revision history for this message
Martin G Miller (mgmiller) wrote :

I think I need to reopen this bug. I have a system that I upgraded from 5.10 incrementally all the way to 8.10. I was recently cleaning up some residual config files and ran across this nvidia-glx problem. In my case, it is conflicting with the nvidia-glx-177. I know it used to run nvidia-glx-new at some time in the past with a different video card. Here is the output of the removal error messages:
E: nvidia-glx: subprocess post-removal script returned error exit status 2

(Reading database ... 223268 files and directories currently installed.)
Removing nvidia-glx ...
Purging configuration files for nvidia-glx ...
dpkg-divert: mismatch on package
  when removing `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx'
  found `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-177'
dpkg: error processing nvidia-glx (--purge):
 subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
 nvidia-glx
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:

Any help would be appreciated.

Revision history for this message
Martin G Miller (mgmiller) wrote :

Just as a follow up, I have never installed video drivers using envy or any of the other scripts. Everything came from the official Ubuntu repos.
Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

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