[Bug 1726068] Re: debconf socket closes if aptdaemon/PK client exits
Julian Andres Klode
julian.klode at canonical.com
Wed Dec 18 11:01:19 UTC 2019
I'm still happy with the test case. It shows that the debconf socket is
independent of whatever frontend is running, and hence closing the
frontend can't close the debconf socket. Which means you can just use
pkcon / aptdcon to test that bit.
I don't really know of any PackageKit frontend that's heavily affected
by this. gnome-software is running as a background service, so I guess
you could install via it and then kill it and check that the prompts
still work. And the KDE stuff is still broken, as they use their own
mess.
For aptdaemon, you could probably write a small script.
** No longer affects: packagekit (Ubuntu Disco)
** No longer affects: aptdaemon (Ubuntu Disco)
** No longer affects: apper (Ubuntu Disco)
--
You received this bug notification because you are a member of
PackageKit-Team, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1726068
Title:
debconf socket closes if aptdaemon/PK client exits
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apper/+bug/1726068/+subscriptions
More information about the Ubuntu-reviews
mailing list