On 2024-04-29 03:05:50 +0200, Guillem Jover wrote: > I don't think dpkg is at fault here, I assume something else is either > getting activated in the middle of the transaction while the package > manager frontend driving dpkg has released the lock (which it should > not), or the package manager frontend driving dpkg is performing the > locking dance incorrectly.
Isn't dpkg able to install/uninstall a set of packages in an atomic way (where dpkg itself would set a lock at the beginning and release the lock once every install/uninstall has been done, so that a lock failure would not be possible in the middle of the installation)? > > > with fdisk. > > > > I see no evidence of that in the log. > > Right, it seems to me, like when dpkg fails due to the already held > lock, then the frontend is not recomputing the transaction and keeps > as if nothing had gone incorrectly, until it then notices later on. Alternatively, if this is too complicated, it could abort and let the user fix things (which is currently needed anyway). > In any case, given that dpkg is not being very helpful in diagnosing > this, I'll implement support to print the process name in addition to > the pid, as this has also hit me, and it's never clear what was the > actual culprit. So that's why I'm leaving this assigned to dpkg, but > with a lower severity. If you'd like to file this elsewhere, then > please clone and reassign that. It seems that the "dpkg frontend lock is locked by another process" error almost always occurs with the same packages: either util-linux or apt. See bugs * 933335 Unpacking util-linux (2.34-0.1) over (2.33.1-0.1) ... dpkg: error: dpkg frontend lock is locked by another process Setting up apt (2.6.1) ... dpkg: error: dpkg frontend lock was locked by another process with pid 4191235 * 940961 Unpacking apt (1.8.4) over (1.8.3) ... dpkg: error: dpkg frontend lock is locked by another process * 1069183 Setting up util-linux-extra (2.38.1-5+deb12u1) ... dpkg: error: dpkg frontend lock was locked by another process with pid 1064194 * 1070027 (this bug) Setting up util-linux (2.40-8) ... fstrim.service is a disabled or a static unit not running, not starting it. dpkg: error: dpkg frontend lock was locked by another process with pid 58569 I'm wondering whether there could be a reason... But there's also bug 1062190: Unpacking locales (2.36-9+deb12u4) over (2.36-9+deb12u3) ... dpkg: error: dpkg frontend lock was locked by another process with pid 567573 -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
