[Bug 1831981] Re: aptdaemon frontend locking, locking fixes

[Julian Andres Klode]

disco - 1.1.1+bzr982-0ubuntu21.1 - was fine too

Skipping cosmic, as releasing this 9 days before EOL is pointless if not
potentially harmful.

** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco

** Tags removed: verification-needed-cosmic
** Tags added: verification-failed-cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to aptdaemon in Ubuntu.
https://bugs.launchpad.net/bugs/1831981

Title:
  aptdaemon frontend locking, locking fixes

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in aptdaemon source package in Xenial:
  Fix Committed
Status in aptdaemon source package in Bionic:
  Fix Committed
Status in aptdaemon source package in Cosmic:
  Fix Committed
Status in aptdaemon source package in Disco:
  Fix Committed
Status in aptdaemon source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  aptdaemon needs to implement frontend locking to avoid it hijacking dpkg status lock from clients that do implement frontend locking; and in order to be protected from apt clients that acquire the status lock (which they won't do if aptdaemon holds the frontend lock).

  This also change the locking order to lock in APT order, and the
  unlock order becomes the reverse of that so that the behavior is sane
  wrt other clients, as it was somewhat broken.

  [Test case]
  Lock /var/lib/dpkg/lock-frontend and then try do so something with aptdaemon, it should not be possible until you release lock-frontend.

  [Regression potential]
  There may be other race conditions appearing now due to the order of (un)locking changing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1831981/+subscriptions