Ubuntu
glib-networking package

package glib-networking 2.28.6.1-0ubuntu1 failed to install/upgrade: error writing to '<standard output>': No such file or directory

Bug #788987 reported by Tom Clabon on 2011-05-27

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
	glib-networking (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: glib-networking

Apport detected the system issue and filled this form out for me. I'm not sure what the package does but I still have a network connection and can still configure it via the GUI

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: glib-networking 2.28.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Fri May 27 08:22:38 2011
ErrorMessage: error writing to '<standard output>': No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: glib-networking
Title: package glib-networking 2.28.6.1-0ubuntu1 failed to install/upgrade: error writing to '<standard output>': No such file or directory
UpgradeStatus: Upgraded to natty on 2011-05-02 (24 days ago)

Tags:

Revision history for this message

Tom Clabon (tom-clabon) wrote on 2011-05-27:

AptOrdering.txt Edit (125 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (748 bytes, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (77.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (488 bytes, 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