snapd.seeded.service never completes preventing full boot to default target
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
High
|
Unassigned | ||
snapd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
systemd-analyze always says "Bootup is not yet finished. Please try again later." no matter how long I wait (hours, days, ...).
The graphical.target (default one) is indeed never reached due to snapd.seeded.
$ systemctl list-jobs
JOB UNIT TYPE STATE
8 graphical.target start waiting
120 snapd.seeded.
9 multi-user.target start waiting
174 ureadahead-
117 systemd-
5 jobs listed.
To let the boot complete, I need to manually force a service stop with:
$ sudo systemctl stop snapd.seeded.
Then, all the waiting jobs are fired and complete ~instantly thus completing the boot process and fixing systemd-analyse:
$ systemctl list-jobs
No jobs running.
$ systemd-analyze
Startup finished in 3.360s (firmware) + 15.447s (loader) + 11.693s (kernel) + 2h 15min 59.902s (userspace) = 2h 16min 30.404s
graphical.target reached after 2h 15min 59.892s in userspace
So clearly something's wrong with snapd.seeded.
$ systemd-analyze blame | head
2h 15min 55.944s snapd.seeded.
6.602s NetworkManager-
4.115s plymouth-
3.624s <email address hidden>
2.458s systemd-
2.403s systemd-
1.265s dev-mapper-
839ms unbound.service
800ms fwupd.service
709ms dev-loop2.device
snapd's journal entries:
$ journalctl -b0 -u snapd | cat -
-- Logs begin at Tue 2018-10-23 09:45:59 EDT, end at Fri 2018-11-30 11:00:02 EST. --
Nov 30 08:32:54 simon-lemur systemd[1]: Starting Snappy daemon...
Nov 30 08:32:55 simon-lemur snapd[1952]: AppArmor status: apparmor is enabled and all features are available
Nov 30 08:32:55 simon-lemur snapd[1952]: 2018/11/30 08:32:55.130505 helpers.go:521: cannot retrieve info for snap "gnome-characters": cannot find installed snap "gnome-characters" at revision 103: missing file /snap/gnome-
Nov 30 08:32:55 simon-lemur snapd[1952]: 2018/11/30 08:32:55.140720 daemon.go:343: started snapd/2.34.2+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.
Nov 30 08:32:55 simon-lemur systemd[1]: Started Snappy daemon.
Nov 30 08:32:55 simon-lemur snapd[1952]: 2018/11/30 08:32:55.143355 stateengine.go:101: state ensure error: Get https:/
Additional information:
$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
$ apt-cache policy snapd
snapd:
Installed: 2.34.2+18.04
Candidate: 2.34.2+18.04
Version table:
*** 2.34.2+18.04 500
500 http://
100 /var/lib/
2.32.5+18.04 500
500 http://
$ snap list
Name Version Rev Tracking Publisher Notes
canonical-livepatch 8.0.2 41 stable canonical -
core 16-2.33.1 4917 stable canonical core
git-ubuntu 0.7.4+git16.0a79cbc 391 stable canonical classic
gnome-3-26-1604 3.26.0 70 stable/… canonical -
gnome-calculator 3.28.2 180 stable/… canonical -
lxd 3.2 7792 stable canonical -
vlc 3.0.4 555 stable videolan -
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: snapd 2.34.2+18.04
ProcVersionSign
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 30 10:51:28 2018
InstallationDate: Installed on 2018-07-15 (138 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
ProcEnviron:
LANG=en_CA.UTF-8
TERM=xterm-
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in snapd: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in snapd (Ubuntu): | |
status: | New → Fix Released |
I just realized now that this issue is preventing snap from refreshing all my snaps:
$ sudo snap refresh lxd
error: cannot refresh "lxd": snap "lxd" has "seed" change in progress
An example of this is that lxd is stuck at version 3.2 while it should be at 3.7:
$ snap info lxd | sed -n '/^channels:/,$ p'
channels:
stable: 3.7 (9664) 53MB -
candidate: 3.8 (9786) 54MB -
beta: ↑
edge: git-ae0a670 (9788) 54MB -
3.0/stable: 3.0.3 (9663) 53MB -
3.0/candidate: 3.0.3 (9663) 53MB -
3.0/beta: ↑
3.0/edge: git-18c9b88 (9673) 53MB -
2.0/stable: 2.0.11 (8023) 28MB -
2.0/candidate: 2.0.11 (8023) 28MB -
2.0/beta: ↑
2.0/edge: git-c7c4cc8 (9257) 26MB -
installed: 3.2 (7792) 57MB -