possibly some relevant info, from journalctl -o short-monotonic

[  540.929982] sstest-616 systemd[1]: snapd.seeded.service: Failed to reset 
devices.list: Operation not permitted
[  540.930083] sstest-616 sshd[257]: Server listening on 0.0.0.0 port 22.
[  540.931309] sstest-616 sshd[257]: Server listening on :: port 22.
[  540.931397] sstest-616 systemd[1]: Starting Wait until snapd is fully 
seeded...
<snip 40 second delay>
[  565.816128] sstest-616 systemd-networkd[155]: Could not set hostname: Method 
call timed out
[  580.923210] sstest-616 snapd[211]: 2018/07/19 17:27:06.134123 
stateengine.go:101: state ensure error: Get 
https://api.snapcraft.io/api/v1/snaps/sections: net/http: request canceled 
while waiting for connection (Client.Timeout exceeded while awaiting headers)
[  581.042394] sstest-616 systemd[1]: Started Wait until snapd is fully seeded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782616

Title:
  long delay (40 seconds) in boot due to snapd.seeded.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782616/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to