Comment 23 for bug 1983528

Hi Steve, and thanks for trying this!

I'm not sure that the deb package is needed; I suspect that the manual update you did occurred too late in the process, when part of the damage was already done. If my understanding is correct (also using the system logs that James posted in comment #19), what happens is:

1. System boots, with snapd 2.55 installed as a deb, and 2.56 installed as a snap. I guess that at this point the boot target is "multi-user", because:
2. "Aug 04 11:07:29 [...] Mounting Mount unit for snapd, revision 16292..." (the snapd snap gets mounted)
3. System reboots, the boot target is oem-config
4. All snap mount units are *not* loaded
5. The snapd startup is triggered
6. Since the mount unit for snapd was not loaded, the deb version of the snapd is run
7. snapd cannot read the yaml file for the installed snaps, and marks them as invalid
8. snapd disconnects all the snap connections

My understanding is that in your test you intervened after point 3. Your installation of the newer snapd and the reinstallation of all the snaps fixed the "WantedBy" line, but by that time the boot target was already set. Since the commands you entered obviously required a running snapd, it means that points 5 to 8 described above have also been executed before the snaps had been reinstalled.

It's not clear to me why the reinstalling of the snaps did not help to restore the connections (if you still have the logs, they could be helpful), but my main point is that, with a fixed snapd, point 4 above would not happen, therefore the snapd deb would not enter into the picture. But again, mine is just speculation, that's why having an image with the newest snapd built-in would be helpful.