package coreutils 8.5-1ubuntu3 failed to install/upgrade: Fehler beim Schreiben von »<Standardausgabe>«: No such file or directory

[sk]

Binary package hint: coreutils

I'm upgrading from lucid [was erroneous: lenny] to maverik on an eee pc.
During the upgrade the gdm was restarted. (After downloading and during package installation.)

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: coreutils 8.5-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Fri Jan 21 13:25:40 2011
ErrorMessage: Fehler beim Schreiben von »<Standardausgabe>«: No such file or directory
SourcePackage: coreutils
Title: package coreutils 8.5-1ubuntu3 failed to install/upgrade: Fehler beim Schreiben von »<Standardausgabe>«: No such file or directory

[C de-Avillez (hggdh2)]

Thank you for opening this bug and helping make Ubuntu better. I am not quite sure how you can upgrade from Lenny to Maverick, but let' s leave that aside.

Your error: "Fehler beim Schreiben von »<Standardausgabe>«: No such file or directory" makes it sound like the coreutils replacement package was not found on your local disc. Also, the only references to 'coreutils' I can find your your 'DpkgTerminalLog.txt' are:

Vorbereiten zum Ersetzen von coreutils 7.4-2ubuntu3 (durch .../coreutils_8.5-1ubuntu3_i386.deb) ...
Entpacke Ersatz für coreutils ...

Nothing Else.

Can you please re-run 'sudo apt-get update', and then retry installing coreutils?

[sk (s-karrmann)]

It was an upgrade from 10.04 LTS (Lucid Lynx) to 10.10 (Maverick Meerkat). Sorry for the wrong l...

The update crashed. Here is what happened afaik:
- gdm/window-manager or session crashed.
- restart or new gdm session on F8 possible without window-manager(!)
- The update python script takes 99-100% of CPU time. It doesn't spawn children (no dpkg etc.) After 12 hours I reboot.
- X starts but does not show the login dialog. :-(
- reboot to restricted: stops after 2 seconds without prompt or consoles. :-(
- reboot from USB (jaunty with luks and xts by hand!) chroot to system.
- apt-get install -f; dpkg --configure -a; aptitude
- boot 2.6.35-24-generic: gdm shows login; looks much better

Still to solve:
- default user still without automatic start of mutter
- new test user has automatically mutter
- I suspect gconf data. But which?
Any hints?

[C de-Avillez (hggdh2)]

Hi sk,

I am completely lost here. We were talking about a coreutils install failure that points to the DEB not being found on the local system, *not* about a system upgrade failure. I am sorry, but this bug is about coreutils...

[sk (s-karrmann)]

Well, I think you are right. It was only that the installation process reported this error. I was not sure if it was cause or consequence. Can we assign it to the update procedure? How can we do it?

[C de-Avillez (hggdh2)]

Yes, it can be done -- click on the down-arrow to the left of the coreutils line under the "Affects", and change the package to what you need, then reset the status to New.

[sk (s-karrmann)]

The real error is probably in the upgrade from lucid to maverik.

[Martin-Éric Racine (q-funk)]

Exactly which tool did you use to perform the upgrade?

[sk (s-karrmann)]

Hi,

I used the ,Aktualisierungsverwaltung' (german). I offers the update to
maverik and I proceed.

NB: I use a luks partition (in xts mode) which is separated in swap
an /.

Am Dienstag, den 08.02.2011, 18:10 +0000 schrieb Martin-Éric Racine:

> Exactly which tool did you use to perform the upgrade?
>

--
Kind Regards,
sk

[Robert Roth (evfool)]

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.