- Печать
Страницы: [1] 2 Все Вниз
Тема: Snap перестал работать и не запускается после обновления на 20.04 (Прочитано 11138 раз)
0 Пользователей и 1 Гость просматривают эту тему.
ArgumentCL
Обновился на 20.04 с 18.04. После обновления обнаружил, что 11 пакетов программ не обновились. Все относились к snap, среди прочих — gimp.
Одновременно с этим, пропал ярлык приложения Телеграмма и пришлось запускать его через «менеджер приложений Ubuntu». Запустился.
Через стандартные средства обновления пытался дообновиться. Загрузились какие-то обновления. Заметил, что у меня недоступен Livepatch. При попытках его запуска через терминал, получал сообщени про несоответствия кода устройства. Точного текста уже не восстановлю, спустя два дня попыток.
Обновил всё что было возможно через:
$ sudo apt update
В результате:
— Пропал менеджер приложений.
В общем, решил попробовать перезапустить snapd, команда stop прошла. С тех пор его запустить не получается.
В ответ на запрос:
sudo snap services или
sudo snap services lxd Service
Выдаёт ответ:
ошибка: cannot communicate with server: Get http://localhost/v2/apps?select=service: dial unix /run/snapd.socket: connect: connection refused
Выдача по
cat /etc/apt/sources.list
# deb cdrom:[Ubuntu 18.04.4 LTS _Bionic Beaver_ - Release amd64 (20200203.1)]/ bionic main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://cz.archive.ubuntu.com/ubuntu/ focal main restricted
deb-src http://cz.archive.ubuntu.com/ubuntu/ focal universe restricted multiverse main #Added by software-properties
deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://cz.archive.ubuntu.com/ubuntu/ focal-updates main restricted
deb-src http://cz.archive.ubuntu.com/ubuntu/ focal-updates universe restricted multiverse main #Added by software-properties
deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://cz.archive.ubuntu.com/ubuntu/ focal universe
deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic universe
deb http://cz.archive.ubuntu.com/ubuntu/ focal-updates universe
deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://cz.archive.ubuntu.com/ubuntu/ focal multiverse
deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://cz.archive.ubuntu.com/ubuntu/ focal-updates multiverse
deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://cz.archive.ubuntu.com/ubuntu/ focal-backports restricted multiverse universe main
deb-src http://cz.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse #Added by software-properties
# deb-src http://ua.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://archive.canonical.com/ubuntu focal partner
deb-src http://archive.canonical.com/ubuntu focal partner
deb http://cz.archive.ubuntu.com/ubuntu/ focal-security main restricted
deb-src http://cz.archive.ubuntu.com/ubuntu/ focal-security universe restricted multiverse main #Added by software-properties
deb-src http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://cz.archive.ubuntu.com/ubuntu/ focal-security universe
deb-src http://security.ubuntu.com/ubuntu bionic-security universe
deb http://cz.archive.ubuntu.com/ubuntu/ focal-security multiverse
deb-src http://security.ubuntu.com/ubuntu bionic-security multiverse
deb http://security.ubuntu.com/ubuntu/ focal-security restricted multiverse universe main
Пользователь добавил сообщение 25 Сентября 2020, 17:57:52:
Есть данные журналов, но они сюда не влазят ((( Лимит размера сообщения.
Делал запросы по:
zgrep snapd $(/bin/ls -r /var/log/syslog*) | grep -v audit
И
journalctl -u snapd
В последнем, записи за март месяц …
« Последнее редактирование: 25 Сентября 2020, 17:57:52 от ArgumentCL »
valrust
ArgumentCL, а какое состояние демона snapd?
sudo systemctl status snapd.service
ArgumentCL
argumentcl@Argumentcl-pc:~$ systemctl status snapd.service
● snapd.service - Snap Daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-09-24 21:46:17 EEST; 21h ago
TriggeredBy: ● snapd.socket
Main PID: 3376 (code=exited, status=1/FAILURE)
сен 24 21:46:17 Argumentcl-pc systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
сен 24 21:46:17 Argumentcl-pc systemd[1]: Stopped Snap Daemon.
сен 24 21:46:17 Argumentcl-pc systemd[1]: snapd.service: Start request repeated too quickly.
сен 24 21:46:17 Argumentcl-pc systemd[1]: snapd.service: Failed with result 'exit-code'.
сен 24 21:46:17 Argumentcl-pc systemd[1]: Failed to start Snap Daemon.
сен 24 21:46:17 Argumentcl-pc systemd[1]: snapd.service: Triggering OnFailure= dependencies.
valrust
Давайте логи посмотрим
sudo journalctl -u snapd.service
ArgumentCL
Давайте логи посмотрим
argumentcl@Argumentcl-pc:~$ sudo journalctl -u snapd.service
[sudo] пароль для argumentcl:
-- Logs begin at Tue 2020-03-03 18:10:53 EET, end at Fri 2020-09-25 19:17:50 EEST. --
мар 03 18:11:04 Argumentcl-pc systemd[1]: Starting Snappy daemon...
мар 03 18:11:09 Argumentcl-pc snapd[1037]: AppArmor status: apparmor is enabled and all features are available
мар 03 18:11:10 Argumentcl-pc snapd[1037]: daemon.go:346: started snapd/2.42.1+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/5.3.0-40-generic.
мар 03 18:11:10 Argumentcl-pc snapd[1037]: daemon.go:439: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
мар 03 18:11:10 Argumentcl-pc snapd[1037]: helpers.go:104: error trying to compare the snap system key: system-key missing on disk
мар 03 18:11:11 Argumentcl-pc systemd[1]: Started Snappy daemon.
мар 03 18:11:11 Argumentcl-pc snapd[1037]: stateengine.go:150: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io: no such host
мар 03 18:11:56 Argumentcl-pc snapd[1037]: daemon.go:540: gracefully waiting for running hooks
мар 03 18:11:56 Argumentcl-pc snapd[1037]: daemon.go:542: done waiting for running hooks
мар 03 18:11:57 Argumentcl-pc systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
мар 03 18:11:57 Argumentcl-pc systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
мар 03 18:11:57 Argumentcl-pc systemd[1]: Stopped Snappy daemon.
мар 03 18:11:57 Argumentcl-pc systemd[1]: Starting Snappy daemon...
мар 03 18:11:57 Argumentcl-pc snapd[2254]: AppArmor status: apparmor is enabled and all features are available
мар 03 18:11:57 Argumentcl-pc snapd[2254]: AppArmor status: apparmor is enabled and all features are available
мар 03 18:11:58 Argumentcl-pc snapd[2254]: patch.go:64: Patching system state level 6 to sublevel 1...
мар 03 18:11:58 Argumentcl-pc snapd[2254]: patch.go:64: Patching system state level 6 to sublevel 2...
мар 03 18:11:58 Argumentcl-pc snapd[2254]: daemon.go:346: started snapd/2.42.5 (series 16; classic) ubuntu/18.04 (amd64) linux/5.3.0-40-generic.
мар 03 18:11:58 Argumentcl-pc snapd[2254]: daemon.go:439: adjusting startup timeout by 35s (pessimistic estimate of 30s plus 5s per snap)
мар 03 18:11:59 Argumentcl-pc systemd[1]: Started Snappy daemon.
мар 03 18:24:58 Argumentcl-pc snapd[2254]: 2020/03/03 18:24:58 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-outrnCache-Control: no-cachernConnection: closern>
мар 03 20:23:19 Argumentcl-pc snapd[2254]: 2020/03/03 20:23:19 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-outrnCache-Control: no-cachernConnection: closern>
мар 03 22:41:27 Argumentcl-pc snapd[2254]: main.go:149: Exiting on terminated signal.
мар 03 22:41:27 Argumentcl-pc systemd[1]: Stopping Snappy daemon...
мар 03 22:41:27 Argumentcl-pc systemd[1]: Stopped Snappy daemon.
-- Reboot --
мар 03 22:42:59 Argumentcl-pc systemd[1]: Starting Snappy daemon...
мар 03 22:43:03 Argumentcl-pc snapd[1185]: AppArmor status: apparmor is enabled and all features are available
мар 03 22:43:05 Argumentcl-pc snapd[1185]: AppArmor status: apparmor is enabled and all features are available
мар 03 22:43:06 Argumentcl-pc snapd[1185]: daemon.go:346: started snapd/2.42.5 (series 16; classic) ubuntu/18.04 (amd64) linux/5.3.0-40-generic.
мар 03 22:43:06 Argumentcl-pc snapd[1185]: daemon.go:439: adjusting startup timeout by 1m10s (pessimistic estimate of 30s plus 5s per snap)
мар 03 22:43:07 Argumentcl-pc systemd[1]: Started Snappy daemon.
мар 03 22:43:07 Argumentcl-pc snapd[1185]: autorefresh.go:390: Cannot prepare auto-refresh change: cannot refresh snap-declaration for "gnome-logs": Get https://api.snapcraft.io/api/v1/snaps/assertions/snap-dec>
мар 03 22:43:07 Argumentcl-pc snapd[1185]: stateengine.go:150: state ensure error: cannot refresh snap-declaration for "gnome-logs": Get https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/kIMf>
мар 04 10:33:41 Argumentcl-pc snapd[1185]: storehelpers.go:436: cannot refresh: snap has no updates available: "core18", "gnome-3-28-1804", "gnome-calculator", "gnome-characters", "gnome-logs", "gnome-system-mo>
мар 04 10:34:00 Argumentcl-pc snapd[1185]: daemon.go:540: gracefully waiting for running hooks
мар 04 10:34:00 Argumentcl-pc snapd[1185]: daemon.go:542: done waiting for running hooks
мар 04 10:34:26 Argumentcl-pc snapd[1185]: cannot run daemon: context deadline exceeded
мар 04 10:34:26 Argumentcl-pc systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
мар 04 10:34:26 Argumentcl-pc systemd[1]: snapd.service: Failed with result 'exit-code'.
мар 04 10:34:26 Argumentcl-pc systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
мар 04 10:34:26 Argumentcl-pc systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
мар 04 10:34:26 Argumentcl-pc systemd[1]: Stopped Snappy daemon.
мар 04 10:34:26 Argumentcl-pc systemd[1]: Starting Snappy daemon...
мар 04 10:34:26 Argumentcl-pc snapd[27022]: AppArmor status: apparmor is enabled and all features are available
мар 04 10:34:26 Argumentcl-pc snapd[27022]: AppArmor status: apparmor is enabled and all features are available
мар 04 10:34:27 Argumentcl-pc snapd[27022]: patch.go:64: Patching system state level 6 to sublevel 1...
мар 04 10:34:27 Argumentcl-pc snapd[27022]: patch.go:64: Patching system state level 6 to sublevel 2...
мар 04 10:34:27 Argumentcl-pc snapd[27022]: patch.go:64: Patching system state level 6 to sublevel 3...
мар 04 10:34:27 Argumentcl-pc snapd[27022]: daemon.go:346: started snapd/2.43.3 (series 16; classic) ubuntu/18.04 (amd64) linux/5.3.0-40-generic.
lines 1-51
valrust
Давайте еще информацию проанализируем.
Версия snap
sudo dpkg -s snapd
Работает ли разрешение хоста api.snapcraft.io
host api.snapcraft.io
ArgumentCL
Давайте еще информацию проанализируем.
argumentcl@Argumentcl-pc:~$ sudo dpkg -s snapd
[sudo] пароль для argumentcl:
Package: snapd
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 119060
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 2.46.1+20.04
Replaces: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9)
Depends: adduser, apparmor (>= 2.10.95-0ubuntu2.2), ca-certificates, openssh-client, squashfs-tools, systemd, udev, libc6 (>= 2.27), libfuse2 (>= 2.6), liblzma5 (>= 5.1.1alpha+20110809), libudev1 (>= 183), zlib1g (>= 1:1.1.4)
Recommends: gnupg
Suggests: zenity | kdialog
Breaks: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9)
Conflicts: snap (<< 2013-11-29-1ubuntu1)
Conffiles:
/etc/apparmor.d/usr.lib.snapd.snap-confine.real 78d546e8f97e64968eaf4fe33baa28d1
/etc/apt/apt.conf.d/20snapd.conf e0e08d8267c66b9f81340dd6500cb67a
/etc/profile.d/apps-bin-path.sh 80883f297d6ab4519e7e8dad927c04da
/etc/xdg/autostart/snap-userd-autostart.desktop 4aaaa2fe36462a072a72e09cad553362
/etc/sudoers.d/99-snapd.conf 64f236f1d75e511ee18e62fc16714a67 obsolete
Description: Daemon and tooling that enable snap packages
Install, configure, refresh and remove snap packages. Snaps are
'universal' packages that work across many different Linux systems,
enabling secure distribution of the latest apps and utilities for
cloud, servers, desktops and the internet of things.
.
Start with 'snap list' to see installed snaps.
Built-Using: apparmor (= 2.13.3-7ubuntu5.1), golang-1.13 (= 1.13.8-1ubuntu1), libcap2 (= 1:2.32-1), libseccomp (= 2.4.3-1ubuntu3.20.04.3)
Homepage: https://github.com/snapcore/snapd
И по хосту:
argumentcl@Argumentcl-pc:~$ host api.snapcraft.io
api.snapcraft.io has address 91.189.92.40
api.snapcraft.io has address 91.189.92.20
api.snapcraft.io has address 91.189.92.41
api.snapcraft.io has address 91.189.92.38
api.snapcraft.io has address 91.189.92.19
api.snapcraft.io has address 91.189.92.39
Я не опытен в работе с терминалом, да и с линуксом в целом, поэтому выложил выше не весь лог, а только первый экран выдачи. Сейчас я смог открыть весь лог, попытаюсь прикрепить его отдельным файлом.
Пользователь добавил сообщение 25 Сентября 2020, 20:26:27:
Вложение
« Последнее редактирование: 25 Сентября 2020, 20:26:27 от ArgumentCL »
valrust
Попробуйте переустановить пакет snapd
sudo apt reinstall snapd
ArgumentCL
Попробуйте переустановить пакет snapd
argumentcl@Argumentcl-pc:~$ sudo apt reinstall snapd
[sudo] пароль для argumentcl:
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Следующие пакеты устанавливались автоматически и больше не требуются:
libbrotli1:i386 libcommon-sense-perl libfluidsynth2 libinstpatch-1.0-2 libjson-xs-perl libmikmod3 libntfs-3g88 libsdl-mixer1.2 libsdl-net1.2 libsdl-ttf2.0-0 libtypes-serialiser-perl python3-scour scour
timgm6mb-soundfont
Для их удаления используйте «sudo apt autoremove».
Обновлено 0 пакетов, установлено 0 новых пакетов, переустановлено 1 пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.
Необходимо скачать 27,6 MB архивов.
После данной операции объём занятого дискового пространства возрастёт на 0 B.
Пол:1 http://cz.archive.ubuntu.com/ubuntu focal-updates/main amd64 snapd amd64 2.46.1+20.04 [27,6 MB]
Получено 27,6 MB за 3с (8.832 kB/s)
dpkg: предупреждение: список файлов пакета «lp-solve» отсутствует; предполагаем, что на данный момент у пакета нет установленных файлов
(Чтение базы данных … на данный момент установлен 238301 файл и каталог.)
Подготовка к распаковке …/snapd_2.46.1+20.04_amd64.deb …
Распаковывается snapd (2.46.1+20.04) на замену (2.46.1+20.04) …
Настраивается пакет snapd (2.46.1+20.04) …
ошибка: cannot read state: EOF
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
Job for snapd.service failed because the control process exited with error code.
See "systemctl status snapd.service" and "journalctl -xe" for details.
Job for snapd.seeded.service failed because the control process exited with error code.
See "systemctl status snapd.seeded.service" and "journalctl -xe" for details.
Обрабатываются триггеры для mime-support (3.64ubuntu1) …
Обрабатываются триггеры для gnome-menus (3.36.0-1ubuntu1) …
Обрабатываются триггеры для man-db (2.9.1-1) …
Обрабатываются триггеры для dbus (1.12.16-2ubuntu2.1) …
Обрабатываются триггеры для desktop-file-utils (0.24-1ubuntu3) …
Контрольные запросы:
argumentcl@Argumentcl-pc:~$ sudo snap services lxd Service
ошибка: cannot communicate with server: Get http://localhost/v2/apps?names=lxd%2CService&select=service: dial unix /run/snapd.socket: connect: connection refused
argumentcl@Argumentcl-pc:~$ systemctl status snapd.service
● snapd.service - Snap Daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-09-25 20:46:25 EEST; 1min 58s ago
TriggeredBy: ● snapd.socket
Process: 27622 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
Main PID: 27622 (code=exited, status=1/FAILURE)
сен 25 20:46:25 Argumentcl-pc systemd[1]: Starting Snap Daemon...
сен 25 20:46:25 Argumentcl-pc systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
сен 25 20:46:25 Argumentcl-pc systemd[1]: snapd.service: Failed with result 'exit-code'.
сен 25 20:46:25 Argumentcl-pc systemd[1]: Failed to start Snap Daemon.
сен 25 20:46:25 Argumentcl-pc systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
сен 25 20:46:25 Argumentcl-pc systemd[1]: Stopped Snap Daemon.
сен 25 20:46:25 Argumentcl-pc systemd[1]: snapd.service: Start request repeated too quickly.
сен 25 20:46:25 Argumentcl-pc systemd[1]: snapd.service: Failed with result 'exit-code'.
сен 25 20:46:25 Argumentcl-pc systemd[1]: Failed to start Snap Daemon.
сен 25 20:46:25 Argumentcl-pc systemd[1]: snapd.service: Triggering OnFailure= dependencies.
argumentcl@Argumentcl-pc:~$
valrust
Посмотрите, существует ли файл /var/lib/snapd/state.json и какие у него права:
sudo ls -l /var/lib/snapd/state.jsonВладелец должен быть root и права тоже только у него.
И что бы проверить структуру файла установите обработчик JSON
sudo apt install jq
Потом выведите ключи у JSON файла /var/lib/snapd/state.json
sudo cat /var/lib/snapd/state.json | jq keys
Должно выйти, что-то типа такого
Если ошибок не было, то файл не поврежден.
ArgumentCL
Должно выйти, что-то типа такого
С ключами выходит незадача:
argumentcl@Argumentcl-pc:~$ sudo apt install jq
[sudo] пароль для argumentcl:
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Следующие пакеты устанавливались автоматически и больше не требуются:
libbrotli1:i386 libcommon-sense-perl libfluidsynth2 libinstpatch-1.0-2
libjson-xs-perl libmikmod3 libntfs-3g88 libsdl-mixer1.2 libsdl-net1.2
libsdl-ttf2.0-0 libtypes-serialiser-perl python3-scour scour
timgm6mb-soundfont
Для их удаления используйте «sudo apt autoremove».
Будут установлены следующие дополнительные пакеты:
libjq1 libonig5
Следующие НОВЫЕ пакеты будут установлены:
jq libjq1 libonig5
Обновлено 0 пакетов, установлено 3 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.
Необходимо скачать 313 kB архивов.
После данной операции объём занятого дискового пространства возрастёт на 1.062 kB.
Хотите продолжить? [Д/н] д
Пол:1 http://cz.archive.ubuntu.com/ubuntu focal/universe amd64 libonig5 amd64 6.9.4-1 [142 kB]
Пол:2 http://cz.archive.ubuntu.com/ubuntu focal/universe amd64 libjq1 amd64 1.6-1 [121 kB]
Пол:3 http://cz.archive.ubuntu.com/ubuntu focal/universe amd64 jq amd64 1.6-1 [50,2 kB]
Получено 313 kB за 2с (195 kB/s)
Выбор ранее не выбранного пакета libonig5:amd64.
dpkg: предупреждение: список файлов пакета «lp-solve» отсутствует; предполагаем,
что на данный момент у пакета нет установленных файлов
(Чтение базы данных … на данный момент установлен 238301 файл и каталог.)
Подготовка к распаковке …/libonig5_6.9.4-1_amd64.deb …
Распаковывается libonig5:amd64 (6.9.4-1) …
Выбор ранее не выбранного пакета libjq1:amd64.
Подготовка к распаковке …/libjq1_1.6-1_amd64.deb …
Распаковывается libjq1:amd64 (1.6-1) …
Выбор ранее не выбранного пакета jq.
Подготовка к распаковке …/archives/jq_1.6-1_amd64.deb …
Распаковывается jq (1.6-1) …
Настраивается пакет libonig5:amd64 (6.9.4-1) …
Настраивается пакет libjq1:amd64 (1.6-1) …
Настраивается пакет jq (1.6-1) …
Обрабатываются триггеры для man-db (2.9.1-1) …
Обрабатываются триггеры для libc-bin (2.31-0ubuntu9.1) …
argumentcl@Argumentcl-pc:~$ sudo ls -l /var/lib/snapd/state.json
-rw------- 1 root root 0 сен 24 15:03 /var/lib/snapd/state.json
argumentcl@Argumentcl-pc:~$ sudo cat /var/lib/snapd/state.json | jq keys
argumentcl@Argumentcl-pc:~$ ^C
argumentcl@Argumentcl-pc:~$
В свойствах файла state.json
Указано:
— Владелец root;
— Группа root;
— Просмотр — Только владелец;
— Изменения — Только владелец;
— Запуск — Никто.
— Размер — 0 байтов.
— Последнее изменение — 24.09.2020 15:03
— Последнее изменение прав 24.09.2020 15:03
— Время последнего доступа — 25.09.2020 20:46 (это время выполнения команды
ystemctl status snapd.service из инструкции выше).
Пользователь добавил сообщение 26 Сентября 2020, 21:56:26:
Проблему решил, частично.
Провёл вот эту серию команд:
sudo fuser -vki /var/lib/dpkg/lock
sudo apt purge snapd
sudo dpkg --configure -a
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo apt install snapd
И переустановил lxd. Кстати стали не все пакеты, но …
argumentcl@Argumentcl-pc:~$ sudo snap services lxd Service
ошибка: snap "Service" not found
argumentcl@Argumentcl-pc:~$ sudo snap services
Service Startup Current Notes
lxd.activate enabled inactive -
lxd.daemon enabled active socket-activated
argumentcl@Argumentcl-pc:~$
snapd.service - Snap Daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-09-26 20:34:06 EEST; 1h 2min ago
TriggeredBy: ● snapd.socket
Main PID: 795 (snapd)
Tasks: 21 (limit: 9297)
Memory: 849.3M
CGroup: /system.slice/snapd.service
└─795 /usr/lib/snapd/snapd
сен 26 20:34:05 Argumentcl-pc snapd[795]: daemon.go:436: adjusting startup timeout by 45s (pessimistic estimate of 30s plus 5s per snap)
сен 26 20:34:06 Argumentcl-pc systemd[1]: Started Snap Daemon.
сен 26 20:34:31 Argumentcl-pc snapd[795]: storehelpers.go:438: cannot refresh: snap has no updates available: "core18", "lxd", "snapd"
сен 26 20:34:31 Argumentcl-pc snapd[795]: autorefresh.go:410: auto-refresh: all snaps are up-to-date
сен 26 20:47:53 Argumentcl-pc snapd[795]: api.go:997: Installing snap "lxd" revision unset
сен 26 20:49:30 Argumentcl-pc snapd[795]: storehelpers.go:438: cannot refresh: snap has no updates available: "core18", "lxd", "snapd"
сен 26 20:49:50 Argumentcl-pc snapd[795]: api.go:997: Installing snap "opera" revision unset
сен 26 20:52:48 Argumentcl-pc snapd[795]: api.go:997: Installing snap "telegram" revision unset
сен 26 20:55:18 Argumentcl-pc snapd[795]: api.go:997: Installing snap "telegram-desktop" revision unset
сен 26 21:29:58 Argumentcl-pc snapd[795]: api.go:997: Installing snap "snap-store" revision unset
snap заработал, приложения устанавливаются. Вручную вернул менеджер приложений:
sudo apt install gnome-software-plugin-snap
Ещё добавил магазин альтернативный:
sudo snap install snap-store
Из незавершенного — только доустановить все пакеты в lxd, не могу придумать команду для обновления/усовершенствования.
Даже Livepatch запустился.
Вообще, внешне, всё запускается.
« Последнее редактирование: 26 Сентября 2020, 21:56:26 от ArgumentCL »
valrust
argumentcl@Argumentcl-pc:~$ sudo snap services lxd Service
Для чего это?
Из незавершенного — только доустановить все пакеты в lxd
sudo snap install lxdТакая команда не устанавливает lxd?
jurganov
а какой смысл ставить снапом то, что легко ставится нормальными способами?
The Green Side
jurganov, а сами то проверяли?
какой смысл давать совет, который не работает?
focal (20.04LTS) (admin): Transitional package — lxd -> snap (lxd) [universe]
Debian 11, Debian 11 Server
jurganov
ГИМП я ставил БЕЗ ВСЯКОГО идиотского снапа. и, о чудо!!, она работает!!
Снап я поставил, что бы установить телегу. Снес и телегу и снапд по бессмысленностью. А снапд ещё — за безмерное загаживание дискового пространства
- Печать
Страницы: [1] 2 Все Вверх
On a fresh Debian 10 install, I did :
sudo apt install snapd
sudo snap install notepad-plus-plus
but I received the message :
error: cannot perform the following tasks:
- Mount snap «notepad-plus-plus» (260) (snap «notepad-plus-plus» assumes unsupported features: snapd2.43 (try to update snapd and refresh the core snap))
Then, a sudo snap refresh notepad-plus-plus says it is not installed.
but a sudo snap refresh --list returns :
snap list
Name Version Rev Tracking Publisher Notes
core18 20210309 1997 stable canonical✓ base
gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 145 stable canonical✓ -
gtk-common-themes 0.1-52-gb92ac40 1515 stable canonical✓ -
wine-platform-5-stable 5.0.3 16 stable mmtrt -
wine-platform-runtime v1.0 216 stable mmtrt -
All is looking ok,
and no apt-get update/upgrade or sudo snap refresh find anything to change.
What’s the problem ?
-
RiversideRocks
- Posts: 16
- Joined: Fri Dec 25, 2020 8:01 pm
- Location: US
Can’t install Snap on Pi 4
I’m trying to install Snap on my raspberry Pi and I’m getting this error when I try to install Snap core.
Command run:
Code: Select all
sudo snap install core; sudo snap refresh core
Result:
Code: Select all
error: system does not fully support snapd: cannot mount squashfs image using
"squashfs": mount: /tmp/sanity-mountpoint-967431678: unknown filesystem type
'squashfs'.
error: system does not fully support snapd: cannot mount squashfs image using
"squashfs": mount: /tmp/sanity-mountpoint-967431678: unknown filesystem type
'squashfs'.
Any idea what this means and how I can fix it? Thanks!
-
B.Goode
- Posts: 14634
- Joined: Mon Sep 01, 2014 4:03 pm
- Location: UK
Re: Can’t install Snap on Pi 4
Tue Aug 31, 2021 11:27 am
RiversideRocks wrote: ↑
Mon Aug 30, 2021 7:48 pm
I’m trying to install Snap on my raspberry Pi and I’m getting this error when I try to install Snap core.Command run:
Code: Select all
sudo snap install core; sudo snap refresh coreResult:
Code: Select all
error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-967431678: unknown filesystem type 'squashfs'. error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-967431678: unknown filesystem type 'squashfs'.Any idea what this means and how I can fix it? Thanks!
It seems you have done what is documented here — https://snapcraft.io/docs/installing-snap-on-raspbian
Maybe ask Canonical for support of their product here: https://forum.snapcraft.io/
-
scruss
- Posts: 5221
- Joined: Sat Jun 09, 2012 12:25 pm
- Location: Toronto, ON
Re: Can’t install Snap on Pi 4
Tue Aug 31, 2021 2:39 pm
Have you installed snapd?
I’m not a fan of snap — it’s a fairly terrible way of managing dependencies — and if I can find a non-snap package to install, I will. Snaps tend to be very large and aren’t updated through the normal apt system.
‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.
Pronouns: he/him
-
craigevil
- Posts: 435
- Joined: Wed Jan 27, 2021 5:22 am
- Location: heaven
Re: Can’t install Snap on Pi 4
Tue Aug 31, 2021 4:51 pm
You might try using Gnome-Software
Code: Select all
sudo apt install gnome-software flatpak snapd gnome-software-plugin-snap gnome-software-plugin-flatpakRaspberry PI 400 Raspberry Pi OS (Debian Sid) Kernel: 6.1.8-v8+ aarch64 DE: XFCE 4.18
Debian — «If you can’t apt install something, it isn’t useful or doesn’t exist»
-
dickon
- Posts: 2320
- Joined: Sun Dec 09, 2012 3:54 pm
- Location: Home, in Tiffield
Re: Can’t install Snap on Pi 4
Tue Aug 31, 2021 5:07 pm
A fairly obvious solution to the OP’s error messages would be ‘modprobe squashfs’, but I’d expect snap to have done that already…
As it is apparently board policy to disallow any criticism of anything, as it appears to criticise something is to criticise all the users of that something, I will no longer be commenting in threads which are not directly relevant to my uses of the Pi.
-
bjtheone
- Posts: 2123
- Joined: Mon May 20, 2019 11:28 pm
- Location: The Frozen North (AKA Canada)
Re: Can’t install Snap on Pi 4
Wed Sep 01, 2021 7:56 pm
scruss wrote: ↑
Tue Aug 31, 2021 2:39 pm
Have you installed snapd?I’m not a fan of snap — it’s a fairly terrible way of managing dependencies — and if I can find a non-snap package to install, I will. Snaps tend to be very large and aren’t updated through the normal apt system.
Mixed system of some packages via snap and some via apt is a lovely way to confuse yourself and if you are extra lucky break your system. In theory snaps should be totally self contained, however the onus is then on you to maintain them. Not convinced that flatpaks are any better. I suppose you could modify make files and compile some yourself and add them to the mix to get a trifecta of goodness… 
It likely comes down to if you want to maintain a system or a bunch of separate «apps». There might be an argument to be made to maintain the system using apt, and install all your applications as snaps. If that is your plan, starting with Lite and building a minimal system with no «apps» is likely the way to go. The one win with snaps is you get standalone applications, at the expense of size, so can more easily get the latest and greatest without being held back by a core library dependency. Personally I am good with not being bleeding end and living with one unified package manager.
Return to “General discussion”
Ubuntu now allows you to use the snap command to install apps from a store. While it’s not designed to replace the Debian-derived apt-get system currently in use on most Ubuntu Linux installations, it does have the benefit of being fairly platform-agnostic. This is why it’s become popular on Ubuntu mobile installations.
You’ll need the command prompt for this, so you can start it from the Ubuntu Dash or by holding down Ctrl, Alt and T at the same time. You could also start it from the Dash or the LXDE menu’s System Tools list on Lubuntu. Xubuntu users may wish to start it up from the Whisker Menu. Before you attempt to use these methods, you’ll want to make sure that a good old sudo apt-get update command doesn’t fix your error right away. Many people aren’t actually using snaps yet.
Method 1: Refreshing the core snap Package
Unlike .deb packages, snap packages contain more or less everything that a particular piece of software needs to run so there aren’t really dependencies. Therefore if you’re getting dependency errors and you’re sure that it’s not with any package installed or updated via apt-get, then you’re more than likely suffering a problem with one of the two core snap packages. Assuming that you don’t have administrator access shown by a # symbol at your prompt, type sudo snap refresh core at the command prompt and push enter. You might get prompted for your administrator password.
Once you’ve typed it and pushed return, the snap package manager will start to update automatically. If it succeeded, then try running the program you were having issues with again and see if the dependency issues are gone. For instance, if you installed the 287 MB or so LibreOffice snap previously and got an error then start LibreOffice either from the Dash or by searching for it. You’ll find in the vast majority of cases this single command was enough to fix the issue and you won’t need to move on at all. If you wanted to see more about what type of error you were looking at, then just type libreoffice or whatever other package names at the command line with no other arguments to see if anything else were wrong.
Method 2: Reinstalling the core snap Package
Very few users will suffer any further problems beyond this, but if you had then you could uninstall the core snap package and any other snaps you’ve installed and then reinstall them. Keep in mind that if the first method worked, then this is totally unnecessary and can make you loose some of your configurations. You’ll want to make sure your data is backed up like usual before doing this, but fortunately, it can still be accomplished with an absolute minimum of playing around.
Make sure you’ve got nothing else open and then run sudo snap remove core snap-package1 snap-package2 from the command line and wait as it runs through the snap packages you have installed. Once it’s done, then type sudo snap install core snap-package1 snap-package2 from the command line and push enter. You’ll need to wait again for the packages to reconfigure themselves, but these two easy commands are enough to sort the issue out.
Method 3: Listing Installed snaps and Changes
You can check the details of any installed snaps at any time by simply running snap list from the command line, and you probably won’t need sudo access for it.
Likewise just run snap changes from the command line when you’re done with any of these tasks to see what changes have been made. Once you have your packages working again, presumably from the technique in the first method, you can always run sudo snap refresh from the command line to update all snaps at once.
Kevin Arrows
Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.
-
keos
- Posts: 105
- Joined: 2021-08-23 16:16
- Location: USA
- Has thanked: 1 time
[Solved] Problems trying to install snap
#1
Post
by keos » 2021-10-15 00:00
Hi,
I’m following these instructions in order to install this app but there is some kind of error with it …
https://snapcraft.io/docs/installing-snap-on-debian
Code: Select all
keos@kaos:~$ sudo snap install core
[sudo] password for keos:
error: cannot communicate with server: Post "http://localhost/v2/snaps/core": dial unix /run/snapd.socket: connect: connection refused
keos@kaos:~$
Thanks for any advice.
Last edited by keos on 2021-10-15 08:11, edited 1 time in total.
Quad Core Intel Core i5-8265U
Model: 0WHCP7 UEFI: Dell v: 1.5.1
Debian-‘testing’
Desktop: xfce4-panel 4.16.3
-
sunrat
- Administrator
- Posts: 5180
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 55 times
- Been thanked: 194 times
Re: Problems trying to install snap
#2
Post
by sunrat » 2021-10-15 04:14
keos wrote: ↑2021-10-15 00:00Thanks for any advice.
Advice? Don’t use snap. 
“ computer users can be divided into 2 categories:
Those who have lost data
…and those who have not lost data YET ” Remember to BACKUP!
-
keos
- Posts: 105
- Joined: 2021-08-23 16:16
- Location: USA
- Has thanked: 1 time
Re: Problems trying to install snap
#3
Post
by keos » 2021-10-15 07:51
Very well, I do not have preferences for any particular option, then … what is your recommendation to get apps that do not exist in Debian, not even in the ‘testing’ 
EDIT:
It seems that it was a temporary interruption, I already got it!:
Code: Select all
keos@kaos:~$ sudo snap install core
[sudo] password for keos:
2021-10-15T03:59:19-04:00 INFO Waiting for automatic snapd restart...
core 16-2.52 from Canonical✓ installed
keos@kaos:~$ sudo snap install hello-world
hello-world 6.4 from Canonical✓ installed
keos@kaos:~$ hello-world
bash: hello-world: orden no encontrada
keos@kaos:~$ sudo hello-world
sudo: hello-world: command not found
keos@kaos:~$ sudo snap install snap-store
snap-store 3.38.0-64-g23c4c77 from Canonical✓ installed
keos@kaos:~$
Thanks any way. 
Quad Core Intel Core i5-8265U
Model: 0WHCP7 UEFI: Dell v: 1.5.1
Debian-‘testing’
Desktop: xfce4-panel 4.16.3
-
cynwulf
Re: Problems trying to install snap
#4
Post
by cynwulf » 2021-10-15 10:28
keos wrote: ↑2021-10-15 07:51
Very well, I do not have preferences for any particular option, then … what is your recommendation to get apps that do not exist in Debian, not even in the ‘testing’
1) Find the project’s git repository and git clone, read the install instructions and just build it from source. You can even «Debianise» the source to build a deb package, or just change the install target to /usr/local
2) Download the source tarball and do as above.
3) If the project provides usable binaries, extract those into /usr/local, create launchers, etc — done.
-
keos
- Posts: 105
- Joined: 2021-08-23 16:16
- Location: USA
- Has thanked: 1 time
Re: [Solved] Problems trying to install snap
#5
Post
by keos » 2021-10-15 10:49
I have dealt with it before. Too technical for someone who is not even able to understand how those GUI work for the backup of the system — when I break it I have to reinstall again. And believe me it’s my most serious limitation.
I do not have more options than to use these alternatives, even if they are candidates to possible failures and have to start again reinstalling …
Either way, thank you very much for answering.
Greetings.
Quad Core Intel Core i5-8265U
Model: 0WHCP7 UEFI: Dell v: 1.5.1
Debian-‘testing’
Desktop: xfce4-panel 4.16.3
-
keos
- Posts: 105
- Joined: 2021-08-23 16:16
- Location: USA
- Has thanked: 1 time
Re: [Solved] Problems trying to install snap
#6
Post
by keos » 2021-10-15 13:50
And that’s not all, when we install packages with Snap there are no one who can finds them, and I do not mean that are not in the Menu but that they do not appear anywhere, incredible, everything is going worse.
Quad Core Intel Core i5-8265U
Model: 0WHCP7 UEFI: Dell v: 1.5.1
Debian-‘testing’
Desktop: xfce4-panel 4.16.3
-
craigevil
- Posts: 5418
- Joined: 2006-09-17 03:17
- Location: heaven
- Has thanked: 25 times
- Been thanked: 34 times
Re: [Solved] Problems trying to install snap
#7
Post
by craigevil » 2021-10-15 14:29
They go in weird places, like this is the command to open Firefox Beta:
env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/firefox_firefox.desktop /snap/bin/firefox %u
If you search the forum you will find a couple of ways to get Snaps and Flatpaks added to the menus.
Don’t worry about what anyone thinks, use what works for you.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB
Debian — «If you can’t apt install something, it isn’t useful or doesn’t exist»
My Giant Sources.list
-
keos
- Posts: 105
- Joined: 2021-08-23 16:16
- Location: USA
- Has thanked: 1 time
Re: [Solved] Problems trying to install snap
#8
Post
by keos » 2021-10-15 16:09
I always deal with it but it is difficult for me … the best thing that I can think of for now is to forget about Snap and go directly to Google to look if I can install some apps without a lot of tangle of adding repos, etc., this is giving to me good results till now.
I only worry about what people thinks when they bring reasonable issues.
Out of Topic:
Do you know about an *easy method* of being able to save the system installed with applications / configurations, etc. (backup/gui). In case I break debian …? — Clonezilla is simply impossible to understand.
Greetings.
Quad Core Intel Core i5-8265U
Model: 0WHCP7 UEFI: Dell v: 1.5.1
Debian-‘testing’
Desktop: xfce4-panel 4.16.3
-
Fossy
- Posts: 173
- Joined: 2021-08-06 12:45
- Has thanked: 21 times
- Been thanked: 20 times
Re: Problems trying to install snap
#9
Post
by Fossy » 2021-10-16 10:55
sunrat wrote: ↑2021-10-15 04:14
keos wrote: ↑2021-10-15 00:00Thanks for any advice.
Advice? Don’t use snap.
anyone who skims the Linux forums will have noticed by now that the «snap» lobby infiltrating ditto forums are working overtime .
Do not forget that Cannonical is not a charity, they think in terms of «ROI».
If you are convinced of the naive opposite then you better switch to Linux Mint which with its hot and cold blowing has opened the door wide for snap .
It remains a choice, of course, and a donkey’s appetite is half of its food.
I remember as far as I am concerned the wise advice , don’t install it , let alone use it …. regardless of the security aspect that is my «opinion» .
Asus GL753VD Intel© Core™ i7-7700HQ / Kernel 5.10 / Multi Boot with W10
currently running 11.6 Bullseye 64-bit Cinnamon /Firefox ESR /DuckDuckGo/ Evolution/eID Belgium/ Single Boot on 5 more Asus laptops
HP LaserJet Pro MFP M130fw
-
kedaha
- Posts: 3507
- Joined: 2008-05-24 12:26
- Has thanked: 33 times
- Been thanked: 75 times
Re: Problems trying to install snap
#10
Post
by kedaha » 2021-10-16 13:26
sunrat wrote: ↑2021-10-15 04:14
keos wrote: ↑2021-10-15 00:00Thanks for any advice.
Advice? Don’t use snap.
I concur.
My main objection is that, while the snapd package is available from the main repository and can allow free and gpl’d software to be installed like for instance, the scidvspc-hkvc chess program, it also—and here I draw the line—facilitates the installation of third-party, binary-only software with licenses that are wholly at variance with Debian policy. This defeats Debian’s purpose of providing a free operating system without such software. Since it is in the main repository, any security concerns can be addressed to the Debian Security team, but obviously non-free programs installed by means of snap cannot be audited for vulnerabilities. And the notification to the effect that, «This application is unconfined. It can access all personal files and system resources,» does not inspire confidence either.
-
keos
- Posts: 105
- Joined: 2021-08-23 16:16
- Location: USA
- Has thanked: 1 time
Re: [Solved] Problems trying to install snap
#11
Post
by keos » 2021-10-16 16:45
As i said before I only worry about what people thinks when they bring reasonable issues. 
How can i remove-purge all snap packages/issues/etc from my system?
Quad Core Intel Core i5-8265U
Model: 0WHCP7 UEFI: Dell v: 1.5.1
Debian-‘testing’
Desktop: xfce4-panel 4.16.3
-
craigevil
- Posts: 5418
- Joined: 2006-09-17 03:17
- Location: heaven
- Has thanked: 25 times
- Been thanked: 34 times
Re: [Solved] Problems trying to install snap
#12
Post
by craigevil » 2021-10-16 18:29
keos wrote: ↑2021-10-16 16:45
As i said before I only worry about what people thinks when they bring reasonable issues.How can i remove-purge all snap packages/issues/etc from my system?
That will still leave a snap dir in your home.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB
Debian — «If you can’t apt install something, it isn’t useful or doesn’t exist»
My Giant Sources.list
I am trying to get and install some https certificates for apache on Debian 10 by following this: https://certbot.eff.org/lets-encrypt/debianbuster-apache
Everything is going fine until step 7: sudo certbot --apache:
An error occurred while fetching Certbot snap plugins: your version of snapd is outdated.
Please run "sudo snap install core; sudo snap refresh core" in your terminal and try again.
An unexpected error occurred:
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://snapd/v2/connections?snap=certbot&interface=content
Please see the logfile '/tmp/tmp5xjbr23v/log' for more details.
When I run sudo snap install core; sudo snap refresh core:
snap "core" is already installed, see 'snap help refresh'
error: cannot refresh "core": refreshing disabled snap "core" not supported
Looking at the log (/tmp/tmp5xjbr23v/log):
2020-11-04 00:26:04,950:DEBUG:urllib3.connectionpool:http://localhost:None "GET /v2/connections?snap=certbot&interface=content HTTP/1.1" 404 88
2020-11-04 00:26:04,951:ERROR:certbot._internal.snap_config:An error occurred while fetching Certbot snap plugins: your version of snapd is outdated.
2020-11-04 00:26:04,951:ERROR:certbot._internal.snap_config:Please run "sudo snap install core; sudo snap refresh core" in your terminal and try again.
2020-11-04 00:26:04,951:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
File "/snap/certbot/652/bin/certbot", line 8, in <module>
sys.exit(main())
File "/snap/certbot/652/lib/python3.8/site-packages/certbot/main.py", line 15, in main
return internal_main.main(cli_args)
File "/snap/certbot/652/lib/python3.8/site-packages/certbot/_internal/main.py", line 1330, in main
cli_args = snap_config.prepare_env(cli_args)
File "/snap/certbot/652/lib/python3.8/site-packages/certbot/_internal/snap_config.py", line 67, in prepare_env
raise e
File "/snap/certbot/652/lib/python3.8/site-packages/certbot/_internal/snap_config.py", line 57, in prepare_env
response.raise_for_status()
File "/snap/certbot/652/lib/python3.8/site-packages/requests/models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://snapd/v2/connections?snap=certbot&interface=content
2020-11-04 00:26:04,951:ERROR:certbot._internal.log:An unexpected error occurred:
2020-11-04 00:26:04,951:ERROR:certbot._internal.log:requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://snapd/v2/connections?snap=certbot&interface=content
Here more details about the version that might be useful sudo snap version:
snap 2.37.4-1+b1
snapd 2.37.4-1+b1
series 16
debian 10
kernel 4.19.0-11-cloud-amd64
I tried to reinstall snapd (https://snapcraft.io/docs/installing-snap-on-debian) using the last version but still having the same..
Do you guys know what is wrong with my setup and how to fix that?
Thanks