** Description changed:

  On Ubuntu Desktop Focal 20200221 after a fresh installation,
- snap.seeded.service never finishes loading and blocked multi-user.target
+ snap.seeded.service never finishes loading and blocked multi-
+ user.target. As a consequence it also blocks all the services that
+ depend on default.target.
  
  According to systemd it's waiting of a configuration variable to be set
  
- $ systemctl status snapd.seeded.service 
+ $ systemctl status snapd.seeded.service
  ● snapd.seeded.service - Wait until snapd is fully seeded
-      Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; 
vendor preset: enabled)
-      Active: activating (start) since Tue 2020-02-25 08:07:04 EST; 3min 24s 
ago
-    Main PID: 687 (snap)
-       Tasks: 8 (limit: 4657)
-      Memory: 11.2M
-      CGroup: /system.slice/snapd.seeded.service
-              └─687 /usr/bin/snap wait system seed.loaded
+      Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; 
vendor preset: enabled)
+      Active: activating (start) since Tue 2020-02-25 08:07:04 EST; 3min 24s 
ago
+    Main PID: 687 (snap)
+       Tasks: 8 (limit: 4657)
+      Memory: 11.2M
+      CGroup: /system.slice/snapd.seeded.service
+              └─687 /usr/bin/snap wait system seed.loaded
  
  journalctl contains the following messages:
  Feb 25 08:07:03 v systemd[1]: Starting Snappy daemon...
  Feb 25 08:07:04 v snapd[573]: AppArmor status: apparmor is enabled and all 
features are available
  Feb 25 08:07:04 v snapd[573]: patch.go:64: Patching system state level 6 to 
sublevel 1...
  Feb 25 08:07:04 v snapd[573]: patch.go:64: Patching system state level 6 to 
sublevel 2...
  Feb 25 08:07:04 v snapd[573]: patch.go:64: Patching system state level 6 to 
sublevel 3...
  Feb 25 08:07:04 v snapd[573]: daemon.go:346: started snapd/2.43.3+git1.8109f8 
(series 16; classic) ubuntu/20.04 (amd64) linux/5.4.0-14-generic.
  Feb 25 08:07:04 v snapd[573]: daemon.go:439: adjusting startup timeout by 30s 
(pessimistic estimate of 30s plus 5s per snap)
  Feb 25 08:07:04 v systemd[1]: Started Snappy daemon.
  Feb 25 08:07:05 v snapd[573]: stateengine.go:150: state ensure error: 
devicemgr: cannot resolve prerequisite assertion: account 
(EH9A6Xg1QtCjYt4v3QlBVTPLAHDvEIn6)
  Feb 25 08:12:04 v snapd[573]: stateengine.go:150: state ensure error: 
devicemgr: cannot resolve prerequisite assertion: account 
(EH9A6Xg1QtCjYt4v3QlBVTPLAHDvEIn6)
  ~
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: snapd 2.43.3+git1.8109f8
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 08:10:54 2020
  InstallationDate: Installed on 2020-02-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.99-snapd.conf: [inaccessible: [Errno 13] 
Permission denied: '/etc/sudoers.d/99-snapd.conf']

** Tags added: rls-ff-incoming

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

Title:
  snap.seeded.service never finishes loading and blocks multi-
  user.target

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

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

Reply via email to