Ubuntu
libproc-waitstat-perl package

package libproc-waitstat-perl 1.00-4 failed to install/upgrade: error writing to '<standard output>': No such file or directory

Bug #595031 reported by Richard Trenchard on 2010-06-16

This bug report is a duplicate of: Bug #545790: package PACKAGE failed to install/upgrade: error writing to '<standard output>': Success. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	libproc-waitstat-perl (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: libproc-waitstat-perl

I just notice this process had crashed
I used the reporting tool to report this bug

Version 10.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libproc-waitstat-perl 1.00-4
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Jun 15 12:47:45 2010
ErrorMessage: error writing to '<standard output>': No such file or directory
PackageArchitecture: all
SourcePackage: libproc-waitstat-perl
Title: package libproc-waitstat-perl 1.00-4 failed to install/upgrade: error writing to '<standard output>': No such file or directory

Tags:

Revision history for this message

Richard Trenchard (richard-trenchard) wrote on 2010-06-16:

AptOrdering.txt Edit (359 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (662 bytes, text/plain; charset="utf-8")
Df.txt Edit (581 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (66.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (45.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-07-11:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #545790, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad