It's way too late for that behavior right now. Many features expect snapd to be live to work. Seeding happens the first time snapd runs, which means a new system will by default start without any snaps installed. The data for command-not-found is acquired by snapd while running as well. We also cannot trivially start and then stop because there's no obvious control point for when snapd is done doing what needs to get done.
So, yeah, we can look for good solutions for this problem, but changing the behavior now would be reckless in terms of stability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730159 Title: Snapd should not start if there are no Snaps installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1730159/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
