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

Sun Sep 20 11:04:48 UTC 2015

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.

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.

> 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).

> In the /var/log/dpkg.log log file:
>
> [...]
> 2015-09-20 00:35:22 status unpacked geoclue-2.0:amd64 2.3.0-1
> 2015-09-20 00:35:22 status unpacked geoclue-2.0:amd64 2.3.0-1
> 2015-09-20 00:35:22 status unpacked geoclue-2.0:amd64 2.3.0-1
> 2015-09-20 00:35:22 status half-configured geoclue-2.0:amd64 2.3.0-1
> 2015-09-20 00:35:22 status installed geoclue-2.0:amd64 2.3.0-1
> 2015-09-20 00:35:22 configure libklibc:amd64 2.0.4-4 <none>
> 2015-09-20 00:35:22 status unpacked libklibc:amd64 2.0.4-4
> 2015-09-20 00:35:22 status half-configured libklibc:amd64 2.0.4-4
> 2015-09-20 00:35:22 status installed libklibc:amd64 2.0.4-4
> 2015-09-20 00:35:22 configure klibc-utils:amd64 2.0.4-4 <none>
> 2015-09-20 00:35:22 status unpacked klibc-utils:amd64 2.0.4-4
> 2015-09-20 00:35:22 status half-configured klibc-utils:amd64 2.0.4-4
> 2015-09-20 00:35:22 status installed klibc-utils:amd64 2.0.4-4
> 2015-09-20 00:35:22 configure liblightdm-gobject-1-0:amd64 1.16.2-1 <none>
> 2015-09-20 00:35:22 status unpacked liblightdm-gobject-1-0:amd64 1.16.2-1
> 2015-09-20 00:35:22 status half-configured liblightdm-gobject-1-0:amd64 1.16.2-1
> 2015-09-20 00:35:22 status installed liblightdm-gobject-1-0:amd64 1.16.2-1
> 2015-09-20 00:35:22 status triggers-pending libc-bin:amd64 2.19-20
> 2015-09-20 00:35:22 configure liblightdm-gobject-dev:amd64 1.16.2-1 <none>
> 2015-09-20 00:35:22 status unpacked liblightdm-gobject-dev:amd64 1.16.2-1
> 2015-09-20 00:35:23 status half-configured liblightdm-gobject-dev:amd64 1.16.2-1
> 2015-09-20 00:35:23 status installed liblightdm-gobject-dev:amd64 1.16.2-1
> 2015-09-20 00:35:23 configure lightdm:amd64 1.16.2-1 <none>
> 2015-09-20 00:35:23 status unpacked lightdm:amd64 1.16.2-1
> 2015-09-20 00:35:23 status unpacked lightdm:amd64 1.16.2-1
> 2015-09-20 00:35:23 status unpacked lightdm:amd64 1.16.2-1
> 2015-09-20 00:35:23 status unpacked lightdm:amd64 1.16.2-1
> 2015-09-20 00:35:23 status unpacked lightdm:amd64 1.16.2-1
> 2015-09-20 00:35:23 status unpacked lightdm:amd64 1.16.2-1
> [The problem occurred here.]
> 2015-09-20 00:46:41 startup packages configure
> [...]

It is repeated many times, but even then if you see the first lines
where I cropped, it also happens with geoclue before in the log file.
(And there is a dpkg process handling geoclue in the dpkg above).

> I don't understand either why I get several times the same line
> in the dpkg log, but this has always occurred (I can see that
> also on another machine, with logs back to 2014-09).

I have repeated lines in my log as well from one year ago, so as you
say, I don't think that this problem is related:

====
2014-10-13 18:11:32 configure dkms:all 2.2.0.3-2 <none>
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status unpacked dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status half-configured dkms:all 2.2.0.3-2
2014-10-13 18:11:32 status installed dkms:all 2.2.0.3-2
====

Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>