[TW] Slow boot once plasma is started

asudem · September 6, 2023, 8:42pm

So I’ve reinstalled my TW and imported my old user’s /home/ partition to see if I could fix some booting issues with my system. To my surprise, they’ve persisted, but having less packages installed cuts down on journal noise.

journalctl log here.

From the time the window with a cursor activates, I get “black screen” for about 30 seconds. After login, a minute or so passes before things like the Application Launcher start or I have the ability to bring up the desktop’s context menu. Applications which autorun will pop up, including “restore applications from last session” prior to the Application Launcher.

I just feel like something is off and I don’t quite know what it is. Any help is greatly appreciated, thanks!

asudem · September 6, 2023, 9:14pm

I find the limited amount of time you are allowed to edit a post here very annoying…

Anyway, for specific times systemd-analyze was used:

Startup finished in 20.266s (firmware) + 1.502s (loader) + 1.556s (kernel) + 5.732s (initrd) + 3min 27.674s (userspace) = 3min 56.732s 
graphical.target reached after 3min 27.627s in userspace.

nrickert · September 6, 2023, 10:00pm

Plasma startup is quite fast here. But that’s because I’m using an SSD (or nvme drive).

My previous desktop also had a slow plasma startup. That was with an encrypted rotating rust drive.

As best I can tell, plasma developers have designed their system with a slow startup but a quick responsive desktop once it is running. So we pay a small penalty during startup but benefit from a more responsive desktop once it is started.

asudem · September 6, 2023, 10:32pm

Perhaps I’m not saying the right thing, maybe I don’t mean “plasma”. It’s true do have a fair amount of drives here, and yes the mounting of said drives does take a while, but prior to adding the drives back into fstab, I also encountered the significant delay.

I should not have to wait 30 seconds from a windowed session to login, and 2 minutes from password entry to be able to click onto the Application Launcher.

EDIT: I’d also like to add that it hasn’t always been like this, even with my drives attached. Between the splash screen of login to the point where I could click on the Application Launcher was typically two to three seconds.

asudem · September 6, 2023, 11:00pm

I’ve just recorded a video of my boot and recorded timestamps to give a better idea of what I’m seeing:

0:00 - Video starts
0:17 - Bios Splash
0:20 - Grub
0:33 - Boot Splash screen is cancelled and I can see the boot log
0:34 - Large drives are attempting to be mounted
1:55 - Greeted with black screen and curseor
2:22 - Finally given user login prompt
2:30 - Login screen is cleared after password entry
2:31 - KDE Splash screen animates
2:38 - KDE Splash screen disappears to show wallpaper
3:59 - Desktop icons appear as well as Application Launcher bar

Historically (in my case), it’s never taken 30 seconds from cursor to get to login screen, nor over a minute after the splash screen disappears to se icons.

If you are saying this is now the normal Plasma tradeoff, I will return to Windows.

asudem · September 6, 2023, 11:16pm

Interestingly, this may be something in my bios, as I booted a much older version of TW on a different drive and experienced similar results. TO have something to compare to, I recorded my much lower specced laptop booting TW:

0:00 - Video starts
0:11 - Bios Splash
0:16 - Grub
0:24 - Boot Splash screen is cancelled and I can see the boot log
0:37 - Greeted with black screen and cursor
0:37 - Login prompt is skipped due to user setting and KDE Splash screen animates
0:39 - KDE Splash screen disappears to show wallpaper
0:40 - Desktop icons appear as well as Application Launcher bar

In less time than it takes for my desktop to get from login to usable desktop, my laptop can cold boot.

asudem · September 6, 2023, 11:55pm

Perhaps something is wrong with my swap partition? That would explain persistence across installs.

rob@DESKTOP-K88HIQO:~> 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 @2min 4.866s
└─multi-user.target @2min 4.866s
  └─power-profiles-daemon.service @34.999s +14ms
    └─basic.target @1.979s
      └─sockets.target @1.978s
        └─pcscd.socket @1.978s
          └─sysinit.target @1.971s
            └─systemd-update-utmp.service @1.946s +25ms
              └─auditd.service @1.868s +76ms
                └─systemd-tmpfiles-setup.service @1.707s +67ms
                  └─local-fs.target @1.705s
                    └─run-user-1000-gvfs.mount @34.892s
                      └─run-user-1000.mount @33.462s
                        └─swap.target @1.190s
                          └─dev-disk-by\x2duuid-334256ae\x2d327d\x2d440d\x2dad50\x2d7cd08272310e.swap @1.134s +30ms
                            └─dev-disk-by\x2duuid-334256ae\x2d327d\x2d440d\x2dad50\x2d7cd08272310e.device @584542y 2w 2d 20h 1min 45.026s +5.636s

I don’t quite know why it thinks my device began booting 584542 years ago, but that just doesn’t seem right…

Disabling the swap partition in fstab resulted in this new, equally confusing systemd-analyze critical-chain

