Ubuntu
gtk+2.0 package

package libgail18 2.24.6-0ubuntu5 failed to install/upgrade: errore nello scrivere su "<standard output>": Successo

Bug #869081 reported by CristianCantoro on 2011-10-06

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
	gtk+2.0 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Just upgraded to Ubuntu 11.10 Beta2. Using gtk-recordmydesktop v. 0.3.8-3ubuntu5
$ uname -a
Linux 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:23:39 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: libgail18 2.24.6-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Oct 6 10:09:12 2011
ErrorMessage: errore nello scrivere su "<standard output>": Successo
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: gtk+2.0
Title: package libgail18 2.24.6-0ubuntu5 failed to install/upgrade: errore nello scrivere su "<standard output>": Successo
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (1 days ago)

Tags:

Revision history for this message

CristianCantoro (cristiancantoro) wrote on 2011-10-06:

AptOrdering.txt Edit (791 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Df.txt Edit (440 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (75.2 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (21.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-01-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. Please continue to report any other bugs you may find.