Slow boot

Support and Help
,
1

Ubuntu Version:
24.04.2 LTS

Problem Description:

I have a few problems after upgrading from 22.04 LTS, but I’m trying to fix one thing at a time. I’ve noticed that my laptop can now take minutes to boot, counting from typing disk encryption key to getting X11 login screen.

Relevant System Information:

  • Lenovo ThinkBook 16p G2 ACH.
  • Hybrid graphics (AMD APU and NVIDIA GeForce RTX 3060).
  • UEFI and encrypted LVM2.
  • Connected to 2 external monitors. Main monitor connects via USB-C to DP cable and has a KVM switch and USB hub, second monitor is connected to first one via MultiStream Transport (MST) and HDMI.

Lenovo does not support Linux in this model and many things (namely power management features) have never worked. That should be fine.

Screenshots or Error Messages:

I’ve noticed these time gaps in dmesg output (if I try to upload entire file, forum software freezes).

[    2.119080] hid-generic 0003:048D:C916.0003: input,hiddev1,hidraw2: USB HID v1.10 Keyboard [ITE Tech. Inc. ITE Device(8296)] on usb-0000:05:00.4-4/input0
[    2.119122] usbcore: registered new interface driver usbhid
[    2.119124] usbhid: USB HID core driver
[   15.230635] PM: Image not found (code -22)
[   15.288591] EXT4-fs (dm-1): mounted filesystem 9f385473-a091-4de5-89ef-7090ae56b495 ro with ordered data mode. Quota mode: none.
[   15.432574] systemd[1]: Inserted module 'autofs4'

[   19.356718] amdgpu 0000:05:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[   19.371250] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[   19.402305] nvidia-uvm: Loaded the UVM driver, major device number 506.
[  110.869127] [drm] DSC precompute is not needed.
[  112.128754] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  112.128759] Bluetooth: BNEP filters: protocol multicast

[  118.484833] Bluetooth: RFCOMM TTY layer initialized
[  118.484848] Bluetooth: RFCOMM socket layer initialized
[  118.484858] Bluetooth: RFCOMM ver 1.11
[  141.283672] systemd-journald[623]: /var/log/journal/fc4aeb2f753e4318a094d1a8bc6e45d6/user-1001.journal: Journal file uses a different sequence number ID, rotating.
[  141.480979] audit: type=1400 audit(1740553099.582:182): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=4297 comm="(onedrive)" requested="userns_create" target="unprivileged_userns"
[  141.481389] audit: type=1400 audit(1740553099.582:183): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=4297 comm="(onedrive)" capability

[  147.267450] kauditd_printk_skb: 42 callbacks suppressed
[  147.267456] audit: type=1107 audit(1740553105.369:234): pid=1560 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.116" pid=4866 label="snap.firefox.firefox" peer_pid=5668 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
[  147.283584] audit: type=1107 audit(1740553105.385:235): pid=1560 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.116" pid=4866 label="snap.firefox.firefox" peer_pid=5668 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
[  369.890541] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[  369.909153] usb 2-2: New USB device found, idVendor=05e3, idProduct=0620, bcdDevice=93.03
[  369.909168] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[  371.707588] hid-generic 0003:1532:00A3.000A: input,hidraw9: USB HID v1.11 Keyboard [Razer Razer Cobra] on usb-0000:05:00.3-2.4/input1
[  371.712195] input: Razer Razer Cobra as /devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb1/1-2/1-2.4/1-2.4:1.2/0003:1532:00A3.000B/input/input31
[  371.781746] hid-generic 0003:1532:00A3.000B: input,hidraw10: USB HID v1.11 Keyboard [Razer Razer Cobra] on usb-0000:05:00.3-2.4/input2
[  414.067976] audit: type=1107 audit(1740553372.169:236): pid=1560 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.164" pid=4866 label="snap.firefox.firefox" peer_pid=9720 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
[  417.666198] loop32: detected capacity change from 0 to 113384

What I’ve Tried:

Nothing yet.

Is there something obvious in my log?

2

Welcome to Ubuntu Discourse :slight_smile:

Please post the output from these 2 commands:
systemd-analyze critical-chain
journalctl -b -2 -xe

3

systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 40.114s
└─multi-user.target @1min 40.113s
  └─docker.service @1min 38.495s +1.618s
    └─containerd.service @1min 37.608s +871ms
      └─network.target @1min 37.598s
        └─NetworkManager.service @1min 36.713s +884ms
          └─dbus.service @1min 36.632s +76ms
            └─basic.target @1min 34.162s
              └─sockets.target @1min 34.162s
                └─cups.socket @1min 36.926s
                  └─sysinit.target @1min 34.132s
                    └─systemd-backlight@backlight:nvidia_0.service @1min 36.661s +22ms
                      └─system-systemd\x2dbacklight.slice @928ms
                        └─system.slice @320ms
                          └─-.slice @320ms

journalctl -b -2 -xe

░░ 
░░ The job identifier is 3399 and the job result is done.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: dev-disk-by\x2duuid-fc1f4f7a\x2df408\x2d4eaa\x2d95f9\x2db131801a279f.swap: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit dev-disk-by\x2duuid-fc1f4f7a\x2df408\x2d4eaa\x2d95f9\x2db131801a279f.swap has successfully entered the 'dead' state.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Deactivated swap dev-disk-by\x2duuid-fc1f4f7a\x2df408\x2d4eaa\x2d95f9\x2db131801a279f.swap - /dev/disk/by-uuid/fc1f4f7a-f408-4eaa->
░░ Subject: A stop job for unit dev-disk-by\x2duuid-fc1f4f7a\x2df408\x2d4eaa\x2d95f9\x2db131801a279f.swap has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit dev-disk-by\x2duuid-fc1f4f7a\x2df408\x2d4eaa\x2d95f9\x2db131801a279f.swap has finished.
░░ 
░░ The job identifier is 3400 and the job result is done.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2draredHUrCpD99pPBpr4sJAyM15YPnidfAr5YJxUqvM09dvrCPcjGyZdjQfkmRHnF.swap: Deactivated successf>
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2draredHUrCpD99pPBpr4sJAyM15YPnidfAr5YJxUqvM09dvrCPcjGyZdjQfkmRHnF.swap has successfully entered the 'dead' state.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Deactivated swap dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2draredHUrCpD99pPBpr4sJAyM15YPnidfAr5YJxUqvM09dvrCPcjGyZdjQfkmRHnF.swap - /d>
░░ Subject: A stop job for unit dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2draredHUrCpD99pPBpr4sJAyM15YPnidfAr5YJxUqvM09dvrCPcjGyZdjQfkmRHnF.swap has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2draredHUrCpD99pPBpr4sJAyM15YPnidfAr5YJxUqvM09dvrCPcjGyZdjQfkmRHnF.swap has finished.
░░ 
░░ The job identifier is 3402 and the job result is done.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: dev-dm\x2d2.swap: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit dev-dm\x2d2.swap has successfully entered the 'dead' state.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Deactivated swap dev-dm\x2d2.swap - /dev/dm-2.
░░ Subject: A stop job for unit dev-dm\x2d2.swap has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit dev-dm\x2d2.swap has finished.
░░ 
░░ The job identifier is 3403 and the job result is done.
Feb 25 13:09:33 payslip-agv-2022 lvm[27660]:   2 logical volume(s) in volume group "vgubuntu" unmonitored
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: dev-mapper-vgubuntu\x2dswap_1.swap: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit dev-mapper-vgubuntu\x2dswap_1.swap has successfully entered the 'dead' state.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Deactivated swap dev-mapper-vgubuntu\x2dswap_1.swap - /dev/mapper/vgubuntu-swap_1.
░░ Subject: A stop job for unit dev-mapper-vgubuntu\x2dswap_1.swap has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit dev-mapper-vgubuntu\x2dswap_1.swap has finished.
░░ 
░░ The job identifier is 3404 and the job result is done.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Reached target umount.target - Unmount All Filesystems.
░░ Subject: A start job for unit umount.target has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit umount.target has finished successfully.
░░ 
░░ The job identifier is 3395.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: lvm2-monitor.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit lvm2-monitor.service has successfully entered the 'dead' state.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
░░ Subject: A stop job for unit lvm2-monitor.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit lvm2-monitor.service has finished.
░░ 
░░ The job identifier is 3354 and the job result is done.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Reached target shutdown.target - System Shutdown.
░░ Subject: A start job for unit shutdown.target has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit shutdown.target has finished successfully.
░░ 
░░ The job identifier is 3168.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Reached target final.target - Late Shutdown Services.
░░ Subject: A start job for unit final.target has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit final.target has finished successfully.
░░ 
░░ The job identifier is 3502.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: systemd-reboot.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit systemd-reboot.service has successfully entered the 'dead' state.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Finished systemd-reboot.service - System Reboot.
░░ Subject: A start job for unit systemd-reboot.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit systemd-reboot.service has finished successfully.
░░ 
░░ The job identifier is 3167.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Reached target reboot.target - System Reboot.
░░ Subject: A start job for unit reboot.target has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit reboot.target has finished successfully.
░░ 
░░ The job identifier is 3166.
Feb 25 13:09:33 payslip-agv-2022 systemd[1]: Shutting down.
Feb 25 13:09:33 payslip-agv-2022 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
Feb 25 13:09:33 payslip-agv-2022 kernel: NVRM: GPU 0000:01:00.0 is already bound to nouveau.
Feb 25 13:09:33 payslip-agv-2022 kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 25 13:09:33 payslip-agv-2022 kernel: NVRM: This can occur when another driver was loaded and 
                                         NVRM: obtained ownership of the NVIDIA device(s).