rob@DESKTOP-K88HIQO:~> 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 @2min 4.920s
└─multi-user.target @2min 4.920s
  └─power-profiles-daemon.service @34.765s +15ms
    └─basic.target @1.871s
      └─sockets.target @1.870s
        └─pcscd.socket @1.870s
          └─sysinit.target @1.865s
            └─systemd-update-utmp.service @1.803s +61ms
              └─auditd.service @1.745s +56ms
                └─systemd-tmpfiles-setup.service @1.594s +44ms
                  └─local-fs.target @1.592s
                    └─run-user-1000-gvfs.mount @34.699s
                      └─run-user-1000.mount @33.108s
                        └─swap.target @1.101s
                          └─dev-disk-by\x2ddiskseq-3\x2dpart7.swap @1.088s +9ms
                            └─dev-disk-by\x2ddiskseq-3\x2dpart7.device @584542y 2w 2d 20h 1min 44.985s +5.548s

asudem · September 7, 2023, 12:16am

I appear to be having similar issues as this user, which remains unresolved.

Output of journalctl -b -u init.scope -g Reached -o short-monotonic

[    1.760880] localhost systemd[1]: Reached target System Initialization.
[    1.814870] localhost systemd[1]: Reached target Path Units.
[    1.814992] localhost systemd[1]: Reached target Basic System.
[    1.864912] localhost systemd[1]: Reached target Initrd Root Device.
[    6.146090] localhost systemd[1]: Reached target Preparation for Remote File Systems.
[    6.146112] localhost systemd[1]: Reached target Remote File Systems.
[    6.201166] localhost systemd[1]: Reached target Initrd Root File System.
[    6.207254] localhost systemd[1]: Reached target Initrd File Systems.
[    6.207287] localhost systemd[1]: Reached target Initrd Default Target.
[    6.233376] localhost systemd[1]: Reached target Switch Root.
[    7.345083] localhost systemd[1]: Reached target Preparation for Local File Systems.
[    7.505890] localhost systemd[1]: Reached target Swaps.
[    7.997610] localhost systemd[1]: Reached target Local File Systems.
[    8.270199] localhost systemd[1]: Reached target System Initialization.
[    8.273612] localhost systemd[1]: Reached target Path Units.
[    8.275683] localhost systemd[1]: Reached target Socket Units.
[    8.276127] localhost systemd[1]: Reached target Basic System.
[    8.567203] localhost systemd[1]: Reached target Host and Network Name Lookups.
[    8.567575] localhost systemd[1]: Reached target User and Group Name Lookups.
[    8.573494] localhost systemd[1]: Reached target Bluetooth Support.
[    8.628525] localhost systemd[1]: Reached target Sound Card.
[    8.729031] localhost systemd[1]: Reached target Preparation for Network.
[    9.480992] localhost.localdomain systemd[1]: Reached target Network.
[    9.595577] localhost.localdomain systemd[1]: Reached target System Time Synchronized.
[    9.596907] localhost.localdomain systemd[1]: Reached target Timer Units.
[    9.728468] localhost.localdomain systemd[1]: Reached target Login Prompts.
[  131.324799] DESKTOP-K88HIQO systemd[1]: Reached target Multi-User System.
[  131.324904] DESKTOP-K88HIQO systemd[1]: Reached target Graphical Interface.
[  131.530537] DESKTOP-K88HIQO systemd[1]: Reached target Network is Online.

Lots of dev-tty at the top of the systemd-analyze blame list.

nrickert · September 7, 2023, 12:20am

I don’t think it is the drive mounting. Once you login to Plasma, there are many files on disk that need to be read. That probably includes most of what is in “$HOME/.cache”. The more complex your configuration, the more data there is to read. You may have windows configured to automatically open on login, and those take time.

asudem · September 7, 2023, 12:23am

Prior to reinstallation, I logged into console as root and moved my ~/.config folder to ~/.config-old, so an entirely new config was created. My configuration should not be complex with a fresh install of the operating system.

Also, I just installed BleachBit and cleaned my ~/.cache folder, as the old cache was preventing newly installed packages from appearing in the application launcher.

EDIT: I am on an NVME drive by the way, not SSD or platter disk. There is also nothing configured to automatically open on login, as I explained previously, if there were applications open prior to the reboot, those do appear before the application launcher.

nrickert · September 7, 2023, 12:40am

Then plasma startup should be very quick. I cannot guess what might be causing issues for you.

asudem · September 7, 2023, 12:45am

There shouldn’t be any guessing at all, which is why I have been both posting logs and timestamps.

To humor myself, I created a new user “test” and logged into it at the login prompt. The amount of time it took from the login screen disappearing to the Application Launcher being available was again over a minute.

Logging out from user “test” to log back into my normal user, the time between the login screen disappearing to the Application Launcher showing was probably less than 1/16th of a second, as I have been used to seeing in the past.

karlmistelberger · September 7, 2023, 3:21am

Get rid of full journal and post summary of startup as shown below. Infamous host erlangen boots:

