Ubuntu
qt4-x11 package

package libqt4-webkit 4:4.7.2-0ubuntu6.1 failed to install/upgrade: error al escribir en `<salida estándar>': No existe el fichero o el directorio

Bug #788302 reported by Guillermo RP on 2011-05-25

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

Bug Description

i was installing spotify linux version and the computer died and now claims it is not an original ubuntu copy i was able to fix it by undoing all the steps i did nd uninstalling the stuff on my own so just don't try it stick to grooveshark cheers

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libqt4-webkit 4:4.7.2-0ubuntu6.1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed May 25 15:41:29 2011
ErrorMessage: error al escribir en `<salida estándar>': No existe el fichero o el directorio
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: qt4-x11
Title: package libqt4-webkit 4:4.7.2-0ubuntu6.1 failed to install/upgrade: error al escribir en `<salida estándar>': No existe el fichero o el directorio
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Guillermo RP (guille-arp) wrote on 2011-05-25:

AptOrdering.txt Edit (181 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
Df.txt Edit (443 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (54.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (802 bytes, 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.