Feb 25 13:09:33 payslip-agv-2022 kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                         NVRM: reconfigure your kernel without the conflicting
                                         NVRM: driver(s)), then try loading the NVIDIA kernel module
                                         NVRM: again.
Feb 25 13:09:33 payslip-agv-2022 kernel: NVRM: No NVIDIA devices probed.
Feb 25 13:09:33 payslip-agv-2022 systemd-shutdown[1]: Syncing filesystems and block devices.
Feb 25 13:09:33 payslip-agv-2022 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Feb 25 13:09:33 payslip-agv-2022 systemd-journald[915]: Received SIGTERM from PID 1 (systemd-shutdow).
Feb 25 13:09:33 payslip-agv-2022 systemd-journald[915]: Journal stopped
░░ Subject: The journal has been stopped
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The system journal process has shut down and closed all currently
░░ active journal files.
4

The output of systemd-analyze blame might also be interesting to see which services take the longest here …

Seems the critical-chain output only actually starts counting at 1min 40sec, so your system was already slow before getting there … (that first entry in the output should really be around/below 20sec on a decent system)

2 Likes
5

I’m shocked by top two entries…

3min 11.753s plocate-updatedb.service
     17.383s apt-daily-upgrade.service
      3.362s systemd-udev-settle.service
      2.724s accounts-daemon.service
      2.546s avahi-daemon.service
      2.545s bluetooth.service
      2.517s clamav-daemon.service
      2.509s apport.service
      1.618s docker.service
      1.421s snapd.seeded.service
      1.267s snapd.service
      1.123s logrotate.service
      1.107s boot-efi.mount
      1.047s fwupd.service
       884ms NetworkManager.service
       871ms containerd.service
       610ms man-db.service
       253ms gnome-remote-desktop.service
       247ms dpkg-db-backup.service
       247ms iio-sensor-proxy.service
       246ms gpu-manager.service
       243ms user@1001.service
       238ms power-profiles-daemon.service
       237ms polkit.service
       236ms pulseaudio-enable-autospawn.service
       234ms networkd-dispatcher.service
       234ms rsyslog.service
       226ms udisks2.service
       217ms systemd-logind.service
       209ms apport-autoreport.service
       200ms dev-mapper-vgubuntu\x2droot.device
       187ms snapd.apparmor.service
       186ms cups.service
       184ms upower.service
       161ms systemd-udev-trigger.service
       146ms plymouth-quit.service
       128ms systemd-journal-flush.service
       128ms dev-loop0.device
       115ms dev-loop2.device
        94ms fwupd-refresh.service
        91ms update-notifier-download.service
        89ms systemd-udevd.service
        83ms systemd-tmpfiles-setup.service
        79ms systemd-resolved.service
        76ms dbus.service
        67ms systemd-tmpfiles-clean.service
        66ms snap-bare-5.mount
        65ms snap-core-16928.mount
        64ms snap-core-17200.mount
        64ms apparmor.service
        64ms systemd-journald.service
        64ms lvm2-monitor.service
        63ms dev-loop7.device
        62ms snap-core18-2846.mount
        61ms dev-loop4.device
        61ms grub-common.service
        61ms secureboot-db.service
        60ms snap-core20-2434.mount
        59ms snap-core20-2496.mount
        59ms switcheroo-control.service
        58ms snap-core22-1722.mount
        57ms snap-core22-1748.mount
        56ms snap-dbeaver\x2dce-349.mount
        55ms snap-dbeaver\x2dce-354.mount
        54ms snap-firefox-5701.mount
        53ms snap-firefox-5783.mount
        53ms dev-loop6.device
        52ms snap-firmware\x2dupdater-167.mount
        50ms snap-gnome\x2d3\x2d28\x2d1804-194.mount
        50ms systemd-timesyncd.service
        49ms ModemManager.service
        48ms snap-gnome\x2d3\x2d28\x2d1804-198.mount
        47ms dev-loop1.device
        46ms snap-gnome\x2d3\x2d38\x2d2004-140.mount
        45ms snap-gnome\x2d3\x2d38\x2d2004-143.mount
        44ms e2scrub_reap.service
        44ms dev-loop5.device
        44ms plymouth-start.service
        44ms snap-gnome\x2d42\x2d2204-176.mount
        42ms snap-gnome\x2d42\x2d2204-202.mount
        41ms snap-gtk2\x2dcommon\x2dthemes-13.mount
        41ms systemd-rfkill.service
        40ms snap-gtk\x2dcommon\x2dthemes-1534.mount
        39ms keyboard-setup.service
        39ms snap-gtk\x2dcommon\x2dthemes-1535.mount
        38ms snap-icon\x2dtheme\x2dpapirus-154.mount
        38ms colord.service
        36ms snap-icon\x2dtheme\x2dpapirus-160.mount
        35ms snap-kde\x2dframeworks\x2d5\x2d91\x2dqt\x2d5\x2d15\x2d3\x2dcore20-1.mount
        34ms snap-snap\x2dstore-1216.mount
        33ms systemd-modules-load.service
        33ms smartmontools.service
        33ms systemd-fsck@dev-disk-by\x2duuid-294D\x2d514E.service
        33ms snap-snap\x2dstore-1248.mount
        31ms snap-snapd-23258.mount
        31ms dev-loop19.device
        31ms rtkit-daemon.service
        30ms snap-snapd-23545.mount
        29ms snap-snapd\x2ddesktop\x2dintegration-247.mount
        29ms systemd-fsck@dev-disk-by\x2duuid-ea802de8\x2d2534\x2d499a\x2d9ed9\x2d83205fb690ec.service
        28ms dev-loop23.device
        28ms snap-snapd\x2ddesktop\x2dintegration-253.mount
        27ms systemd-cryptsetup@nvme0n1p3_crypt.service
        27ms systemd-remount-fs.service
        25ms var-snap-firefox-common-host\x2dhunspell.mount
        24ms kerneloops.service
        23ms dev-loop20.device
        23ms wpa_supplicant.service
        22ms systemd-backlight@backlight:nvidia_0.service
        22ms dev-loop17.device
        21ms dev-loop25.device
        21ms systemd-binfmt.service
        20ms dev-loop31.device
        19ms dev-loop21.device
        19ms dev-loop30.device
        19ms alsa-restore.service
        19ms systemd-backlight@backlight:amdgpu_bl1.service
        19ms dev-loop27.device
        18ms boot.mount
        18ms dev-loop14.device
        18ms dev-loop29.device
        18ms dev-loop28.device
        17ms grub-initrd-fallback.service
        17ms dev-loop26.device
        17ms clamav-daemon.socket
        17ms dev-loop10.device
        17ms dev-loop24.device
        17ms dev-loop22.device
        16ms dev-loop18.device
        16ms dev-loop16.device
        16ms dev-loop15.device
        16ms dev-loop11.device
        16ms dev-loop9.device
        16ms dev-mapper-vgubuntu\x2dswap_1.swap
        16ms dev-loop8.device
        15ms dev-loop13.device
        15ms dev-loop12.device
        15ms systemd-tmpfiles-setup-dev-early.service
        14ms plymouth-read-write.service
        14ms dev-hugepages.mount
        14ms dev-mqueue.mount
        13ms snap-core18-2855.mount
        13ms sys-kernel-debug.mount
        13ms sys-kernel-tracing.mount
        12ms systemd-sysctl.service
        12ms user-runtime-dir@1001.service
        11ms proc-sys-fs-binfmt_misc.mount
        10ms systemd-random-seed.service
        10ms kmod-static-nodes.service
         9ms modprobe@configfs.service
         8ms systemd-tmpfiles-setup-dev.service
         8ms modprobe@drm.service
         7ms systemd-backlight@leds:platform::kbd_backlight.service
         7ms modprobe@fuse.service
         7ms systemd-update-utmp.service
         6ms systemd-update-utmp-runlevel.service
         6ms systemd-user-sessions.service
         6ms setvtrgb.service
         5ms console-setup.service
         5ms openvpn.service
         5ms modprobe@dm_mod.service
         5ms modprobe@efi_pstore.service
         5ms sys-fs-fuse-connections.mount
         5ms modprobe@loop.service
         4ms ufw.service
         4ms sys-kernel-config.mount
         3ms sddm.service
         2ms docker.socket
       926us snapd.socket
        22us blk-availability.service
