web-dev-qa-db-fra.com

Impossible d'installer snapd sur Ubuntu 18.04.2 LTS

snapd sur ma machine ne fonctionne pas et j'ai essayé de réinstaller en utilisant Sudo apt install --reinstall snapd

J'ai eu l'erreur ci-dessous.

Unpacking snapd (2.38+18.04) over (2.38+18.04) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Setting up snapd (2.38+18.04) ...
md5sum: /etc/apparmor.d/usr.lib.snapd.snap-confine: No such file or directory
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.
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...

J'ai redémarré la machine et j'ai essayé mais pas de chance.
Comment puis-je resoudre ceci?

Mise à jour:

  1. Selon la sortie, j'ai exécuté les commandes systemctl status snapd.service et journalctl -xe. Ce qui suit est leur sortie.
mithilesh@linux:~$ systemctl status snapd.service
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: en
   Active: failed (Result: exit-code) since Sun 2019-05-19 16:55:24 IST; 5h 43mi
  Process: 833 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
 Main PID: 833 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomple

mithilesh@linux:~$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Activating 
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Activating 
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Activating 
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Activating 
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Successfull
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Successfull
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Successfull
May 19 22:36:35 linux nautilus[4154]: g_key_file_load_from_file: assertion 'file
May 19 22:36:35 linux nautilus[4154]: Could not establish a connection to Tracke
May 19 22:36:35 linux nautilus[4154]: g_queue_pop_head: assertion 'queue != NULL
May 19 22:36:35 linux nautilus[4154]: g_queue_pop_head: assertion 'queue != NULL
May 19 22:36:35 linux nautilus[4154]: g_queue_foreach: assertion 'queue != NULL'
May 19 22:36:35 linux nautilus[4154]: g_queue_free: assertion 'queue != NULL' fa
May 19 22:36:35 linux nautilus[4154]: g_queue_foreach: assertion 'queue != NULL'
May 19 22:36:35 linux nautilus[4154]: g_queue_free: assertion 'queue != NULL' fa
May 19 22:36:35 linux nautilus[4154]: g_queue_pop_head: assertion 'queue != NULL
May 19 22:36:35 linux dbus-daemon[2408]: [session uid=1000 pid=2408] Successfull
May 19 22:36:36 linux gnome-calendar[4156]: source_credentials_required_cb: Fail
May 19 22:36:37 linux nautilus[4154]: g_queue_foreach: assertion 'queue != NULL'
May 19 22:36:37 linux nautilus[4154]: g_queue_free: assertion 'queue != NULL' fa
  1. Sur la base des commentaires, ce qui suit est la sortie de l'exécution de snap list, snap version et snap warnings
mithilesh@linux:~$ snap list
error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/snaps: dial unix /run/snapd.socket: connect: connection refused
mithilesh@linux:~$ snap version
snap    2.38+18.04
snapd   unavailable
series  -
mithilesh@linux:~$ snap warnings
error: cannot communicate with server: Get http://localhost/v2/warnings: dial unix /run/snapd.socket: connect: connection refused
  1. Fonctionnement Sudo apt autoclean et Sudo apt autoremove n'a rencontré aucune erreur. Mais pour Sudo apt update, des avertissements sont renvoyés pour google-chorme application.
18.04snapapparmor
2
Mithilesh_Kunal

La sortie est un peu étrange.

Je peux recommander de recommencer à zéro en purgeant le package snapd et en le réinstallant avec les commandes ci-dessous:

Sudo apt-get purge snapd
Sudo apt-get install snapd
4
N0rbert