package gcc-4.4-base 4.4.1-4ubuntu6 failed to install/upgrade: error writing to '<standard output>': No such file or directory

Bug #442193 reported by Claus7
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

Binary package hint: gcc-4.4

Description: Ubuntu karmic (development branch)
Release: 9.10

gcc-4.4-base:
  Installed: 4.4.1-4ubuntu6
  Candidate: 4.4.1-4ubuntu6
  Version table:
 *** 4.4.1-4ubuntu6 0
        500 http://gr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

I was expecting this package to update normally.
Instead it crushed.

ProblemType: Package
Architecture: i386
Date: Sun Oct 4 15:41:40 2009
Dependencies:

DistroRelease: Ubuntu 9.10
ErrorMessage: error writing to '<standard output>': No such file or directory
NonfreeKernelModules: nvidia
Package: gcc-4.4-base 4.4.1-4ubuntu6
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: gcc-4.4
Title: package gcc-4.4-base 4.4.1-4ubuntu6 failed to install/upgrade: error writing to '<standard output>': No such file or directory
Uname: Linux 2.6.31-11-generic i686

Revision history for this message
Claus7 (lastexile7gr) wrote :
Revision history for this message
Claus7 (lastexile7gr) wrote :

What I did to avoid this, was to go to synaptic and from the down left corner I chose the option Status and then broken packages. I updated them and and I anew started the updated process from the icon in the toolbar.

The next step was to have a new bug for python this time. I closed the update process and I opened once again synaptic and updated my whole system from there. The update went ok and smooth. The icon in the toolbar did not disappear, yet after all this, when I clicked on it, it said that there were no more updates for my system. So, I think that that way someone can bypass this issue.

In synaptic I have installed both gcc-4.4-base and gcc-4.3-base.

I have karmic since alpha 5 or 6 and I do all the updates in the meantime.

Revision history for this message
Matthias Klose (doko) wrote :

not a gcc error

affects: gcc-4.4 (Ubuntu) → ubuntu
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.