package lilypond-doc None [modified: /var/lib/dpkg/info/lilypond-doc.list] failed to install/upgrade: short read in buffer_copy (backend dpkg-deb during `./usr/share/doc/lilypond/html/input/regression/lily-e0fb9af6f1.png')

Bug #323193 reported by Paul
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lilypond (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: lilypond

Synaptic failed to install this package on ubuntu studio intrepid

ProblemType: Package
Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 8.10
ErrorMessage: short read in buffer_copy (backend dpkg-deb during `./usr/share/doc/lilypond/html/input/regression/lily-e0fb9af6f1.png')
NonfreeKernelModules: wl
Package: lilypond-doc None [modified: /var/lib/dpkg/info/lilypond-doc.list]
PackageArchitecture: all
SourcePackage: lilypond
Title: package lilypond-doc None [modified: /var/lib/dpkg/info/lilypond-doc.list] failed to install/upgrade: short read in buffer_copy (backend dpkg-deb during `./usr/share/doc/lilypond/html/input/regression/lily-e0fb9af6f1.png')
Uname: Linux 2.6.27-3-rt x86_64

Revision history for this message
Paul (pcate) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

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.

Changed in lilypond (Ubuntu):
status: New → Incomplete
Changed in lilypond (Ubuntu):
assignee: nobody → albezambu (albertozamburlini)
status: Incomplete → New
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

@albezambu, why did you change the status to New ? have you got the same error ? It's likely due to a full hard drive or a disk error.

Changed in lilypond (Ubuntu):
status: New → Incomplete
Changed in lilypond (Ubuntu):
status: Incomplete → New
fxndx (fxndx)
Changed in lilypond (Ubuntu):
assignee: albezambu (albertozamburlini) → nobody
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 lilypond (Ubuntu):
status: New → 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.