6

systemctl status plocate-updatedb shows service as “inactive (dead)”. If I try to restart it, I get:

Failed to allocate directory watch: Too many open files

I can live without this utility so I’ll get rid of it if I don’t find an easy fix.

Edit 1: same thing with apt-daily-upgrade. Now it’s coming to my mind that this error happened to me in the past due to some work tool I use, I need to increase maximum file handle limit, I’m checking old notes.

Edit 2: yes, I’ve found my old custom settings in /etc/sysctl.conf.dpkg-old:

# Fix errors about too many open files
#
# `sysctl fs.inotify.max_user_instances` returns 128 by default
fs.inotify.max_user_instances=1024
1 Like
7

Check out launchpad bug 2042301 for the graphical.target time of 1 min plus. Not clear what the x11 login screen is, the Gnome desktop after selecting an x11 session under the gear icon on the password entry screen?

8

That bug returns a 404, check the bug number?

9

Oops 2042301, a little lisdexic here.

1 Like
10

Weird, once I manage to get to the login screen everything else goes lightning fast.

I don’t know how to interpret that command but, is it possible the culprit is this one?

systemd-backlight@backlight:nvidia_0.service @1min 36.661s +22ms
11

I purged and reinstalled plocate.

systemd-analyze critical-chain

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

graphical.target @7.622s
└─multi-user.target @7.622s
  └─docker.service @5.942s +1.679s
    └─containerd.service @5.105s +825ms
      └─network.target @5.090s
        └─NetworkManager.service @4.194s +896ms
          └─dbus.service @4.116s +69ms
            └─basic.target @4.103s
              └─sockets.target @4.103s
                └─snapd.socket @4.102s +816us
                  └─sysinit.target @4.080s
                    └─systemd-udev-settle.service @662ms +3.417s
                      └─systemd-udev-trigger.service @350ms +159ms
                        └─systemd-udevd-kernel.socket @331ms
                          └─system.slice @304ms
                            └─-.slice @304ms

