Ah, yes. When looking for a solution I ran onto some ubuntu answers page which claimed that snap stop --disable is the same as snap stop + snap disable.
And the snap manpage I've read is not explicit about the fact that there's two different sorts of 'disabled', that disabling the snap and disabling daemons are different things. The manpage explanation for snap disable and snap stop --disable are slightly different, but "Disable a snap in the system. The disable command disables a snap. The binaries and services of the snap will no longer be available..." and "As well as stopping the service now, arrange for it to no longer be started on boot." do not reveal that these are different things, it just looks like some sloppy short version. It's not obvious from the docs, that there's two functionally different "disabled" states. Btw., snap list should show both disabled states. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900356 Title: transition from systemd to snapd breaks functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900356/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
