Ubuntu 19.04 Desktop:slow boot

Bug #1821462 reported by Stephen Waines
28
This bug affects 6 people
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-wait-online.service
          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-upgrade.service
          1.017s snap-core18-782.mount
           988ms snap-vice\x2djz-22.mount
           983ms snap-gnome\x2dcalculator-260.mount
           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\x2d3\x2d26\x2d1604-78.mount
           868ms snap-remmina-2831.mount
           855ms snap-gnome\x2dcharacters-139.mount
           845ms snap-youtube\x2ddl\x2dsnap-1.mount
           844ms dev-loop17.device
           834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
           824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount
           814ms snap-remmina-2823.mount
           803ms snap-gnome\x2dclocks-85.mount
           798ms snap-gnome\x2dcharacters-206.mount
           793ms snap-core-6350.mount
           783ms snap-core-6531.mount
           776ms udisks2.service
           773ms snap-gnome\x2dlogs-45.mount
           763ms snap-vice\x2djz-20.mount
           753ms snap-gtk\x2dcommon\x2dthemes-1198.mount
           744ms snap-core-6405.mount
           734ms snap-vice\x2djz-19.mount
           733ms snap-gnome\x2dcharacters-124.mount
           725ms snap-gtk\x2dcommon\x2dthemes-1122.mount
           719ms dev-loop18.device
           715ms snap-core18-731.mount
           706ms snap-core18-719.mount
           695ms snap-gnome\x2dcalculator-238.mount
           680ms upower.service
           662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount
           646ms dev-loop19.device
           643ms snap-gtk\x2dcommon\x2dthemes-818.mount
           638ms dev-loop23.device
           626ms snap-gnome\x2dlogs-57.mount
           626ms dev-loop26.device
           610ms snap-gnome\x2dsystem\x2dmonitor-70.mount
           596ms dev-loop21.device
           589ms dev-loop25.device
           587ms dev-loop20.device
           583ms dev-loop24.device
           528ms logrotate.service
           523ms systemd-journal-flush.service
           496ms dev-loop22.device
           491ms dev-loop30.device
           490ms dev-loop27.device
           487ms dev-loop28.device
           433ms networkd-dispatcher.service
           427ms snapd.service
           397ms ModemManager.service
           382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount
           379ms snap-gnome\x2dcalculator-352.mount
           369ms snap-remmina-2819.mount
           362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount
           359ms snap-gnome\x2dsystem\x2dmonitor-57.mount
           340ms accounts-daemon.service
           307ms systemd-logind.service
           281ms keyboard-setup.service
           280ms kmod-static-nodes.service
           261ms dev-hugepages.mount
           260ms avahi-daemon.service
           259ms sys-kernel-debug.mount
           259ms ufw.service
           255ms apport-autoreport.service
           251ms systemd-udev-trigger.service
           242ms systemd-modules-load.service
           232ms systemd-journald.service
           230ms fwupd.service
           206ms apport.service
           196ms dev-mqueue.mount
           194ms apparmor.service
           186ms rsyslog.service
           184ms dev-loop29.device
           182ms NetworkManager.service
           181ms systemd-remount-fs.service
           180ms gdm.service
           174ms nmbd.service
           164ms smbd.service
           164ms wpa_supplicant.service
           157ms dev-loop32.device
           154ms networking.service
           142ms thermald.service
           137ms virtualbox.service
           124ms systemd-sysusers.service
           122ms grub-common.service
           121ms lm-sensors.service
           120ms teamviewerd.service
           120ms dev-loop31.device
           118ms colord.service
           114ms switcheroo-control.service
           111ms user@1000.service
           108ms systemd-random-seed.service
           105ms sys-fs-fuse-connections.mount
           102ms sys-kernel-config.mount
           102ms systemd-resolved.service
            99ms systemd-sysctl.service
            97ms swapfile.swap
            92ms home-media-video_drive.mount
            91ms gpu-manager.service
            74ms systemd-timesyncd.service
            73ms systemd-udevd.service
            66ms pppd-dns.service
            48ms kerneloops.service
            46ms polkit.service
            45ms ssh.service
            43ms bolt.service
            40ms snapd.seeded.service
            39ms snapd.socket
            32ms grub-initrd-fallback.service
            31ms plexmediaserver.service
            31ms systemd-tmpfiles-setup-dev.service
            26ms systemd-tmpfiles-setup.service
            23ms user-runtime-dir@1000.service
            22ms home-media-Secondary_drive.mount
            20ms ifupdown-pre.service
            19ms dns-clean.service
            16ms systemd-tmpfiles-clean.service
            15ms plymouth-read-write.service
            13ms systemd-user-sessions.service
            13ms systemd-update-utmp.service

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/FindRightPackage. 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.]

