Comment 17 for bug 205348

I reported my own encounter with this bug quite some time back now. In
fact, I'd forgotten about it till I rec'd your e-mail. Why Canonical
routed your query to me mystifies me as I'm simply another user. Sorry I
don't have a deep answer for you Sergio; I never rec'd an answer back
myself. On the other hand...

I surmised that, since the upgrade script didn't find the expected file in
the path quoted, my system was misconfigured to begin with, or the file was
damaged. The nasty work around in such a case is to blow away your Linux
installation and start fresh with the latest install image, which is what I
did. The better solution, if you have a good full backup that worked, try
a system restore and proceed from there. So few of us back up religiously,
that may not help.

Probably not the answer you looked for. Hope my answer helps though.

Gary Greene <email address hidden>
Gilroy, California

On Wed, Sep 5, 2018 at 10:55 AM sergio alberto rosales <email address hidden>
wrote:

> help!
> I am not an expert in Linux but I have to, ir order to work with GROMACS.
> Everything was OK until this bug appear and now I cannot doing anything
> Errors were encountered while processing:
> g77-3.4-doc
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Could you tell me, please, what can I do?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (190186).
> https://bugs.launchpad.net/bugs/205348
>
> Title:
> gcc-3.4-doc uphgrade failed due to missing
> usr/share/info/gcc-3.4.info.gz
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gcc-3.4/+bug/205348/+subscriptions
>