[Aptitude-devel] Bug#799532: aptitude: typing Ctrl-L during an upgrade puts aptitude in background

[Vincent Lefevre]

On 2015-09-20 12:04:48 +0100, Manuel A. Fernandez Montecelo wrote:
> 2015-09-20 2:08 GMT+01:00 Vincent Lefevre <vincent at vinc17.net>:
> > On 2015-09-20 02:50:45 +0200, Vincent Lefevre wrote:
> >> > >zira:~> pstree -ap 29204
> >> > >bash,29204
> >> > > └─aptitude,29206
> >> > >     ├─(dpkg,29277)
> >> > >     ├─dpkg,30424 --status-fd 76 --configure geoclue-2.0:amd64 ...
> >> > >     │   └─sh,30438 -c...
> >> > >     │       └─less,30440 -Lis
> >> > >     └─{aptitude},29491
> >>
> >> There was a zombie dpkg process that was a child of aptitude.
> >> Where did it come from?
> 
> There are dpkg processes launched to e.g. ascertain whether multi-arch
> is supported, and if it needs to use the arch when calling dpkg and
> apt.  It is also called directly to reconfigre packages, but I assume
> that you didn't issue that action.

No, I didn't. But why would it leave a zombie?

> Probably apt also calls the dpkg command in that way internally.  If
> dpkg is called from libapt-pkg, it will be shown from within the
> aptitude process, as in this case.
> 
> If we could see the arguments, mayge we would get better clues.  If
> you can reproduce it in the future, please try to list the args of the
> commands, if they are retrievable.

The -p option shows the arguments: you can see this for the other
processes. Unfortunately, as the dpkg was a zombie, the arguments
were no longer available.

> > And in the /var/log/aptitude log file:
> >
> > Aptitude 0.7.1: log report
> > Sun, Sep 20 2015 00:34:35 +0200
> >[...]
> > Aptitude 0.7.1: log report
> > Sun, Sep 20 2015 00:35:01 +0200
> >[...]
> >
> > I don't understand why this is duplicated.
> 
> It is not exactly duplicated, the dates are different.  (But it could
> be a bug of commiting the information twice to the logs, if you are
> sure that you only ran it once in that period of time).

Even if I had run aptitude twice (which is not possible due to locking,
and BTW, when it was put in background, running aptitude again gave me
a locking error), I couldn't have got the same logs.

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)