You are not logged in.
Hello,
I'm getting weird behaviour of gdm, when I let it start automatically via "systemctl enable". At the moment where you'd expect to see login screen, I'm stuck with black screen instead. That would stay apparently forever (I waited about 5 minutes or so, just to check), or until I move my finger on touchpad (can't be sure if that's registered as a movement or a click). Then, after 5 seconds or so a cursor appears, and after another few seconds the login screen pops up.
If I disable gdm autostart, and start it manually via "systemctl start", then everything is ok. Usual, expected behaviour.
Not a deal-breaker, just annoying.
Any ideas where to start looking?
Last edited by melandrien (2019-07-20 16:55:05)
Offline
There's a problem where the random number generator of the kernel takes a long time to initialize at boot. I don't know how GDM works, but the random number thing is the problem for other display managers hanging at boot. You can check on it by doing "journalctl -b" and searching for a message about "random: crng" (type "/random: crng<Enter>" to search).
If you find out that it's taking a long time for the "random: crng init done" message to show up, then you can fix that problem by installing either "haveged" or "rng-tools" (only one of them, not both), and enabling the service in those packages (see the ArchWiki articles about them for instructions). Or, if you want to make the kernel trust the RNG that's built into the CPU, you can add a parameter "random.trust_cpu=on" to your boot loader's kernel command line config.
Last edited by Ropid (2019-07-20 13:50:29)
Offline
Problem solved, thanks for the in-depth reply!!
Every day something new...
Offline