Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 724872 - gpg-agent instances left running after emerge --sync
Summary: gpg-agent instances left running after emerge --sync
Status: RESOLVED DUPLICATE of bug 718066
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-23 20:58 UTC by Erik Quaeghebeur
Modified: 2020-05-24 02:14 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Quaeghebeur 2020-05-23 20:58:37 UTC
I have a Gentoo VPS and I noticed (with htop) that I had multiple gpg-agent instances running. Namely, when I looked recently, I had 18 of them, all looking as follows:

gpg-agent --homedir /tmp/<some random string> --use-standard-socket --daemon

In a forum post (https://forums.gentoo.org/viewtopic.php?p=8461290#8461290), another user recalled having had the same issue, but for them it disappeared after a while. They linked it to emerge --sync calls.

So I tried looking at htop output while doing an emerge --sync and indeed, gpg-agent instances were started and left running. I also saw a dirmngr instance referring to the same <some random string>, but that disappeared.

Reproducible: Always

Steps to Reproduce:
1. run emerge --sync

Actual Results:  
gpg-agent instance started and left running

Expected Results:  
gpg-agent started and stopped once its use is over
Comment 1 Zac Medico gentoo-dev 2020-05-24 02:11:20 UTC

*** This bug has been marked as a duplicate of bug 718066 ***
Comment 2 Zac Medico gentoo-dev 2020-05-24 02:14:17 UTC
According to bug 718066, should be fixed with app-portage/gemato-14.4.