[SOLVED] Login screen takes too long to appear

[kingocounty]

I'm experiencing the same problem (AMD FX-8350, Samsung SSD, Nvidia graphics) and I found a workaround on Reddit/debian. According to the thread, the problem is linked to low entropy and can be remedied by installing the haveged package. Here's the link to the solution and explanation:

https://www.reddit.com/r/debian/comment ... em/dyj3xhj

[kevinthefixer]

Worked for me too. Many thanks for posting this!

[cgirerd]

That also works for me! Thank you very much for this solution

[lbrunosouzati]

Just confirming the user's response kingocounty really solves the problem I just tested an "apt install haveged" and the boot returned the previous usual speed. (Before installing boot in 24 minutes / after 5s).

[cgirerd]

I've just renamed this thread with a more explicit formulation ("Login screen takes too long to appear"), as other users that have the same problem may not seem directly concerned by this thread regarding its previous name "Debian Stretch - boot problem". For instance, I just found another thread here: http://forums.debian.net/viewtopic.php?f=5&t=137440 to explain the same problem.

[elbraca]

Same issue here. Solved it by installing havehed. Thanks!

Regards.

[debiman]

very glad to see this solved!
a true community effort!

[emariz]

Both of my laptops were affected by this issue, but I think that the symptoms here are worse, for the entire boot sequence is halted. This is, the system cannot perform a complete boot, even after one hour, unless one presses some keys multiple times (around ten times, in my case.)

One laptop is an old Sony Vaio with an Intel Sandy Brige i3 processor and a hard drive, the other one is a more recent ThinkPad E470 with an Intel Kaby Lake i5 processor and an SSD. Both are running Testing.

Installing haveged does seem to have solved to problem on the newer laptop, yet it does not solve it on the old Vaio, which must use the previous kernel (4.15.0-2-amd64 = 4.15.11-1) in order to boot normally.

According to systemd-analyze, the Vaio halts during the "kernel" period of the booting sequence. Unfortunately, the lines visible on the screen are only harmless warnings.

[kevinthefixer]

@emariz, sounds like your Vaio has a different problem. Suggest you start another thread for that one, and keep in mind that you are running Testing.

[smalltimer]

Not sure of the etiquette, but thought I'd report in. Issue solved! Many thanks to kingocounty for pointing out the haveged solution.

[cgirerd]

Just a quick question before I may tag this topic as solved. The solution to our issue was to install haveged. But I wonder if our problem was just a missing package we should have installed, or if it is just a way to fix a real problem with the linux kernel (or whatever). I think we are in the second case, do you agree? If so, there might be a real problem somewhere. I guess it might have been observed by developpers, but maybe we should fill in a bug report? What do you think?

[sunrat]

There was a kernel update today for Stretch. Possibly fixes the problem, I can't confirm though.

[cgirerd]

There was a kernel update today for Stretch. Possibly fixes the problem, I can't confirm though.

I just did the update. I also removed haveged to see if this updated kernel solves our problem. And it looks like it is the case (at least for me). I've rebooted my computer about 20 times on the new kernel and didn't experience any issue.

[Manumerique]

I got the same problem as cgirerd.
Stuck right before login screen, with usual tty1 output.
When logging into tty2, launching x server with startx, I was automatically sent back to tty1 after a few seconds.
Same without GUI, tty2 stops blinking, same issue.
I'm on Debian Testing, I was on kernel 4.15.3, and the problem happend after the 4.16.1 update.
Nevertheless, I tried booting with older kernels (4.15.3, 4.15.2) without success.
I tried installing haveged, without success.
I tried reinstalling gdm3, without success.
I removed gdm3 and installed lightdm instead, and it works !
The problem (at least mine) seems definitely tied to gdm3.
I'm waiting for a patch before switching back to gdm3.

[kingocounty]

The latest kernel update appears to have fixed the issue for me. I've uninstalled haveged and have done a few successful reboots with no wait for gdm.

[lbrunosouzati]

Only confirming, the 05/09/2018 update despite the kernel number being the same the slow screen login problem was solved, even without installing the haveged package I did a clean install with the gnome and the error is no longer detected.

[kevinthefixer]

Latest kernel update fixed me up too, installed the new kernel, uninstalled haveged and boot times are normal, the sun is shining upon the kingdom, the trees are full of fruit and even the birds are singing! Bet you never expected that from a kernel update now did you? But seriously folks, thanks to all who pitched in and got this fixed. This is the way it's supposed to work, maybe we could show this example to the world's politicians?

[kingocounty]

Yes, we came together as a community to break, and then fix, Debian.

Purely said in fun, of course. I have great respect and appreciation for everyone involved in maintaining and furthering Debian. Thanks to all the devs for keeping up this fantastic distribution!

[cgirerd]

I guess this issue is definitely solved for everyone. Thank you for your help and efforts!

[Manumerique]

Problem not solved for me.
Didn't have a kernel update in Debian Testing since 4.16.1.
Tried to remove lightdm and reinstall gdm, with same problems as in my previous post.
Folks, what was the version number of your kernel update ?