Nick Koretsky via tde-users composed on 2023-06-05 08:52 (UTC+0300):
This has nothing to do with TDE. systemd waits/timeouts on mounting something
Those mounts aren't related to whatever's delaying TDM painting the screen: # journalctl -b --no-host | grep -E 'l: Command l|tdm|rinit' 16:44:37 kernel: Command line: root=... noresume preempt=full mitigations=none 16:46:09 display-manager[717]: Starting service tdm 16:48:45 dbus-daemon[616]: [system] Activating service name='org.trinitydesktop.hardwarecontrol' requested by ':1.10' (uid=0 pid=838 comm="/opt/trinity/bin/tdm_greet") (using servicehelper) 16:48:45 org.trinitydesktop.hardwarecontrol[855]: [tde_dbus_hardwarecontrol] Listening... 16:48:45 dbus-daemon[616]: [system] Successfully activated service 'org.trinitydesktop.hardwarecontrol' 16:48:46 org.trinitydesktop.hardwarecontrol[855]: [tde_dbus_hardwarecontrol] Name acquired: :1.11 16:48:47 org.trinitydesktop.hardwarecontrol[855]: [tde_dbus_hardwarecontrol] Name acquired: org.trinitydesktop.hardwarecontrol # Systemd starts TDM @16.46.09, but doesn't finish until 16.48.47, nearly 2.5 minutes later. All mounting that's relevant was already done before 16.46.09: # systemd-analyze critical-chain ... graphical.target @56.424s
I switched default to multi-user.target, and with all non-essential mounts removed from fstab: # systemd-analyze Startup finished in 3.553s (kernel) + 15.260s (initrd) + 1min 23.083s (userspace) = 1min 41.897s multi-user.target reached after 1min 355ms in userspace.
Then I switched default back to graphical.target and rebooted: # systemd-analyze Startup finished in 3.553s (kernel) + 15.337s (initrd) + 1min 17.873s (userspace) = 1min 36.765s graphical.target reached after 53.930s in userspace. Similar delay repeats: Journal start: Jun 06 00:00:39 # journalctl -b --no-host | grep -E 'l: Command l|tdm|rinit' 00:00:39 kernel: Command line: root=... noresume preempt=full mitigations=none 00:01:44 display-manager[639]: Starting service tdm 00:04:20 dbus-daemon[570]: [system] Activating service name='org.trinitydesktop.hardwarecontrol' requested by ':1.7' (uid=0 pid=752 comm="/opt/trinity/bin/tdm_greet") (using servicehelper) 00:04:20 org.trinitydesktop.hardwarecontrol[767]: [tde_dbus_hardwarecontrol] Listening... 00:04:20 dbus-daemon[570]: [system] Successfully activated service 'org.trinitydesktop.hardwarecontrol' 00:04:21 org.trinitydesktop.hardwarecontrol[767]: [tde_dbus_hardwarecontrol] Name acquired: :1.8 00:04:22 org.trinitydesktop.hardwarecontrol[767]: [tde_dbus_hardwarecontrol] Name acquired: org.trinitydesktop.hardwarecontrol # This time it took 00:02:37 to get TDM painted/ready. 5 partitions on sda were referenced in journal, from 00:00:50 through 00:01:30, all done before "Starting service tdm" @ 00:01:44, after last "journald" entry @00:01:27. I've attached the entire journal from the first appearance of tdm, 00:01:44 until 00:04:22, the last. In that period, there's practially nothing besides Trinity, just a few seconds of samba-related things. I booted again after taking the triggers for samba-related things out of fstab. TDM first appeared @00:38:18, and ended @00:41:23, so took 00:03:05 to get from start to ready.