systemd-analyze blame

3.417s systemd-udev-settle.service
2.163s pulseaudio-enable-autospawn.service
2.019s gpu-manager.service
1.679s docker.service
1.442s snapd.seeded.service
1.281s snapd.service
1.188s plymouth-quit.service
 896ms NetworkManager.service
 825ms containerd.service
 270ms apport.service
 237ms user@1001.service
 222ms dev-mapper-vgubuntu\x2droot.device
 205ms systemd-rfkill.service
 202ms networkd-dispatcher.service
 196ms cups.service
 196ms snapd.apparmor.service
 189ms udisks2.service
 170ms accounts-daemon.service
 169ms upower.service
 159ms systemd-udev-trigger.service
 155ms gnome-remote-desktop.service
 151ms iio-sensor-proxy.service
 145ms dev-loop0.device
 142ms power-profiles-daemon.service
 136ms dev-loop2.device
 132ms polkit.service
 114ms rsyslog.service
 112ms dev-loop7.device
 101ms dev-loop6.device
  94ms dev-loop3.device
  92ms update-notifier-download.service
  90ms systemd-journal-flush.service
  83ms dev-loop4.device
  80ms systemd-resolved.service
  79ms systemd-udevd.service
  79ms systemd-logind.service
  79ms avahi-daemon.service
  77ms bluetooth.service
  71ms ModemManager.service
  71ms lvm2-monitor.service
  71ms dev-loop5.device
  69ms dbus.service
  65ms apparmor.service
  64ms systemd-journald.service
  64ms dev-loop1.device
  61ms snap-bare-5.mount
  60ms snap-core-16928.mount
  59ms snap-core-17200.mount
  58ms snap-core18-2846.mount
  57ms snap-core18-2855.mount
[...]

I think the slow boot is (probably?) solved. Remember I said I have several problems but was trying to focus on one? It’s hard, because they interfere each other. At this point, my machine either boots promptly or doesn’t boot at all. I can’t find the exact pattern, but once it starts showing a blank screen after typing disk password it isn’t going anywhere, no matter how many reboots: I can give it an hour to boot and it won’t show any progress. At that point, I need to do this:

  1. Start in rescue mode.
  2. Switch from NVIDIA Nouveau to Proprietary.
  3. Reboot.
  4. Switch from NVIDIA Proprietary to Nouveau.
  5. Reboot.

Whatever, that’s a different problem and I’d think I’d better head to NVIDIA forums.

12

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.