erlangen:~ # journalctl -b -u init.scope -g Reached
Sep 06 15:50:34 erlangen systemd[1]: Reached target System Initialization.
Sep 06 15:50:34 erlangen systemd[1]: Reached target Path Units.
Sep 06 15:50:34 erlangen systemd[1]: Reached target Basic System.
Sep 06 15:50:34 erlangen systemd[1]: Reached target Initrd Root Device.
Sep 06 15:50:37 erlangen systemd[1]: Reached target Preparation for Remote File Systems.
Sep 06 15:50:37 erlangen systemd[1]: Reached target Remote File Systems.
Sep 06 15:50:37 erlangen systemd[1]: Reached target Initrd Root File System.
Sep 06 15:50:37 erlangen systemd[1]: Reached target Initrd File Systems.
Sep 06 15:50:37 erlangen systemd[1]: Reached target Initrd Default Target.
Sep 06 15:50:37 erlangen systemd[1]: Reached target Switch Root.
Sep 06 15:50:38 erlangen systemd[1]: Reached target Preparation for Local File Systems.
Sep 06 15:50:39 erlangen systemd[1]: Reached target Local File Systems.
Sep 06 15:50:39 erlangen systemd[1]: Reached target System Initialization.
Sep 06 15:50:39 erlangen systemd[1]: Reached target Path Units.
Sep 06 15:50:39 erlangen systemd[1]: Reached target Socket Units.
Sep 06 15:50:39 erlangen systemd[1]: Reached target Basic System.
Sep 06 15:50:39 erlangen systemd[1]: Reached target Sound Card.
Sep 06 15:50:40 erlangen systemd[1]: Reached target Network.
Sep 06 15:50:40 erlangen systemd[1]: Reached target Network is Online.
Sep 06 15:50:40 erlangen systemd[1]: Reached target System Time Synchronized.
Sep 06 15:50:40 erlangen systemd[1]: Reached target Timer Units.
Sep 06 15:50:40 erlangen systemd[1]: Reached target Login Prompts.
Sep 06 15:50:46 erlangen systemd[1]: Reached target Multi-User System.
Sep 06 15:50:46 erlangen systemd[1]: Reached target Graphical Interface.
erlangen:~ #

Display manager is ready at 3.3 seconds in userspace:

erlangen:~ # systemd-analyze critical-chain display-manager.service 
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.

display-manager.service +529ms
└─apache2.service @2.750s +33ms
  └─time-sync.target @2.747s
    └─chronyd.service @2.635s +110ms
      └─network.target @2.601s
        └─NetworkManager.service @2.144s +456ms
          └─dbus.service @1.915s +47ms
            └─basic.target @1.912s
              └─sockets.target @1.912s
                └─vsftpd.socket @1.912s
                  └─sysinit.target @1.909s
                    └─systemd-update-utmp.service @1.873s +35ms
                      └─auditd.service @1.829s +43ms
                        └─systemd-tmpfiles-setup.service @1.735s +34ms
                          └─local-fs.target @1.732s
                            └─run-user-1000.mount @2.159s
                              └─local-fs-pre.target @1.064s
                                └─systemd-tmpfiles-setup-dev.service @872ms +67ms
                                  └─kmod-static-nodes.service @540ms +138ms
                                    └─systemd-journald.socket
                                      └─system.slice
                                        └─-.slice
erlangen:~ #

Plasma starts fast:

karl@erlangen:~> journalctl --user -b -g Started
Sep 06 15:51:47 erlangen systemd[1095]: Started D-Bus User Message Bus.
Sep 06 15:51:48 erlangen systemd[1095]: Started Baloo File Indexer Daemon.
Sep 06 15:51:48 erlangen systemd[1095]: Started sandboxed app permission store.
Sep 06 15:51:48 erlangen systemd[1095]: Started flatpak document portal service.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE Config Module Initialization.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE Daemon.
Sep 06 15:51:48 erlangen systemd[1095]: Started User preferences database.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE Global Shortcuts Server.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE Window Manager.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE Session Management Server.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE Plasma Workspace.
Sep 06 15:51:48 erlangen systemd[1095]: Started Proxies GTK DBus menus to a Plasma readable format.
Sep 06 15:51:48 erlangen systemd[1095]: Started Handle legacy xembed system tray icons.
Sep 06 15:51:48 erlangen systemd[1095]: Started KActivityManager Activity manager Service.
Sep 06 15:51:48 erlangen systemd[1095]: Started Xdg Desktop Portal For KDE.
Sep 06 15:51:48 erlangen systemd[1095]: Started KDE PolicyKit Authentication Agent.
Sep 06 15:51:48 erlangen systemd[1095]: Started Powerdevil.
Sep 06 15:51:48 erlangen systemd[1095]: Started Geoclue Demo agent.
Sep 06 15:51:48 erlangen systemd[1095]: Started Accessibility.
Sep 06 15:51:48 erlangen systemd[1095]: Started Set KDE_FULL_SESSION=1.
Sep 06 15:51:48 erlangen systemd[1095]: Started Calendar Reminders.
Sep 06 15:51:48 erlangen systemd[1095]: Started Virtual filesystem service.
Sep 06 15:51:48 erlangen systemd[1095]: Started /usr/bin/kalendarac.
Sep 06 15:51:48 erlangen systemd[1095]: Started KScreen.
Sep 06 15:51:48 erlangen systemd[1095]: Started Portal service (GTK/GNOME implementation).
Sep 06 15:51:48 erlangen systemd[1095]: Started PipeWire Multimedia Service.
Sep 06 15:51:48 erlangen systemd[1095]: Started Multimedia Service Session Manager.
Sep 06 15:51:48 erlangen systemd[1095]: Started Portal service.
Sep 06 15:51:48 erlangen systemd[1095]: Started Firefox - Web Browser.
Sep 06 15:51:49 erlangen systemd[1095]: Started Terminal - Super User Mode.
Sep 06 15:51:49 erlangen systemd[1095]: Started KMail - Mail Client.
Sep 06 15:51:49 erlangen systemd[1095]: Started PipeWire PulseAudio.
karl@erlangen:~>

