I’m working on my oss tool found at Kushtaka.org and I started shipping it as a snap. I encountered a weird edge case that I’m hoping someone can help me with.
Kushtaka can act as either a server or a sensor and after you install the snap, you either enable/disable the mode of operation you want.
I noticed that after I run snap refresh kushtaka the --disabled service will be re-enabled.
As I do not want this, I’m wondering how I can account for it? Thoughts?
well, how did you disable the service in the first place ?
if via systemctl, that might indeed be ingored by snapd … you should use snap stop --disable <snap>.<app>, if this does not save the state, then there is a bug somewhere …
Can you try refreshing to the edge channel of the core snap and trying your situation again? we should have this fixed in the edge channel due to https://github.com/snapcore/snapd/pull/7431
Hi, can you try this again with the core snap from the beta channel?
$ snap refresh core --beta
$ snap version
snap 2.43~pre1
snapd 2.43~pre1
series 16
ubuntu 19.04
kernel 5.0.0-37-generic
host amd64
I tested again and am no longer able to reproduce this with the released beta channel. I think the issue previously was that we hadn’t yet actually released a version of snapd with the fix in.