On a new installation of 15.2 on a i9-10900k dual monitor system using kernel 64 5.3.18-lp152.57.1 (using nvidia drivers 390.138-lp152.33.1 for a GTX 1080 Ti), I have encountered a delay problem that I can’t seem to isolate. The symptoms are:
Power on to solicitation of user id and password is less that 10 seconds
From entering password to presentation of desktop is 90 seconds
What? Looking in the systemd journal, /var/log/messages, /var/log/boot.log, and the X log, I can find no problems. The display does exhibit some unusual behavior during the delay: each screen goes all black at different times only to return to the login solicitation, the KDE logo is displayed briefly, then the normal desktop is presented. From this time forward, all functions are normal and the system performs perfectly. This behavior was not observer on 15.1. Any help on how to fix this problem, monitor it during the 90 second delay, or where to look for log information would be greatly appreciated. Thank you…
(I have tried disabling all autostarts, removing non-essentials in fstab, changing/removing all themes, and disabling all network connections. All to no effect whatsoever.)
Blame is for pre-login OP indicates problem after login before desktop. May have to do with video drivers since he uses multiple monitors.
does problem happen if you log out then back in??? Does it happen with a different user???
I agree that the problem is after logon. Logoff/logon yields a repeat of the same problem. Other users see the same behavior. I can’t seem to find any logs or other records or displays (like ESC during boot) of what occurs between logon and desktop. I really appreciate any help here…
As gogalthorp mentioned, blame isn’t showing anything after login. I asked for it because I’ve had issues when it took forever the system to be ready after login and the issue was due to fstrim trimming for >~15 minutes on each boot.
How did you install the Nvidia driver? 390 is rather old for the 1080Ti I think.
From the top post I see your machine has one of the lastest and greatest Intel processors. But your output of systemd-analyze blame shows really abysmal performance. Compare your output to the following:
**3400G:~ #** 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 @1.688s
└─**display-manager.service @1.008s +679ms**
└─**apache2.service @906ms +101ms**
└─time-sync.target @898ms
└─**chronyd.service @860ms +37ms**
└─nss-lookup.target @859ms
└─**systemd-resolved.service @673ms +184ms**
└─**systemd-tmpfiles-setup.service @652ms +19ms**
└─**systemd-journal-flush.service @263ms +388ms**
└─**var.mount @255ms +6ms**
└─local-fs-pre.target @246ms
└─**systemd-tmpfiles-setup-dev.service @234ms +11ms**
└─**kmod-static-nodes.service @215ms +9ms**
└─systemd-journald.socket
└─-.mount
└─system.slice
└─-.slice
**3400G:~ #**
The confusing thing is that the time from power-on to solicitation for login credentials is normal, but from login enter to desktop presentation is 90 seconds. Investigating what is going on during that delay is what I can’t find any information or tools for…
On login the splash starts, then the login sound plays then apps are started and display if I logged out on the virtual desktop that holds them but no wallpaper or taskbar. I can use any apps that are visible, switch between windows but if I minimise they vanish.
Eventually the wallpaper/desktop displays as does the taskbar and it works fine going on. If I logout and back in it can startup quickly as expected.
I start kmail, konversation, kleopatra and amarok/clementine at login (or rather they get started as shutdown with them running.
I point wallpaper slideshow to my whole photo selection which is pretty big, maybe it’s that. They are on NTFS partition shared with Windows. (Would be nicer if Windows could work with Linux partitions.)
Some of these are set so some groups can write to them. Seems to work fine and hasn’t caused any issues until upgrade to 15.2 so maybe non-relevant. Would be nicer if Windows could mount/read/write to Linux partitions but there you go.