asudem · September 7, 2023, 3:58am

That was done in post #8, but I will repost output:

rob@DESKTOP-K88HIQO:~> sudo journalctl -b -u init.scope -g Reached
[sudo] password for root: 
Sep 06 12:18:54 localhost systemd[1]: Reached target System Initialization.
Sep 06 12:18:55 localhost systemd[1]: Reached target Path Units.
Sep 06 12:18:55 localhost systemd[1]: Reached target Basic System.
Sep 06 12:18:55 localhost systemd[1]: Reached target Initrd Root Device.
Sep 06 12:18:59 localhost systemd[1]: Reached target Preparation for Remote File Systems.
Sep 06 12:18:59 localhost systemd[1]: Reached target Remote File Systems.
Sep 06 12:18:59 localhost systemd[1]: Reached target Initrd Root File System.
Sep 06 12:18:59 localhost systemd[1]: Reached target Initrd File Systems.
Sep 06 12:18:59 localhost systemd[1]: Reached target Initrd Default Target.
Sep 06 12:18:59 localhost systemd[1]: Reached target Switch Root.
Sep 06 19:19:00 localhost systemd[1]: Reached target Preparation for Local File Systems.
Sep 06 19:19:00 localhost systemd[1]: Reached target Swaps.
Sep 06 19:20:31 localhost systemd[1]: Reached target Local File Systems.
Sep 06 19:20:32 localhost systemd[1]: Reached target System Initialization.
Sep 06 19:20:32 localhost systemd[1]: Reached target Path Units.
Sep 06 19:20:32 localhost systemd[1]: Reached target Socket Units.
Sep 06 19:20:32 localhost systemd[1]: Reached target Basic System.
Sep 06 19:20:32 localhost systemd[1]: Reached target Host and Network Name Lookups.
Sep 06 19:20:32 localhost systemd[1]: Reached target User and Group Name Lookups.
Sep 06 19:20:32 localhost systemd[1]: Reached target Bluetooth Support.
Sep 06 19:20:32 localhost systemd[1]: Reached target Sound Card.
Sep 06 19:20:32 localhost systemd[1]: Reached target Preparation for Network.
Sep 06 19:20:32 localhost.localdomain systemd[1]: Reached target Network.
Sep 06 19:20:33 localhost.localdomain systemd[1]: Reached target System Time Synchronized.
Sep 06 19:20:33 localhost.localdomain systemd[1]: Reached target Timer Units.
Sep 06 19:20:33 localhost.localdomain systemd[1]: Reached target Login Prompts.
Sep 06 19:22:36 DESKTOP-K88HIQO systemd[1]: Reached target Multi-User System.
Sep 06 19:22:36 DESKTOP-K88HIQO systemd[1]: Reached target Graphical Interface.
Sep 06 19:22:36 DESKTOP-K88HIQO systemd[1]: Reached target Network is Online.

Now for systemd-analyze critical-chain display-manager.service

rob@DESKTOP-K88HIQO:~> systemd-analyze critical-chain display-manager.service 
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.

display-manager.service +538ms
└─systemd-user-sessions.service @1min 33.307s +40ms
  └─network.target @1min 33.266s
    └─NetworkManager.service @1min 33.022s +244ms
      └─network-pre.target @1min 32.976s
        └─firewalld.service @1min 32.817s +158ms
          └─polkit.service @1min 32.622s +190ms
            └─basic.target @1min 32.607s
              └─sockets.target @1min 32.607s
                └─pcscd.socket @1min 32.605s
                  └─sysinit.target @1min 32.601s
                    └─systemd-update-utmp.service @1min 32.571s +29ms
                      └─auditd.service @1min 32.506s +38ms
                        └─systemd-tmpfiles-setup.service @1min 32.458s +46ms
                          └─systemd-journal-flush.service @1min 32.223s +174ms
                            └─var.mount @1.200s +1min 30.972s
                              └─dev-nvme0n1p5.device @584542y 2w 2d 20h 1min 44.975s +5.649s

