snapd taking enormous amount of time to boot

[ventrical]

systemd-analyze blame returns

ventrical@ventrical-MS-7850:~$ systemd-analyze blame
    4min 42.027s snapd.refresh.service
    3min 18.049s apt-daily.service
          8.149s NetworkManager-wait-online.service

This was suppossed to be fixed in ver 2.11

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: snapd 2.22.3+17.04
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Fri Feb 24 23:21:31 2017
InstallationDate: Installed on 2016-10-06 (141 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

[Jeremy Bícha (jbicha)]

I don't even have any snaps installed but snapd appears to delay my boot by 93 seconds.

I am running Ubuntu 17.10 Alpha with snapd 2.26.8+17.10. I have a traditional non-SSD hard drive.

$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2min 505ms
└─multi-user.target @2min 505ms
  └─virtualbox.service @1min 51.341s +959ms
    └─network-online.target @1min 51.325s
      └─NetworkManager-wait-online.service @1min 40.711s +10.613s
        └─NetworkManager.service @1min 35.045s +5.617s
          └─dbus.service @1min 33.323s
            └─basic.target @1min 33.308s
              └─sockets.target @1min 33.307s
                └─snapd.socket @1min 33.295s +12ms
                  └─sysinit.target @1min 33.275s
                    └─apparmor.service @16.480s +1.893s
                      └─local-fs.target @16.443s
                        └─home-jeremy.mount @2min 11.302s
                          └─local-fs-pre.target @9.310s
                            └─systemd-remount-fs.service @9.180s +129ms
                              └─system.slice @3.086s
                                └─-.slice @2.647s

[Jeremy Bícha (jbicha)]

Oh, I guess I read the output wrong, +12ms isn't bad.

[Markus Majer (mpathy)]

This all is still happening:

graphical.target @3min 44.860s
└─multi-user.target @3min 44.859s
  └─snapd.seeded.service @1min 32.298s +42.935s
    └─snapd.service @1min 32.544s +42.687s
      └─basic.target @1.999s
        └─sockets.target @1.999s
          └─snapd.socket @1.998s +837us
            └─sysinit.target @1.993s
              └─systemd-backlight@leds:tpacpi::kbd_backlight.service @2.871s +4ms
                └─system-systemd\x2dbacklight.slice @1.236s
                  └─system.slice @165ms
                    └─-.slice @162ms

    3min 42.346s plymouth-quit-wait.service
         42.935s snapd.seeded.service
         42.687s snapd.service
          6.355s NetworkManager-wait-online.service
          2.822s dev-sda1.device

Also, my simple gnome calculator, which wasnt not installed and now is installed as a snap package, starts so slowly when executing it.

[Ian Johnson (anonymouse67)]

Multiple speedups for snapd seeding have been implemented since this was first filed, can you confirm that you still see slow snapd seeding on boot without any snaps installed on the system?

Also @mpathy, the issue surrounding gnome-calculator being slow to start is a separate issue that has also been worked on and should be much faster (though the first start of the snap will be a bit slow to cache fonts and things). Do you still see a significant slowdown when using the snap? If so please comment on the already filed bug to gnome-calculator here: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734

[Launchpad Janitor (janitor)]

[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]