Mit*_*nal 3 apparmor snap 18.04
我的机器上的 snapd 无法正常工作，我尝试使用重新安装 sudo apt install --reinstall snapd
我收到以下错误。
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) ...
我重新启动了机器并尝试了这个，但没有运气。
我该如何解决这个问题？
更新：
systemctl status snapd.service和journalctl -xe. 下面是他们的输出。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
snap list，snap version以及snap warningsmithilesh@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
sudo apt autoclean并sudo apt autoremove没有通过任何错误。但是对于sudo apt update，google-chorme应用程序会返回警告。输出有点奇怪。
我可以建议通过清除snapd软件包并使用以下命令重新安装它来从头开始：
sudo apt-get purge snapd
sudo apt-get install snapd
| 归档时间： |
|
| 查看次数： |
8118 次 |
| 最近记录： |