package libgl1-mesa-glx 7.4-0ubuntu3 failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile returned error exit status 2

[Jean-Paul Calderone]

I had an error when upgrading Jaunty with update manager.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release i386 (20090420.1)
Package: libgl1-mesa-glx 7.4-0ubuntu3
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
SourcePackage: mesa
Title: package libgl1-mesa-glx 7.4-0ubuntu3 failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Uname: Linux 2.6.28-11-generic i686

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef]
     Subsystem: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] [1022:2000]

[Martin Olsson (mnemo)]

@Jean-Paul Calderone, could you attach the output of "dpkg -l" from this machine please?

[Jean-Paul Calderone (exarkun)]

Attaching.

[Martin Olsson (mnemo)]

@Jean-Paul, assuming you apt cache is intact... what does it print if you run:
md5sum /var/cache/apt/archives/libgl1-mesa-dri_7.4-0ubuntu3.1_i386.deb

[Jean-Paul Calderone (exarkun)]

Hi Martin,

Here you go:

$ md5sum /var/cache/apt/archives/libgl1-mesa-dri_7.4-0ubuntu3.1_i386.deb
a318f2d32966b43db95c810fc75ae911 /var/cache/apt/archives/libgl1-mesa-dri_7.4-0ubuntu3.1_i386.deb

[Martin Olsson (mnemo)]

Strange, I have the exact same version as you and mine works fine. So at least the file wasn't corrupted while it downloaded or something like that.

I see you still have the 0ubuntu3 version installed, do you get any error if you run:
sudo dpkg -i /var/cache/apt/archives/libgl1-mesa-*3.1_i386.deb

And what happens if you run update-manager again, does it still say there is a mesa updating waiting?

[Jean-Paul Calderone (exarkun)]

update-manager does still say I have mesa updates waiting. Using dpkg to install the .deb from /var/cache/apt/archives succeeds with no error. I did this for two of the three packages which failed to install, libgl1-mesa-glx and libgl1-mesa-dri. I tried using update-manager to install the third, libglu1-mesa (along with a bunch of other updates that had come along). update-manager still failed to install the package.

[Martin Olsson (mnemo)]

OK, so its not a bug in the mesa package itself.

[Martin Olsson (mnemo)]

I'm opening this against update-manager since update-manager fails to install the update despite it being installable using "dpkg -i".

Note that we have not seen any other reports similar to this one so it sounds to me that there is some special config or similar on this bug that prevents update-manager from installing it.

Also, the dpkg -l shows update-manager 0.111.7 but I have 0.111.9 on my jaunty machine (maybe you have since posting the dpkg -l also been updated to 0.111.9?).

[Jean-Paul Calderone (exarkun)]

I have 0.111.9 now as well. I tried using it to install the package again, just to make sure, and it failed the same way.

[waltm (jjmaden)]

I'm getting a similar error when trying to upgrade. I get the same md5sum as above but could not update manually as above. Attached is the text from trying, it seems to get hung up with the error

 unable to create `./usr/lib/libGL.so.1.2': No such file or directory

Please let me know if other info is needed.

[Jean-Baptiste Lallement (jibel)]

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 latest Ubuntu release? Thanks in advance.

[Jean-Baptiste Lallement (jibel)]

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!