tags: added: bot-comment
Revision history for this message
Stephen Waines (stevinski) wrote : Re: [Bug 1821462] Re: Ubuntu 19.04 Desktop:slow boot
Download full text (7.7 KiB)

Hello
I don't know what package census other drives my system information should
provide you with what you need.

On March 23, 2019 4:30:47 PM Ubuntu Foundations Team Bug Bot
<email address hidden> wrote:

> 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/FindRightPackage.
> 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.]
>
> ** Tags added: bot-comment
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821462
>
> Title:
> Ubuntu 19.04 Desktop:slow boot
>
> Status in Ubuntu:
> New
>
> 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-wait-online.service
> 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-upgrade.service
> 1.017s snap-core18-782.mount
> 988ms snap-vice\x2djz-22.mount
> 983ms snap-gnome\x2dcalculator-260.mount
> 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\x2d3\x2d26\x2d1604-78.mount
> 868ms snap-remmina-2831.mount
> 855ms snap-gnome\x2dcharacters-139.mount
> 845ms snap-youtube\x2ddl\x2dsnap-1.mount
> 844ms dev-loop17.device
> 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
> 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount
> 814ms snap-remmina-2823.mount
> 803ms snap-gnome\x2dclocks-85.mount
> 798ms snap-gnome\x2dcharacters-206.mount
> ...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
affects: ubuntu → systemd (Ubuntu)
tags: added: disco
Revision history for this message
Mohamed Amine JALLOULI (jallouli-med-amine) wrote :
Download full text (4.1 KiB)

also my case:

         21.939s plymouth-quit-wait.service
         13.357s NetworkManager-wait-online.service
          3.952s user@1000.service
          1.759s dev-sdb2.device
          1.495s plymouth-read-write.service
          1.035s snapd.service
           789ms dev-loop1.device
           747ms dev-loop2.device
           706ms dev-loop9.device
           703ms dev-loop3.device
           673ms dev-loop8.device
           670ms dev-loop4.device
           642ms dev-loop5.device
           635ms dev-loop6.device
           613ms dev-loop7.device
           605ms dev-loop10.device
           596ms snap-gnome\x2dcalculator-406.mount
           592ms snap-core-6818.mount
           590ms snap-gnome\x2dcharacters-254.mount
           588ms snap-gnome\x2d3\x2d28\x2d1804-31.mount
           522ms systemd-logind.service
           487ms udisks2.service
           484ms fwupd.service
           467ms dev-loop11.device
           419ms networkd-dispatcher.service
           347ms dev-loop0.device
           332ms ModemManager.service
           312ms snap-gnome\x2dsystem\x2dmonitor-77.mount
           303ms snap-gnome\x2dlogs-61.mount
           298ms snap-gtk\x2dcommon\x2dthemes-1198.mount
           293ms snap-gnome\x2dsystem\x2dmonitor-81.mount
           283ms snap-gnome\x2dcharacters-258.mount
           268ms accounts-daemon.service
           218ms systemd-rfkill.service
           203ms snap-core18-941.mount
           190ms upower.service
           178ms snap-core-6673.mount
           172ms NetworkManager.service
           167ms systemd-resolved.service
           161ms systemd-udev-trigger.service
           160ms thermald.service
           154ms grub-common.service
           154ms snap-gnome\x2d3\x2d28\x2d1804-40.mount
           149ms apparmor.service
           133ms avahi-daemon.service
           121ms systemd-timesyncd.service
           113ms systemd-journal-flush.service
           111ms apport.service
           104ms pppd-dns.service
           102ms systemd-backlight@backlight:intel_backlight.service
           102ms switcheroo-control.service
           101ms systemd-backlight@leds:asus::kbd_backlight.service
            96ms gdm.service
            94ms polkit.service
            90ms gpu-manager.service
            87ms bluetooth.service
            86ms wpa_supplicant.service
            83ms systemd-fsck@dev-disk-by\x2duuid-b550cb95\x2d3485\x2d4705\x2d8e99\x2d35d4a8597e15.service
            83ms systemd-journald.service
            83ms keyboard-setup.service
            75ms rsyslog.service
            75ms systemd-fsck@dev-disk-by\x2duuid-AA4F\x2dB4F9.service
            73ms packagekit.service
            71ms systemd-udevd.service
            44ms plymouth-start.service
            40ms systemd-tmpfiles-setup.service
            37ms dev-disk-by\x2duuid-4c770753\x2dfa86\x2d42f1\x2dad92\x2d2c4ea669c27e.swap
            32ms networking.service
            31ms bolt.service
            29ms systemd-modules-load.service
            25ms snapd.seeded.service
            23ms kerneloops.service
            20ms console-setup.service
            20ms systemd-sysctl.service
            19ms boot-efi.mount
         ...

