package dasher (not installed) failed to install/upgrade: failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/bin/dasher'

Bug #628251 reported by Tom Cantara

This bug report was converted into a question: question #130658: package dasher (not installed) failed to install/upgrade: failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/bin/dasher'.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dasher (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: dasher

Error came up after reinstall of gnome-desktop, due to loss of the gnome-power manager after using scalpel to recover deleted files. This coincided with a previous bug I've reported after the same problem. Using Ubuntu 10.04 LTS.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: dasher (not installed)
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Wed Sep 1 13:41:52 2010
ErrorMessage: failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/bin/dasher'
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: dasher
Title: package dasher (not installed) failed to install/upgrade: failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/bin/dasher'

Revision history for this message
Tom Cantara (tacantara) wrote :
Revision history for this message
Alan Bell (alanbell) wrote :

sorry, I don't think this is a Dasher bug, it sounds like the dpkg database is in a bit of a mess

Revision history for this message
Alan Bell (alanbell) wrote :

this doesn't appear to be a bug in the package as such, but a scenario with a known cause that has happened on your system so converting it to a question and will see if I can find someone to suggest next steps if this is still an issue for you.

Changed in dasher (Ubuntu):
status: New → Invalid
Revision history for this message
Tom Cantara (tacantara) wrote :

I was able to restore my system, through some luck and noodling with a terminal session. I haven't run the Scalpel program, which eventually led to the reported problem, since the problem surfaced.

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.