Sep 06 19:21:05 DESKTOP-K88HIQO systemd[1712]: Started Daily Cleanup of User's Temporary Directories.
Sep 06 19:21:05 DESKTOP-K88HIQO systemd[1712]: Started D-Bus User Message Bus.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started sandboxed app permission store.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started flatpak document portal service.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE Config Module Initialization.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Unlock kwallet from pam credentials.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE Daemon.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE Window Manager.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE Global Shortcuts Server.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE Session Management Server.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started User preferences database.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE Plasma Workspace.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Proxies GTK DBus menus to a Plasma readable format.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Handle legacy xembed system tray icons.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KActivityManager Activity manager Service.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Xdg Desktop Portal For KDE.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KDE PolicyKit Authentication Agent.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Virtual filesystem service.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Portal service (GTK/GNOME implementation).
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started PipeWire Multimedia Service.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Multimedia Service Session Manager.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started Portal service.
Sep 06 19:21:06 DESKTOP-K88HIQO systemd[1712]: Started KScreen.
Sep 06 19:21:11 DESKTOP-K88HIQO systemd[1712]: Started Geoclue Demo agent.
Sep 06 19:21:11 DESKTOP-K88HIQO systemd[1712]: Started Accessibility.
Sep 06 19:21:11 DESKTOP-K88HIQO systemd[1712]: Started Set KDE_FULL_SESSION=1.
Sep 06 19:21:11 DESKTOP-K88HIQO systemd[1712]: Started Calendar Reminders.
Sep 06 19:21:11 DESKTOP-K88HIQO systemd[1712]: Started /usr/bin/kalendarac.
Sep 06 19:21:31 DESKTOP-K88HIQO systemd[1712]: Started Powerdevil.
Sep 06 19:21:31 DESKTOP-K88HIQO systemd[1712]: Started PipeWire PulseAudio.

So what’s happening between Sep 06 19:20:33 localhost.localdomain systemd[1]: Reached target Login Prompts. and Sep 06 19:22:36 DESKTOP-K88HIQO systemd[1]: Reached target Multi-User System.?

karlmistelberger · September 7, 2023, 4:14am

Looks like a timeout related to /var:

erlangen:~ # findmnt /var 
TARGET
     SOURCE                 FSTYPE OPTIONS
/var /dev/nvme0n1p2[/@/var] btrfs  rw,relatime,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@/var
erlangen:~ #

Check your drive and filesystem for issues.

asudem · September 7, 2023, 6:33am

rob@DESKTOP-K88HIQO:~> findmnt /var
TARGET
     SOURCE                 FSTYPE OPTIONS
/var /dev/nvme0n1p5[/@/var] btrfs  rw,relatime,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@/var

nvme0n1p5 is the root partition of my linux install, it was before the reinstall too. The partition was deleted and recreated in the new install. Also doesn’t the mounting usually happen before login prompt?

karlmistelberger · September 7, 2023, 8:58am

You may show all mounts. Typical mounts:

erlangen:~ # journalctl -b -u '*.mount' -o short-monotonic
[    6.101157] erlangen systemd[1]: Mounting /sysroot...
[    6.171691] erlangen systemd[1]: Mounted /sysroot.
[    6.222709] erlangen systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully.
[    6.222819] erlangen systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
[    6.238921] erlangen systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount: Deactivated successfully.
[    7.293441] erlangen systemd[1]: Mounting FUSE Control File System...
[    7.293972] erlangen systemd[1]: Mounting Kernel Configuration File System...
[    7.297377] erlangen systemd[1]: Mounted FUSE Control File System.
[    7.297413] erlangen systemd[1]: Mounted Kernel Configuration File System.
[    7.492032] erlangen systemd[1]: Mounting /.snapshots...
[    7.501915] erlangen systemd[1]: Mounting /boot/efi...
[    7.515635] erlangen systemd[1]: Mounting /boot/grub2/i386-pc...
[    7.517722] erlangen systemd[1]: Mounting /boot/grub2/x86_64-efi...
[    7.519407] erlangen systemd[1]: Mounting /home...
[    7.521237] erlangen systemd[1]: Mounting /opt...
[    7.521292] erlangen systemd[1]: root.mount: Directory /root to mount over is not empty, mounting anyway.
[    7.522384] erlangen systemd[1]: Mounting /root...
[    7.523309] erlangen systemd[1]: Mounting /srv...
[    7.524171] erlangen systemd[1]: Mounting /usr/local...
[    7.525019] erlangen systemd[1]: Mounting /var...
[    7.548936] erlangen systemd[1]: Mounted /.snapshots.
[    7.549049] erlangen systemd[1]: Mounted /boot/grub2/i386-pc.
[    7.549121] erlangen systemd[1]: Mounted /boot/grub2/x86_64-efi.
[    7.549175] erlangen systemd[1]: Mounted /home.
[    7.549228] erlangen systemd[1]: Mounted /opt.
[    7.551749] erlangen systemd[1]: Mounted /root.
[    7.551817] erlangen systemd[1]: Mounted /srv.
[    7.551835] erlangen systemd[1]: Mounted /usr/local.
[    7.551852] erlangen systemd[1]: Mounted /var.
[    7.799300] erlangen systemd[1]: Mounted /boot/efi.
[    8.096769] erlangen systemd[1]: Mounting /home-SSD...
[    8.156874] erlangen systemd[1]: Mounted /home-SSD.
[   86.597607] erlangen systemd[1]: run-user-477.mount: Deactivated successfully.
...
erlangen:~ #

asudem · September 7, 2023, 9:36am

