Long time before login screen appears

[Watermann]

After the latest security updates it takes a very very long time before the login screen appears and I can login with no problems.
Am I the only one facing this? If so, what can I do to solve it?

[oshunluvr]

Try opening Konsole and entering:

sudo systemd-analyze critical-chain

This should show you what's taking a long time to finish.

As usual, the Arch Wiki has info: https://wiki.archlinux.org/title/Imp...e/Boot_process

[Watermann]

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 30.709s
└─multi-user.target @1min 30.709s
└─kerneloops.service @1min 30.684s +24ms
└─network-online.target @1min 30.672s
└─NetworkManager-wait-online.service @1min 25.623s +5.048s
└─NetworkManager.service @1min 25.021s +591ms
└─dbus.service @1min 24.934s +74ms
└─basic.target @1min 24.921s
└─sockets.target @1min 24.921s
└─snapd.socket @1min 24.913s +7ms
└─sysinit.target @1min 24.904s
└─systemd-udev-settle.service @417ms +1min 24.485s
└─systemd-udev-trigger.service @328ms +86ms
└─systemd-udevd-kernel.socket @311ms
└─system.slice @298ms
└─-.slice @298ms

Cannot interpret this because I cannot compare this with the figures before the update..

[skyfishgoo]

this is your problem systemd-udev-settle.service @417ms +1min 24.485s

that's an outlandish time to complete, the rest looks comparatively normal to mine

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 @12.180s
└─multi-user.target @12.180s
└─kerneloops.service @12.149s +29ms
└─network-online.target @12.108s
└─NetworkManager-wait-online.service @6.114s +5.993s
└─NetworkManager.service @5.331s +780ms
└─dbus.service @5.284s +42ms
└─basic.target @5.276s
└─sockets.target @5.276s
└─libvirtd-ro.socket @5.276s
└─libvirtd.socket @5.272s +3ms
└─sysinit.target @5.265s
└─systemd-udev-settle.service @639ms +4.615s
└─systemd-udev-trigger.service @315ms +99ms
└─systemd-udevd-kernel.socket @302ms
└─system.slice @286ms
└─-.slice @286ms

[oshunluvr]

You didn't describe your system specs but here's mine for comparison:

graphical.target @9.852s
 └─lactd.service @9.852s
  └─multi-user.target @9.851s
   └─webmin.service @7.682s +2.167s
    └─network-online.target @7.662s
     └─NetworkManager-wait-online.service @3.882s +3.780s
      └─basic.target @3.121s
       └─sockets.target @3.121s
        └─libvirtd-ro.socket @3.121s
         └─libvirtd.socket @3.115s +4ms
          └─sysinit.target @3.092s
           └─systemd-resolved.service @1.499s +1.593s
            └─systemd-tmpfiles-setup.service @1.468s +25ms
             └─local-fs.target @1.462s
              └─tmp.mount @1.455s +6ms
               └─swap.target @640ms
                └─dev-disk-by\x2duuid-1ae06117\x2d4c44\x2d450c\x2db3e5\x2dceefa4de0d86.swap @616ms +10ms
                 └─dev-disk-by\x2duuid-1ae06117\x2d4c44\x2d450c\x2db3e5\x2dceefa4de0d86.device @516ms​

So maybe your PC is just a little slow? My specs are in my sig...

[oshunluvr]

Apparently, this service is not recommended by Arch. It's not running on my machine - KDEneon.

https://man.archlinux.org/man/core/s...e.service.8.en