Ubuntu
libgcrypt11 package

package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: error writing to '<standard output>': Success

Bug #1014254 reported by Daniel O'Connor on 2012-06-17

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

Bug Description

Occurs when starting system - specifically logging into gnome.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libgcrypt11 1.5.0-3ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic i686
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
Date: Sat Jun 9 22:36:53 2012
ErrorMessage: error writing to '<standard output>': Success
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: libgcrypt11
Title: package libgcrypt11 1.5.0-3ubuntu0.1 failed to install/upgrade: error writing to '<standard output>': Success
UpgradeStatus: Upgraded to precise on 2012-04-11 (66 days ago)

Tags:

Revision history for this message

Daniel O'Connor (daniel-oconnor) wrote on 2012-06-17:

AptOrdering.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (476 bytes, text/plain; charset="utf-8")
Df.txt Edit (408 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (60.8 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (6.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (19.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-06-17:

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.