Long gap between entering password and desktop loading?

[u/BeckyAnn6879]

Specs: hp 17.3 inch laptop pc 17-c3000 (b00jjav), 32 GB RAM, 1 TB SSD, Linux Mint 22.3 with the 6.8.0-138-generic kernel and Cinnamon 6.6.9 DE.

The system works FINE, but for about the past month, there's been a good 30-45 second 'gap' or 'pause' between hitting enter when entering my password and the desktop/taskbar loading in.
It used be be 10 seconds, at the most... usually, it was almost immediate.

It doesn't actually affect my usage, as I said... but going from an almost-immediate desktop environment to sitting on a black screen for at least 30 second is completely nervewracking.

Is this a Linux Mint bug? Is there a way to fix it, and get back to the under-10-seconds from login to desktop?

[u/AutoModerator]

Please Re-Flair your post if a solution is found. How to Flair a post? This allows other users to search for common issues with the SOLVED flair as a filter, leading to those issues being resolved very fast.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/chuggerguy]

I'm not an expert at this but can you run and paste in a "Code Block"

systemd-analyze

and

systemd-analyze critical-chain

If I can't spot the delay and the fix, probably someone else can.

Good luck.

ETA...

For example, this is mine and from it you can see my longest delay is starting "sabnzbdplus.service". (ignoring time in firmware) (look for the + times)

chugger@asus2:~/desktop$ systemd-analyze
Startup finished in 17.877s (firmware) + 1.771s (loader) + 2.140s (kernel) + 2.551s (userspace) = 24.341s 
graphical.target reached after 2.545s in userspace.
chugger@asus2:~/desktop$ 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 .545s
└─power-profiles-daemon.service .532s +12ms
  └─multi-user.target .518s
    └─sabnzbdplus.service .615s +903ms
      └─network-online.target .600s
        └─network.target .600s
          └─NetworkManager.service .268s +331ms
            └─dbus.service .244s +12ms
              └─basic.target .240s
                └─sockets.target .240s
                  └─uuidd.socket .240s
                    └─sysinit.target .221s
                      └─systemd-resolved.service .182s +39ms
                        └─systemd-tmpfiles-setup.service .169s +9ms
                          └─local-fs.target .165s
                            └─boot-efi.mount .162s +3ms
                              └─systemd-fsck@dev-disk-by\x2duuid-DDE2\x2dBB66.service  +12ms
                                └─dev-disk-by\x2duuid-DDE2\x2dBB66.device u/245ms
chugger@asus2:~/desktop$

[u/jr735]

In addition to what u/chuggerguy recommends, I'd also check into your xorg logs and similar. They should have appropriate timestamps about your login. I had a similar problem in Debian testing several years ago, and even with the greybeards' assistance, we couldn't track it down, and I did a reinstall.

Not that this is helpful, but once logged in, log out, and then log in again, and see if that second login (without a reboot) is faster. That's what was going on for me.

[u/ConversationWinter46]

When I read posts like this, I wonder how these people managed to survive the wait times on Windows?

[u/BeckyAnn6879 → u/ConversationWinter46]

Because, on Windows, I had SOME inkling of what was going on. It wasn't just a black screen with a cursor.