Seems I had a similar problem. This is how the snapd related output of `ps fax` looked like: ``` 2766197 ? Ssl 0:02 /usr/lib/snapd/snap-failure snapd 2766264 ? Sl 4:27 \_ /snap/snapd/21465/usr/lib/snapd/snapd 1817555 ? Ss 0:00 /bin/sh /usr/lib/apt/apt.systemd.daily install 1817559 ? S 0:00 \_ /bin/sh /usr/lib/apt/apt.systemd.daily lock_is_held install 1817594 ? S 2:11 \_ /usr/bin/python3 /usr/bin/unattended-upgrade 1822087 ? S 1:24 \_ /usr/bin/python3 /usr/bin/unattended-upgrade 1822170 pts/0 Ss+ 0:00 \_ /usr/bin/dpkg --status-fd 11 --configure --pending 1822171 pts/0 S+ 0:00 \_ /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.63.1+24.04 1822348 pts/0 S+ 0:00 \_ /usr/bin/perl /usr/bin/deb-systemd-invoke restart snapd.service 1822352 pts/0 S+ 0:00 \_ systemctl --quiet --system restart snapd.service 2775926 ? Ssl 0:00 /usr/lib/snapd/snapd ``` And the PID of the last process would change once in a while. So I guessed that systemctl restart wants to start `/usr/lib/snapd/snapd` without first stopping the old process `/snap/snapd/21465/usr/lib/snapd/snapd` and the new process cannot acquire the lock and keeps restarting. So I did `kill 2766264` which killed the old snapd process `/snap/snapd/21465/usr/lib/snapd/snapd`, and that finally allowed snapd to start and unattended-upgrade to finish and everything started working again.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065576 Title: Snap inoperable on upgrade: Failed to lock state file/restart snapd.mounts-pre.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2065576/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
