Control: reassign 852697 daptup
Control: retitle 852697 daptup: automatically starts gpg-agent in root user
slice
Control: affects 852697 + gnupg-agent
On Sun 2017-02-05 10:21:58 +0100, Laurent Bonnaud wrote:
> On 05/02/2017 10:08, Daniel Kahn Gillmor wrote:
>
>> Were you able to isolate what's
On Sun, 5 Feb 2017 11:21:58 +0100 Laurent Bonnaud
wrote:
> On 05/02/2017 10:08, Daniel Kahn Gillmor wrote:
>
> > Were you able to isolate what's launching the process?
>
> Yes I finally took the time to test all apt hooks and found the cause: it is
>
On 05/02/2017 10:08, Daniel Kahn Gillmor wrote:
> Were you able to isolate what's launching the process?
Yes I finally took the time to test all apt hooks and found the cause: it is
/etc/apt/apt.conf.d/11daptup from package daptup.
Should I reassign the bug?
> btw, that gpg-agent process is a
On Fri 2017-01-27 05:54:59 -0500, Laurent Bonnaud wrote:
> Here is what my system has in its apt config:
>
> /etc/apt/apt.conf.d:
> total 136
> -rw-r--r-- 1 root root 769 Nov 27 2015 01autoremove
> -r--r--r-- 1 root root 2677 Jan 24 15:42 01autoremove-kernels
> -rw-r--r-- 1 root root 628 May
On 27/01/2017 01:05, Daniel Kahn Gillmor wrote:
> Does the agent process appear as soon as you log in?
No, it appears when I run "apt update".
I had a similar problem with gvfs (see bug #852696) but in the case of
gpg-agent the logs give less information about which apt add-on is responsible:
Hi Laurent--
On Thu 2017-01-26 09:06:03 -0500, Laurent Bonnaud wrote:
> I usually remotely log in (via ssh) as root on a system where gnupg
> packages are installed and I noticed that a gpg-agent process is
> created for the root user:
>
> # systemd-cgls
> Control group /:
> -.slice
>
6 matches
Mail list logo