[    6.283459] localhost systemd[1]: Mounting /sysroot...
[    6.294019] localhost systemd[1]: Mounted /sysroot.
[    6.310479] localhost systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully.
[    6.310533] localhost systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
[    6.320251] localhost systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount: Deactivated successfully.
[    7.473480] localhost systemd[1]: Mounting FUSE Control File System...
[    7.473957] localhost systemd[1]: Mounting Kernel Configuration File System...
[    7.476544] localhost systemd[1]: Mounted FUSE Control File System.
[    7.476704] localhost systemd[1]: Mounted Kernel Configuration File System.
[    7.730913] localhost systemd[1]: Mounting /.snapshots...
[    7.731440] localhost systemd[1]: Mounting /boot/grub2/i386-pc...
[    7.731916] localhost systemd[1]: Mounting /boot/grub2/x86_64-efi...
[    7.732435] localhost systemd[1]: Mounting /home...
[    7.732925] localhost systemd[1]: Mounting /opt...
[    7.733490] localhost systemd[1]: Mounting /root...
[    7.734425] localhost systemd[1]: Mounting /run/media/rob/FreeSpace...
[    7.734956] localhost systemd[1]: Mounting /run/media/rob/Images...
[    7.735503] localhost systemd[1]: Mounting /run/media/rob/My Book...
[    7.736060] localhost systemd[1]: Mounting /run/media/rob/Seagate Backup Plus Drive...
[    7.736626] localhost systemd[1]: Mounting /run/media/rob/bfd18...
[    7.737195] localhost systemd[1]: Mounting /run/media/rob/bfd20...
[    7.737787] localhost systemd[1]: Mounting /srv...
[    7.738375] localhost systemd[1]: Mounting /usr/local...
[    7.738995] localhost systemd[1]: Mounting /var...
[    7.740561] localhost mount[906]: The disk contains an unclean file system (0, 0).
[    7.740561] localhost mount[906]: Metadata kept in Windows cache, refused to mount.
[    7.740561] localhost mount[906]: Falling back to read-only mount because the NTFS partition is in an
[    7.740561] localhost mount[906]: unsafe state. Please resume and shutdown Windows fully (no hibernation
[    7.740561] localhost mount[906]: or fast restarting.)
[    7.744456] localhost systemd[1]: Mounted /.snapshots.
[    7.744577] localhost systemd[1]: Mounted /boot/grub2/i386-pc.
[    7.744682] localhost systemd[1]: Mounted /boot/grub2/x86_64-efi.
[    7.744783] localhost systemd[1]: Mounted /opt.
[    7.744886] localhost systemd[1]: Mounted /root.
[    7.770111] localhost mount[906]: Could not mount read-write, trying read-only
[    7.771738] localhost ntfs-3g[966]: Version 2022.10.3 external FUSE 29
[    7.771872] localhost ntfs-3g[966]: Mounted /dev/nvme2n1p5 (Read-Only, label "FreeSpace", NTFS 3.1)
[    7.771884] localhost ntfs-3g[966]: Cmdline options: rw
[    7.771897] localhost ntfs-3g[966]: Mount options: allow_other,nonempty,relatime,ro,fsname=/dev/nvme2n1p5,blkdev,blksize=4096
[    7.771908] localhost ntfs-3g[966]: Ownership and permissions disabled, configuration type 7
[    7.774971] localhost mount[913]: The disk contains an unclean file system (0, 0).
[    7.774971] localhost mount[913]: Metadata kept in Windows cache, refused to mount.
[    7.774971] localhost mount[913]: Falling back to read-only mount because the NTFS partition is in an
[    7.774971] localhost mount[913]: unsafe state. Please resume and shutdown Windows fully (no hibernation
[    7.774971] localhost mount[913]: or fast restarting.)
[    7.801455] localhost systemd[1]: Mounted /run/media/rob/FreeSpace.
[    8.012333] localhost systemd[1]: Mounted /home.
[    8.014322] localhost systemd[1]: Mounted /run/media/rob/Images.
[    8.220228] localhost systemd[1]: Mounting /boot/efi...
[    8.221435] localhost systemd[1]: Mounting /run/media/rob/spare8...
[    8.222534] localhost systemd[1]: Mounting Temporary Directory /tmp...
[    8.226426] localhost systemd[1]: Mounted Temporary Directory /tmp.
[    8.233491] localhost systemd[1]: Mounted /boot/efi.
[    8.847806] localhost mount[913]: Could not mount read-write, trying read-only
[    8.857200] localhost ntfs-3g[1042]: Version 2022.10.3 external FUSE 29
[    8.857360] localhost ntfs-3g[1042]: Mounted /dev/sdb2 (Read-Only, label "bfd18", NTFS 3.1)
[    8.857405] localhost ntfs-3g[1042]: Cmdline options: rw
[    8.857427] localhost ntfs-3g[1042]: Mount options: allow_other,nonempty,relatime,ro,fsname=/dev/sdb2,blkdev,blksize=4096
[    8.857448] localhost ntfs-3g[1042]: Ownership and permissions disabled, configuration type 7
[    8.860141] localhost systemd[1]: Mounted /run/media/rob/bfd18.
[    9.195435] localhost ntfs-3g[1044]: Version 2022.10.3 external FUSE 29
[    9.195688] localhost ntfs-3g[1044]: Mounted /dev/sdc1 (Read-Write, label "Seagate Backup Plus Drive", NTFS 3.1)
[    9.195733] localhost ntfs-3g[1044]: Cmdline options: rw
[    9.195756] localhost ntfs-3g[1044]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sdc1,blkdev,blksize=4096
[    9.195782] localhost ntfs-3g[1044]: Ownership and permissions disabled, configuration type 7
[    9.200058] localhost systemd[1]: Mounted /run/media/rob/Seagate Backup Plus Drive.
[    9.382490] localhost ntfs-3g[1047]: Version 2022.10.3 external FUSE 29
[    9.382924] localhost ntfs-3g[1047]: Mounted /dev/sde1 (Read-Write, label "My Book", NTFS 3.1)
[    9.383012] localhost ntfs-3g[1047]: Cmdline options: rw
[    9.383035] localhost ntfs-3g[1047]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sde1,blkdev,blksize=4096
[    9.383051] localhost ntfs-3g[1047]: Ownership and permissions disabled, configuration type 7
[    9.386071] localhost systemd[1]: Mounted /run/media/rob/My Book.
[   11.428769] localhost ntfs-3g[1049]: Version 2022.10.3 external FUSE 29
[   11.429049] localhost ntfs-3g[1049]: Mounted /dev/sdd1 (Read-Write, label "spare8", NTFS 3.1)
[   11.429103] localhost ntfs-3g[1049]: Cmdline options: rw
[   11.429126] localhost ntfs-3g[1049]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sdd1,blkdev,blksize=4096
[   11.429152] localhost ntfs-3g[1049]: Ownership and permissions disabled, configuration type 7
[   11.434590] localhost systemd[1]: Mounted /run/media/rob/spare8.
[   97.740083] localhost systemd[1]: srv.mount: Mounting timed out. Terminating.
[   97.740927] localhost systemd[1]: var.mount: Mounting timed out. Terminating.
[   97.741024] localhost systemd[1]: usr-local.mount: Mounting timed out. Terminating.
[   98.014777] localhost systemd[1]: Mounted /run/media/rob/bfd20.
[   98.015377] localhost systemd[1]: srv.mount: Mount process exited, code=killed, status=15/TERM
[   98.015467] localhost systemd[1]: Mounted /srv.
[   98.015925] localhost systemd[1]: usr-local.mount: Mount process exited, code=killed, status=15/TERM
[   98.016008] localhost systemd[1]: Mounted /usr/local.
[   98.016802] localhost systemd[1]: var.mount: Mount process exited, code=killed, status=15/TERM
[   98.016884] localhost systemd[1]: Mounted /var.
[  147.067315] DESKTOP-K88HIQO systemd[1]: run-user-461.mount: Deactivated successfully.
[  907.640307] DESKTOP-K88HIQO systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.

