I mounted a graphics card and it would show a message about waiting for lightdm service to come up, which it never did. (this is all fine, regarding this issue). What isn't is that I could not switch to TTY2 to understand what had failed since whenever I'd switch to another TTY it would revert back to TTY after 1 or 2 seconds.
Steps to reproduce
Change Xorg config to something that crashes.
Try to start the system
Expected behavior
I'd be able to switch to other TTYs even when lightdm fails to start
Actual behavior
can't switch
Extra Information
After much effort I was able to overcome this annoying switching, but logging in to tty2 through multiple switching attempts and kill the lightdm service (sudo systemctl stop lightdm).
After that the switching thing stopped. I then inspected the lightdm error log and it pointed to an Xserver crashing. So I guess what's happening here is that lightdm forcefully tries to restart the Xserver without success in a loop to eternity and that somehow messes with the TTYs (maybe by tring to open a session in "tty7", failing and reverting back to tty1).
I had a similar issue, booting with the parameter option systemd.unit=multi-user.target solved it for me, booted me into a tty shell without trying to start lightdm.
Qubes OS release
4.2-rc4
Brief summary
I mounted a graphics card and it would show a message about waiting for lightdm service to come up, which it never did. (this is all fine, regarding this issue). What isn't is that I could not switch to TTY2 to understand what had failed since whenever I'd switch to another TTY it would revert back to TTY after 1 or 2 seconds.
Steps to reproduce
Expected behavior
I'd be able to switch to other TTYs even when lightdm fails to start
Actual behavior
can't switch
Extra Information
After much effort I was able to overcome this annoying switching, but logging in to tty2 through multiple switching attempts and kill the lightdm service (
sudo systemctl stop lightdm
). After that the switching thing stopped. I then inspected the lightdm error log and it pointed to an Xserver crashing. So I guess what's happening here is that lightdm forcefully tries to restart the Xserver without success in a loop to eternity and that somehow messes with the TTYs (maybe by tring to open a session in "tty7", failing and reverting back to tty1).