Ubuntu
libplrpc-perl package

package libplrpc-perl 0.2020-2 failed to install/upgrade: Fehler beim Schreiben von »<Standardausgabe>«: Datei oder Verzeichnis nicht gefunden

Bug #775056 reported by Philipp Strube on 2011-05-01

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
	libplrpc-perl (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: libplrpc-perl

I wanted to install mysql-server and this was pulled in as a dependency. Suddenly my my screen went black and I ended up in gdm again and had to login.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libplrpc-perl 0.2020-2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sun May 1 20:26:22 2011
ErrorMessage: Fehler beim Schreiben von »<Standardausgabe>«: Datei oder Verzeichnis nicht gefunden
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
SourcePackage: libplrpc-perl
Title: package libplrpc-perl 0.2020-2 failed to install/upgrade: Fehler beim Schreiben von »<Standardausgabe>«: Datei oder Verzeichnis nicht gefunden
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Philipp Strube (pst418) wrote on 2011-05-01:

AptOrdering.txt Edit (551 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (688 bytes, text/plain; charset="utf-8")
Df.txt Edit (519 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (63.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-01-12:

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. Please continue to report any other bugs you may find.