Comment 3 for bug 133791

Hi,

I've gone from having this problem every day to not having it at all.
Significantly I've reformatted my drive and installed Tribe 4 + recent
updates. Unfortunately it's difficult to know what fixed the problem.

Chris

LGB [Gábor Lénárt] wrote:
> *** This bug is a duplicate of bug 134858 ***
> https://bugs.launchpad.net/bugs/134858
>
> It seems bug #134858 marked as fix released (and also originally it's
> about update-manager and not apt-get), though I still have got this bug,
> so I've decided to include my comment here as well (with some
> modifications):
>
> I've also got this bug, it's ubuntu gutsy on AMD64 (but I've seen this
> on an i386 box too at my workplace, with the same version numbers),
> version of apt package is 0.7.6ubuntu12, version of dpkg is
> 1.14.5ubuntu16. From time to time using "apt-get" causes to "freeze", I
> can see process "dpkg" in defunct state with command ps. It seems it's
> just after unpacking packages, since killing apt-get than running "dpkg
> --configure -a" does the trick (eg furthet "apt-get dist-upgrade" does
> not find any more task to do).
>
> Also (don't it's related or not) I've discovered that I can't stop apt-
> get (when unpacking packages) with CTRL-Z even before the freeze however
> I've used this to stop installing packages for a while if I need more
> disk I/O bandwidth for an urgent task or such (I've got very slow disk
> ....) which can be continued with command 'fg' from the shell where I
> had ran apt-get from.
>
> As I've written in my latter comment of mine, even CTRL-C does not work.
> I've met with this problem from issuing apt-get from gnome-terminal and
> text console as well (without starting X) if it counts ...
>
>