[Bug 2114923] Re: Upon booting iso, no snaps are installed and desktop installer service crashes
Ernest Lotter
2114923 at bugs.launchpad.net
Wed Sep 3 09:41:00 UTC 2025
Verification:
-------------
Refer to https://bugs.launchpad.net/ubuntu-desktop-
provision/+bug/2114923/comments/25
** Description changed:
[SRU] 2.71: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2118396
+
+ This issue was originally reported to be a snapd issue, however there is
+ no definitive fix on the snapd side to guarantee that another user
+ service that depends on seeding to be complete, does not start too
+ early. For this reason the recommendation was made to change the boot
+ sequence for the other service, and this is the definitive fix that was
+ made to livecd-rootfs (Ubuntu).
+
+ On the snapd side, some work was done to improve seeding speed, but this
+ is not in any way a definitive fix, it just decrease the likelihood of
+ encountering the problem on a slow system.
+ https://github.com/canonical/snapd/pull/15682
[ Impact ]
...
[ Test Plan ]
...
---original---
Upon booting an ISO (I believe this may only happen with slow internet
connections) there is (sometimes) NO snaps installed. Snapd is
functional but snap info list lists no snaps. The desktop installer
services crashes, and thus the installer never boots up. After *quite*
some time (approx 5m) on this live iso, snaps were installed, and the
installer icon then functional. I've attached the journalctl to help
debugging.
** Description changed:
[SRU] 2.71: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2118396
This issue was originally reported to be a snapd issue, however there is
no definitive fix on the snapd side to guarantee that another user
service that depends on seeding to be complete, does not start too
early. For this reason the recommendation was made to change the boot
sequence for the other service, and this is the definitive fix that was
made to livecd-rootfs (Ubuntu).
On the snapd side, some work was done to improve seeding speed, but this
is not in any way a definitive fix, it just decrease the likelihood of
encountering the problem on a slow system.
https://github.com/canonical/snapd/pull/15682
[ Impact ]
- ...
+ When another service starts up and depends on snapd seeding to be done,
+ without enforcing a boot order that ensures seeding is complete (e.g.
+ `After=snapd.seeded.service`), snaps will be missing and this will lead
+ to failuires. This is the case for the installer ubuntu-desktop-
+ installer.service.
[ Test Plan ]
- ...
+ Confirm that the definitive fix made for livecd-rootfs (Ubuntu) solves
+ the problem.
---original---
Upon booting an ISO (I believe this may only happen with slow internet
connections) there is (sometimes) NO snaps installed. Snapd is
functional but snap info list lists no snaps. The desktop installer
services crashes, and thus the installer never boots up. After *quite*
some time (approx 5m) on this live iso, snaps were installed, and the
installer icon then functional. I've attached the journalctl to help
debugging.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2114923
Title:
Upon booting iso, no snaps are installed and desktop installer service
crashes
Status in snapd:
Fix Committed
Status in ubuntu-desktop-provision:
Invalid
Status in livecd-rootfs package in Ubuntu:
Fix Released
Bug description:
[SRU] 2.71:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2118396
This issue was originally reported to be a snapd issue, however there
is no definitive fix on the snapd side to guarantee that another user
service that depends on seeding to be complete, does not start too
early. For this reason the recommendation was made to change the boot
sequence for the other service, and this is the definitive fix that
was made to livecd-rootfs (Ubuntu).
On the snapd side, some work was done to improve seeding speed, but
this is not in any way a definitive fix, it just decrease the
likelihood of encountering the problem on a slow system.
https://github.com/canonical/snapd/pull/15682
[ Impact ]
When another service starts up and depends on snapd seeding to be
done, without enforcing a boot order that ensures seeding is complete
(e.g. `After=snapd.seeded.service`), snaps will be missing and this
will lead to failuires. This is the case for the installer ubuntu-
desktop-installer.service.
[ Test Plan ]
Confirm that the definitive fix made for livecd-rootfs (Ubuntu) solves
the problem.
---original---
Upon booting an ISO (I believe this may only happen with slow internet
connections) there is (sometimes) NO snaps installed. Snapd is
functional but snap info list lists no snaps. The desktop installer
services crashes, and thus the installer never boots up. After *quite*
some time (approx 5m) on this live iso, snaps were installed, and the
installer icon then functional. I've attached the journalctl to help
debugging.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2114923/+subscriptions
More information about the foundations-bugs
mailing list