Read more...

Revision history for this message
Jwtiyar Nariman (jwtiyar) wrote :

mine also take too much to boot
https://paste.ubuntu.com/p/nZQf5ySCT5/
And the time system booted up is
https://paste.ubuntu.com/p/BtwVSDCMTH/

and takes more than this time when trying to open firefox or files .

Revision history for this message
RUSTAM HUSSAIN (rustam9091) wrote :

HI
I am also facing a slow boot issue. If I shut down my system, I am unable to start the system. IT takes 1 hour to start but I don't know exactly when it will get start. I do just on and off the system. I am using Ubuntu 19.04 version. can you please help me on the same.

Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Stephen Waines (stevinski) wrote :
Download full text (7.0 KiB)

Hello

Thanks for the email hope you're doing well. Apparently that was a bug in
19.04. I'm on 20.04 and I have exactly no issues.

Thank you for the follow-up.

I actually barely remember reporting this bug.

Steve

On June 30, 2021 6:36:30 p.m. Dan Streetman <email address hidden> wrote:

> please reopen if this is still an issue
>
> ** Changed in: systemd (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821462
>
> Title:
> Ubuntu 19.04 Desktop:slow boot
>
> Status in systemd package in Ubuntu:
> Invalid
>
> 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-wait-online.service
> 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-upgrade.service
> 1.017s snap-core18-782.mount
> 988ms snap-vice\x2djz-22.mount
> 983ms snap-gnome\x2dcalculator-260.mount
> 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\x2d3\x2d26\x2d1604-78.mount
> 868ms snap-remmina-2831.mount
> 855ms snap-gnome\x2dcharacters-139.mount
> 845ms snap-youtube\x2ddl\x2dsnap-1.mount
> 844ms dev-loop17.device
> 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
> 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount
> 814ms snap-remmina-2823.mount
> 803ms snap-gnome\x2dclocks-85.mount
> 798ms snap-gnome\x2dcharacters-206.mount
> 793ms snap-core-6350.mount
> 783ms snap-core-6531.mount
> 776ms udisks2.service
> 773ms snap-gnome\x2dlogs-45.mount
> 763ms snap-vice\x2djz-20.mount
> 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount
> 744ms snap-core-6405.mount
> 734ms snap-vice\x2djz-19.mount
> 733ms snap-gnome\x2dcharacters-124.mount
> 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount
> 719ms dev-loop18.device
> 715ms snap-core18-731.mount
> 706ms snap-core18-719.mount
> 695ms snap-gnome\x2dcalculator-238.mount
> 680ms upower.service
> 662ms snap-gnome\x2...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.