Comment 29 for bug 1839237

To stop this SSD killing, I ran `sudo systemctl stop snapd`. The daemon doesn't stop (probably depends on `snapd.socket`).
But then I run `snap change 79` again and see that` core` is installed, and the load percentage of `chromium` starts to update. The packets are installed in a minute.

snap change 79
Status Spawn Ready Summary
Done today at 06:19 MSK today at 06:19 MSK Проверка доступности необходимых компонентов "core"
Done today at 06:19 MSK today at 08:34 MSK Загрузить пакет "core" (10185) с канала "latest/stable"
Done today at 06:19 MSK today at 08:34 MSK Получить и проверить подтверждение для пакета "core" (10185)
Done today at 06:19 MSK today at 08:34 MSK Подключить пакет "core" (10185)
...
Done today at 06:19 MSK today at 08:34 MSK Проверка доступности необходимых компонентов "chromium"
Done today at 06:19 MSK today at 08:36 MSK Загрузить пакет "chromium" (1362) с канала "latest/stable"
Done today at 06:19 MSK today at 08:36 MSK Получить и проверить подтверждение для пакета "chromium" (1362)
Done today at 06:19 MSK today at 08:36 MSK Подключить пакет "chromium" (1362)
Done today at 06:19 MSK today at 08:36 MSK Run pre-refresh hook of "chromium" snap if present
Done today at 06:19 MSK today at 08:36 MSK Stop snap "chromium" services
...
Done today at 06:19 MSK today at 08:36 MSK Consider re-refresh of "core", "chromium"

......................................................................
Consider re-refresh of "core", "chromium"

2020-10-23T08:36:32+03:00 INFO No re-refreshes found.

Do I understand correctly that every time the computer starts, it is necessary to manually stop the snap or try to restart it? To avoid killing SSD and wasting resources?