Package: snapd
Version: 2.30-5+b1
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrade from Debian Stretch to Debian Buster.
* What exactly did you do (or not do) that was effective (or
ineffective)?
None - not sure how to tackle the situation. Need advice.
* What was the outcome of this action?
N/A
* What outcome did you expect instead?
N/A
On every boot of the system, boot hangs at
'[ *** ] A start job is running for Snappy daemon (1s / 1min 31s)'
The boot process continues after 1 minute and 31 seconds.
I have supplied some debug information below. Please advise as to what
else is needed to help resolve this bug.
Regards,
Joe
Debug info:
$ Journalctl -u snapd
-- Logs begin at Fri 2018-10-26 11:35:26 AEDT, end at Fri 2018-10-26 11:54:41
AEDT. --
Oct 26 11:35:27 jaczel-desktop systemd[1]: Starting Snappy daemon...
Oct 26 11:36:47 jaczel-desktop systemd[1]: snapd.service: Start operation timed
out. Terminating.
Oct 26 11:36:47 jaczel-desktop systemd[1]: snapd.service: Failed with result
'timeout'.
Oct 26 11:36:47 jaczel-desktop systemd[1]: Failed to start Snappy daemon.
Oct 26 11:36:48 jaczel-desktop systemd[1]: snapd.service: Service
RestartSec=100ms expired, scheduling restart.
Oct 26 11:36:48 jaczel-desktop systemd[1]: snapd.service: Scheduled restart
job, restart counter is at 1.
Oct 26 11:36:48 jaczel-desktop systemd[1]: Stopped Snappy daemon.
Oct 26 11:36:48 jaczel-desktop systemd[1]: Starting Snappy daemon...
Oct 26 11:38:18 jaczel-desktop systemd[1]: snapd.service: Start operation timed
out. Terminating.
Oct 26 11:38:18 jaczel-desktop systemd[1]: snapd.service: Failed with result
'timeout'.
Oct 26 11:38:18 jaczel-desktop systemd[1]: Failed to start Snappy daemon.
Oct 26 11:38:18 jaczel-desktop systemd[1]: snapd.service: Service
RestartSec=100ms expired, scheduling restart.
Oct 26 11:38:18 jaczel-desktop systemd[1]: snapd.service: Scheduled restart
job, restart counter is at 2.
Oct 26 11:38:18 jaczel-desktop systemd[1]: Stopped Snappy daemon.
Oct 26 11:38:18 jaczel-desktop systemd[1]: Starting Snappy daemon...
Oct 26 11:38:36 jaczel-desktop snapd[1939]: AppArmor status: apparmor is
enabled but some features are missing: dbus, network
Oct 26 11:38:36 jaczel-desktop snapd[1939]: AppArmor status: apparmor is
enabled but some features are missing: dbus, network
Oct 26 11:38:37 jaczel-desktop snapd[1939]: daemon.go:344: started snapd/2.35.4
(series 16; classic; devmode) debian/ (amd64) linux/4.18.0-2-amd64.
Oct 26 11:38:37 jaczel-desktop systemd[1]: Started Snappy daemon.
$ snap list
Name Version Rev Tracking Publisher
Notes
atom 1.32.0 204 stable snapcrafters
classic
core 16-2.35.4 5662 stable canonical✓
core
gtk-common-themes 0.1 701 stable canonical✓ -
nextcloud-client 2.3.3+gitab40efe 10 stable nextcloud✓ -
slack 3.3.3 9 stable slack✓
classic
telegram-desktop 1.4.3-alpha-2-g0c2de43 291 stable telegram.desktop -
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8),
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages snapd depends on:
ii adduser 3.118
ii apparmor 2.13-8
ii ca-certificates 20170717
ii gnupg 2.2.10-3
ii libapparmor1 2.13-8
ii libc6 2.27-6
ii libcap2 1:2.25-1.2
ii libseccomp2 2.3.3-3
ii libudev1 239-10
ii openssh-client 1:7.8p1-1
ii squashfs-tools 1:4.3-6
ii systemd 239-10
snapd recommends no packages.
snapd suggests no packages.
-- no debconf information
