CD upgrade fails

Bug #237965 reported by Fernando
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

I was just updating from a 7.10 CD install to 8.04

ProblemType: Package
Architecture: i386
Date: Fri Jun 6 13:03:28 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)

Package: update-manager 1:0.87.27
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.87.27 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.22-14-generic i686

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

Here is what is cauding the error:

Preparing to replace xfonts-100dpi 1:1.0.0-3 (using .../xfonts-100dpi_1%3a1.0.0-4_all.deb) ...
Unpacking replacement xfonts-100dpi ...
dpkg-deb (subprocess): error in buffer_read(stream): failed to write to pipe in copy: Input/output error
b) ...
dpkg-deb: subprocess paste returned error exit status 2
dpkg: error processing /var/cache/apt/archives/xfonts-100dpi_1%3a1.0.0-4_all.deb (--unpack):
 short read in buffer_copy (backend dpkg-deb during `./usr/share/fonts/X11/100dpi/symb18.pcf.gz')

This sounds like the CD might be broken (bad burn maybe?). Could you run a CD check please?

Thanks,
 Michael

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Fernando (linuxmercedes) wrote : Re: CD upgrade fails (bad burn?)

I'll run a CD check; however, it would surprise me because this disc was pressed by Canonical and mailed to me.

"Check finished: no errors found"

I guess to fix the problem I'd uninstall the xfonts-100dpi package and reinstall it?

Revision history for this message
Jayson Rowe (jayson.rowe) 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 update-manager:
status: Incomplete → Invalid
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.