What about the "once of week" fsck situation? I am getting in that situation quite a lot these days. Even though there is nothing wrong.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1840615 Title: Slow booting, slow start-up & once a week fsck issues in Ubuntu 19.04 Status in network-manager package in Ubuntu: New Bug description: bond@007:~$ 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 24.420s └─multi-user.target @2min 24.419s └─kerneloops.service @2min 9.379s +247ms └─network-online.target @2min 9.354s └─NetworkManager-wait-online.service @1min 40.208s +29.145s └─NetworkManager.service @1min 32.992s +7.213s └─dbus.service @1min 32.963s └─basic.target @1min 32.932s └─sockets.target @1min 32.932s └─snapd.socket @1min 32.900s +29ms └─sysinit.target @1min 32.873s └─apparmor.service @23.447s +2.113s └─local-fs.target @23.445s └─run-user-1000-gvfs.mount @2min 44.750s └─run-user-1000.mount @2min 27.618s └─local-fs-pre.target @4.127s └─systemd-tmpfiles-setup-dev.service @3.653s +473ms └─systemd-sysusers.service @2.988s +663ms └─systemd-remount-fs.service @2.858s +127ms └─systemd-journald.socket @2.855s └─-.mount @2.827s └─systemd-journald.socket @2.855s └─... In pictures: https://imgur.com/CT7s2sI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1840615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
