© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I'll try to get myself to dig through the logs.
some more background:
Of course this whole saga starts with a botched upgrade
I tried upgrading a focal system to jammy. The upgrade failed with a 'some files failed to download, aborting upgrade' (paraphrasing). But it failed *after* it already had downloaded and *unpacked/
So this left my system in a limbo state where it would not fully boot. It would get as far as mounting root, and then it would stop on a timeout mounting my home folder.
I dug into that and found out that the systemd unit for the block device failed, because it would try to open a socket connection to init and then after some back & forth never get a reply. (god, this whole system feels so overengineered. I'm sure it's useful for something, but why not just check if the block device is there and mount it already).
I decided it was probably a case of a half installed new system, with different parts of the systemd machinery being from different versions and misunderstanding eachother. I this the default trick for botched upgrades: start from an ubuntu 22.04 usb stick, mount the hdds, bind-mount /proc etc, chroot into the hdd and run apt dist-upgrade.
This worked and got my system back up to a running state, but it of course did not do the rest of the jammy update executable, so maybe there's the origin of hostfs being visible?
Everything seemed to run well, *except* that any exectuable from a snap refused to run because 'snap-confine' was running unrestricted (apparmore error msg. paraphrasing, I could get the exact message but it doesn't really matter for this story).
'apt reinstall snapd' didn't work. Neither did reinstalling apparmor or apparmor profiles.
I then decided to dpkg -r snapd (with the plan of then manually wiping any remains) and reinstall it. This trick has often saved me in the past and it seemed feasible, as the only thing depending on snapd (according to dpkg) was firefox. With the disastrous results following.