You are not logged in.
Not every time I booted, but most times, I would get this scenario while booting, after my GRUB bootmanager menu, and the restart counter would progress to 5 and then time out;
Jun 29 10:32:22 yoda systemd[1]: Starting Light Display Manager...
Jun 29 10:32:22 yoda systemd[1]: Started Light Display Manager.
Jun 29 10:32:22 yoda systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 10:32:22 yoda systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jun 29 10:32:23 yoda systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Jun 29 10:32:23 yoda systemd[1]: Stopped Light Display Manager.Sometimes <Ctrl+Alt+Del> would make it reboot successfully, other times it would not. But one thing that succeeded every time was opening another TTY and logging in via CLI and then simply doing a
sudo systemctl restart lightdmThis started intermittently happening after I upgraded my GPU from an RX470 to an RX6700XT, which is a substantial jump in speed. I did a standard Pacman system update and checked my journalctl -xeb and cat /var/log/lightdm/lightdm.log and got the suspicion that my system was booting too quickly for lightdm and that the display server wasn't fully initialised before lightdm was trying to run.
I was almost about to switch Display Manager when I came across this parameter for the lightdm configuration file /etc/lightdm/lightdm.conf after searching through these forums and consulting the wiki;
[LightDM]
logind-check-graphical=truehttps://wiki.archlinux.org/title/LightDM
This fixed my issue and it has been perfect ever since, so I just wanted to share what I found.
Last edited by coxe87b (2022-07-04 01:39:48)
Desktop: Dual boot {Arch & Windows 11} | Hyprland | AMD Ryzen 5700X | 32GB DDR4 | AMD Radeon RX 6700XT | Dual display DP-1 & DP-2=2560x1440
Laptop: Triple boot {Arch & Mint & Windows 11} | Dell Latitude 5420 | Intel Core i5-1145G7 | 16GB DDR4 | Iris Xe GPU | eDP-1=1920x1080
~ Do or do not, there is no try ~
Offline