note that this is not reproducable on any machine i tried, as described in:
https://forum.snapcraft.io/t/have-a-snap-be-run-only-when-started- manually/20493 The mechanism to manually start disabled snap services seems to work just as it should (and given how many snaps in IoT use such a setup (disabling services after install from a hook and starting them from some master daemon snap on demand) there would be quite an outcry if it failed): $ sudo snap stop --disable lxd Stopped. $ sudo snap start lxd Started. $ on a side-note the apport data above points to a manually modified conffile in /etc/sudoers.d/99-snapd.conf, this contains the default PATH settings for sudo when dealing with snaps, did you modify it on purpose ... ? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