It’s bfd20 that’s taking all the time, not var. I’ve booted into windows and cleaned the bfd18 volume which was dirty and removed all non-essential mount points from fstab, here is the revised output:

[    6.344530] localhost systemd[1]: Mounting /sysroot...
[    6.355826] localhost systemd[1]: Mounted /sysroot.
[    6.375807] localhost systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully.
[    6.375901] localhost systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
[    6.378921] localhost systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount: Deactivated successfully.
[    7.271190] localhost systemd[1]: Mounted Huge Pages File System.
[    7.271290] localhost systemd[1]: Mounted POSIX Message Queue File System.
[    7.271385] localhost systemd[1]: Mounted Kernel Debug File System.
[    7.271479] localhost systemd[1]: Mounted Kernel Trace File System.
[    7.576766] localhost systemd[1]: Mounting FUSE Control File System...
[    7.577428] localhost systemd[1]: Mounting Kernel Configuration File System...
[    7.580124] localhost systemd[1]: Mounted FUSE Control File System.
[    7.580293] localhost systemd[1]: Mounted Kernel Configuration File System.
[    7.907227] localhost systemd[1]: Mounting /.snapshots...
[    7.907542] localhost systemd[1]: Mounting /boot/grub2/i386-pc...
[    7.908035] localhost systemd[1]: Mounting /boot/grub2/x86_64-efi...
[    7.908643] localhost systemd[1]: Mounting /home...
[    7.909179] localhost systemd[1]: Mounting /opt...
[    7.909648] localhost systemd[1]: Mounting /root...
[    7.910249] localhost systemd[1]: Mounting /srv...
[    7.910750] localhost systemd[1]: Mounting /usr/local...
[    7.911284] localhost systemd[1]: Mounting /var...
[    7.916535] localhost systemd[1]: Mounted /.snapshots.
[    7.916643] localhost systemd[1]: Mounted /boot/grub2/i386-pc.
[    7.916764] localhost systemd[1]: Mounted /boot/grub2/x86_64-efi.
[    7.916865] localhost systemd[1]: Mounted /opt.
[    7.916964] localhost systemd[1]: Mounted /root.
[    7.917062] localhost systemd[1]: Mounted /srv.
[    7.917163] localhost systemd[1]: Mounted /usr/local.
[    7.917272] localhost systemd[1]: Mounted /var.
[    7.920356] localhost systemd[1]: Mounting Temporary Directory /tmp...
[    7.923128] localhost systemd[1]: Mounted Temporary Directory /tmp.
[    8.181730] localhost systemd[1]: Mounted /home.
[    8.298013] localhost systemd[1]: Mounting /boot/efi...
[    8.308156] localhost systemd[1]: Mounted /boot/efi.
[   50.108825] DESKTOP-K88HIQO systemd[1]: run-user-461.mount: Deactivated successfully.

