| 2018-05-29 14:21:16 |
Dimitri John Ledkov |
bug |
|
|
added bug |
| 2018-05-29 16:00:18 |
Julian Andres Klode |
apt (Ubuntu): status |
New |
In Progress |
|
| 2018-05-29 16:00:22 |
Julian Andres Klode |
apt (Ubuntu): importance |
Undecided |
Medium |
|
| 2018-05-29 16:00:26 |
Julian Andres Klode |
apt (Ubuntu): assignee |
|
Julian Andres Klode (juliank) |
|
| 2018-06-19 15:18:13 |
Julian Andres Klode |
apt (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2018-06-20 20:06:07 |
Launchpad Janitor |
apt (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2018-06-25 12:16:55 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-06-25 12:16:55 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Bionic) |
|
| 2018-06-25 12:17:01 |
Julian Andres Klode |
apt (Ubuntu Bionic): status |
New |
In Progress |
|
| 2018-06-25 12:17:04 |
Julian Andres Klode |
apt (Ubuntu Bionic): status |
In Progress |
Triaged |
|
| 2018-06-26 07:38:29 |
Julian Andres Klode |
description |
apt-key adv should gpgconf --kill all the things after execution
to ensure that e.g. dirmngr processes are not left hanging around |
[Impact]
dirmngr processes are left hanging around
[Test case]
apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092" < /dev/null ; ps aux
should not show a dirmngr process after exit (except for any that was there before running it, obviously)
[Regression potential]
This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows?
[Original bug report]
apt-key adv should gpgconf --kill all the things after execution
to ensure that e.g. dirmngr processes are not left hanging around |
|
| 2018-06-26 07:38:41 |
Julian Andres Klode |
description |
[Impact]
dirmngr processes are left hanging around
[Test case]
apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092" < /dev/null ; ps aux
should not show a dirmngr process after exit (except for any that was there before running it, obviously)
[Regression potential]
This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows?
[Original bug report]
apt-key adv should gpgconf --kill all the things after execution
to ensure that e.g. dirmngr processes are not left hanging around |
[Impact]
dirmngr processes are left hanging around after doing key server stuff with apt-key adv.
[Test case]
apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092" < /dev/null ; ps aux
should not show a dirmngr process after exit (except for any that was there before running it, obviously)
[Regression potential]
This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows?
[Original bug report]
apt-key adv should gpgconf --kill all the things after execution
to ensure that e.g. dirmngr processes are not left hanging around |
|
| 2018-06-26 07:42:55 |
Julian Andres Klode |
description |
[Impact]
dirmngr processes are left hanging around after doing key server stuff with apt-key adv.
[Test case]
apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092" < /dev/null ; ps aux
should not show a dirmngr process after exit (except for any that was there before running it, obviously)
[Regression potential]
This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows?
[Original bug report]
apt-key adv should gpgconf --kill all the things after execution
to ensure that e.g. dirmngr processes are not left hanging around |
[Impact]
dirmngr processes are left hanging around after doing key server stuff with apt-key adv.
[Test case]
apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092" < /dev/null ; sleep 2; ps aux
should not show a dirmngr process (except for any that was there before running it, obviously).
[Regression potential]
This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows?
[Original bug report]
apt-key adv should gpgconf --kill all the things after execution
to ensure that e.g. dirmngr processes are not left hanging around |
|
| 2018-06-26 07:43:39 |
Julian Andres Klode |
apt (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2018-06-27 15:44:46 |
Chris J Arges |
apt (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-06-27 15:44:47 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-06-27 15:44:48 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2018-06-27 15:44:51 |
Chris J Arges |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-06-28 09:41:03 |
Julian Andres Klode |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2018-07-05 07:35:00 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-07-05 07:44:59 |
Launchpad Janitor |
apt (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
