I don't think this test case is well formed, it doesn't describe how to
install the packages with the named backends and it doesn't mention
needing to kill the frontend or when to kill it.
** Changed in: packagekit (Ubuntu Disco)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1726068
Title:
debconf socket closes if aptdaemon/PK client exits
Status in apper package in Ubuntu:
New
Status in aptdaemon package in Ubuntu:
Fix Released
Status in packagekit package in Ubuntu:
Fix Released
Status in software-properties package in Ubuntu:
Invalid
Status in apper source package in Bionic:
New
Status in aptdaemon source package in Bionic:
New
Status in packagekit source package in Bionic:
New
Status in apper source package in Disco:
New
Status in aptdaemon source package in Disco:
New
Status in packagekit source package in Disco:
Incomplete
Bug description:
[Impact]
Closing an application using PackageKit or aptdaemon to install packages
kills the debconf endpoint (because it's a subprocess that's cleaned up),
causing debconf to use defaults which might lead to wrong results, or even
cause installations to fail.
[Solution]
The solution is to move the end point into a socket-activated systemd unit,
so that it is independent of the graphical frontend that started the
transaction. The other advantage is that this offers us restart if the end
point crashes.
[Test case]
1. Install opera deb using packagekit, ensure service is activated
2. Install opera deb using aptdaemon, ensure service is activated
Alternatively, you might use another deb that has debconf prompts.
[Regression potential]
Systems that do not yet use systemd will fall back to the old method, so
should not regress.
Otherwise, if there are bugs, they'd affect the ability to show
debconf prompts, and behavior would revert to using the defaults.
There might be some uncertainty if you restart your desktop while the
helper is running and it does not pick up the new X/Wayland display
until it restarts (it should fail to connect and restart). Given that
the helper times out, this should not be an issue in practice, as
you'd have to logout, login, and start a new install within 60
seconds.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apper/+bug/1726068/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
