Ubuntu
libice package

package libice-dev 2:1.0.7-1ubuntu1 failed to install/upgrade: error writing to '<standard output>': No such file or directory

Bug #804491 reported by derrick4tech on 2011-07-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
	libice (Ubuntu)	New	Undecided	Unassigned

Bug Description

After installing latest updates for Natty Narhewal, without restarting I tried installing eclipse via CLI, I had to pause the installation during the download with 'kill-STOP' to make a few skype calls, after Unpacking, it got stuck at "Processing triggers for python.." since there was no progress after, a hour i killed the terminal & restarted my system

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libice-dev 2:1.0.7-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Jul 2 00:43:18 2011
ErrorMessage: error writing to '<standard output>': No such file or directory
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: libice
Title: package libice-dev 2:1.0.7-1ubuntu1 failed to install/upgrade: error writing to '<standard output>': No such file or directory
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

derrick4tech (derrick4tech) wrote on 2011-07-01:

AptOrdering.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (732 bytes, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (247.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (9.0 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