Ubuntu 19.04 Desktop:slow boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hello,
I have my ubuntu desktop set to boot text only mode.
it seems a removable hard drive was pplugged into my machine some time ago.
On every boot the boot takes a minute and a half to search to see if that drive is plugged in.
I ran systemd-analyze blame
Below is my output:
37.816s apt-daily.service
2.383s dev-sda4.device
2.381s NetworkManager-
1.198s man-db.service
1.112s dev-loop9.device
1.108s dev-loop8.device
1.098s dev-loop4.device
1.083s dev-loop6.device
1.071s dev-loop10.device
1.057s dev-loop13.device
1.057s dev-loop11.device
1.051s dev-loop7.device
1.051s dev-loop12.device
1.046s dev-loop2.device
1.032s dev-loop14.device
1.024s apt-daily-
1.017s snap-core18-
988ms snap-vice\
983ms snap-gnome\
949ms dev-loop15.device
930ms dev-loop3.device
905ms dev-loop5.device
901ms dev-loop1.device
899ms dev-loop0.device
891ms dev-loop16.device
878ms snap-gnome\
868ms snap-remmina-
855ms snap-gnome\
845ms snap-youtube\
844ms dev-loop17.device
834ms snap-gnome\
824ms snap-gnome\
814ms snap-remmina-
803ms snap-gnome\
798ms snap-gnome\
793ms snap-core-
783ms snap-core-
776ms udisks2.service
773ms snap-gnome\
763ms snap-vice\
753ms snap-gtk\
744ms snap-core-
734ms snap-vice\
733ms snap-gnome\
725ms snap-gtk\
719ms dev-loop18.device
715ms snap-core18-
706ms snap-core18-
695ms snap-gnome\
680ms upower.service
662ms snap-gnome\
646ms dev-loop19.device
643ms snap-gtk\
638ms dev-loop23.device
626ms snap-gnome\
626ms dev-loop26.device
610ms snap-gnome\
596ms dev-loop21.device
589ms dev-loop25.device
587ms dev-loop20.device
583ms dev-loop24.device
528ms logrotate.service
523ms systemd-
496ms dev-loop22.device
491ms dev-loop30.device
490ms dev-loop27.device
487ms dev-loop28.device
433ms networkd-
427ms snapd.service
397ms ModemManager.
382ms snap-gnome\
379ms snap-gnome\
369ms snap-remmina-
362ms snap-gnome\
359ms snap-gnome\
340ms accounts-
307ms systemd-
281ms keyboard-
280ms kmod-static-
261ms dev-hugepages.mount
260ms avahi-daemon.
259ms sys-kernel-
259ms ufw.service
255ms apport-
251ms systemd-
242ms systemd-
232ms systemd-
230ms fwupd.service
206ms apport.service
196ms dev-mqueue.mount
194ms apparmor.service
186ms rsyslog.service
184ms dev-loop29.device
182ms NetworkManager.
181ms systemd-
180ms gdm.service
174ms nmbd.service
164ms smbd.service
164ms wpa_supplicant.
157ms dev-loop32.device
154ms networking.service
142ms thermald.service
137ms virtualbox.service
124ms systemd-
122ms grub-common.service
121ms lm-sensors.service
120ms teamviewerd.service
120ms dev-loop31.device
118ms colord.service
114ms switcheroo-
111ms user@1000.service
108ms systemd-
105ms sys-fs-
102ms sys-kernel-
102ms systemd-
99ms systemd-
97ms swapfile.swap
92ms home-media-
91ms gpu-manager.service
74ms systemd-
73ms systemd-
66ms pppd-dns.service
48ms kerneloops.service
46ms polkit.service
45ms ssh.service
43ms bolt.service
40ms snapd.seeded.
39ms snapd.socket
32ms grub-initrd-
31ms plexmediaserver
31ms systemd-
26ms systemd-
23ms user-runtime-
22ms home-media-
20ms ifupdown-
19ms dns-clean.service
16ms systemd-
15ms plymouth-
13ms systemd-
13ms systemd-
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1821462/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]