var unsuprisingly gets mounted much faster, and this also unsurprisingly, does not fix my graphical desktop issue which occurs after all mountpoints are mounted.

karlmistelberger · September 7, 2023, 9:49am

Which issue? Your conclusions won’t help much. You need to provide factual information. Show again journalctl --user -b -g Started.

asudem · September 7, 2023, 10:13am

Please reread the original post:

My conclusion is based on factual information. All drives are mounted before the KDE login prompt. There is nothing ambiguous about that. My ability to have to sit and wait for over a minute after the login screen before I can interact with the desktop is a fact. The fact that creating a new user and logging in as that does not reduce the time I can interact with the desktop is a fact. The fact I can logout and login to begin instantly interacting with the desktop is a fact. I am providing as much logging as I can, all which are factual about my system, but if you need to see it again, here you are:

Sep 07 02:43:02 DESKTOP-K88HIQO systemd[1812]: Started Daily Cleanup of User's Temporary Directories.
Sep 07 02:43:02 DESKTOP-K88HIQO systemd[1812]: Started D-Bus User Message Bus.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started sandboxed app permission store.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started flatpak document portal service.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE Config Module Initialization.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Unlock kwallet from pam credentials.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE Daemon.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE Global Shortcuts Server.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE Window Manager.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE Session Management Server.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started User preferences database.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE Plasma Workspace.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Proxies GTK DBus menus to a Plasma readable format.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Handle legacy xembed system tray icons.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KActivityManager Activity manager Service.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KDE PolicyKit Authentication Agent.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Xdg Desktop Portal For KDE.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Virtual filesystem service.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Portal service (GTK/GNOME implementation).
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started PipeWire Multimedia Service.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Multimedia Service Session Manager.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started Portal service.
Sep 07 02:43:03 DESKTOP-K88HIQO systemd[1812]: Started KScreen.
Sep 07 02:43:08 DESKTOP-K88HIQO systemd[1812]: Started Geoclue Demo agent.
Sep 07 02:43:08 DESKTOP-K88HIQO systemd[1812]: Started Accessibility.
Sep 07 02:43:08 DESKTOP-K88HIQO systemd[1812]: Started Set KDE_FULL_SESSION=1.
Sep 07 02:43:08 DESKTOP-K88HIQO systemd[1812]: Started Calendar Reminders.
Sep 07 02:43:08 DESKTOP-K88HIQO systemd[1812]: Started /usr/bin/kalendarac.
Sep 07 02:43:28 DESKTOP-K88HIQO systemd[1812]: Started Powerdevil.
Sep 07 02:43:28 DESKTOP-K88HIQO systemd[1812]: Started PipeWire PulseAudio.
Sep 07 02:46:44 DESKTOP-K88HIQO systemd[1812]: Started Firefox - Web Browser.
Sep 07 02:46:45 DESKTOP-K88HIQO systemd[1812]: Started Konsole - Terminal.
Sep 07 02:47:10 DESKTOP-K88HIQO systemd[1812]: Started LibreOffice Calc - Spreadsheet.
Sep 07 02:47:46 DESKTOP-K88HIQO systemd[1812]: Started Discord - Internet Messenger.
Sep 07 02:47:46 DESKTOP-K88HIQO systemd[1812]: Started flatpak session helper.
Sep 07 02:47:46 DESKTOP-K88HIQO systemd[1812]: Started app-flatpak-com.discordapp.Discord-3143.scope.
Sep 07 02:47:47 DESKTOP-K88HIQO systemd[1812]: Started flatpak portal.
Sep 07 02:47:47 DESKTOP-K88HIQO systemd[1812]: Started app-flatpak-com.discordapp.Discord-3186.scope.
Sep 07 02:48:57 DESKTOP-K88HIQO systemd[1812]: Started Virtual filesystem metadata service.
Sep 07 03:07:47 DESKTOP-K88HIQO sudo[8118]:      rob : TTY=pts/2 ; PWD=/home/rob ; USER=root ; COMMAND=/usr/bin/journalctl --user -b -g Started.
Sep 07 03:07:58 DESKTOP-K88HIQO sudo[8129]:      rob : TTY=pts/2 ; PWD=/home/rob ; USER=root ; COMMAND=/usr/bin/journalctl --user -b -g Started.
Sep 07 03:08:00 DESKTOP-K88HIQO systemd[1812]: Started Dolphin - File Manager.

Something is happening between Pipewire and Firefox.