You are not logged in.
Pages: 1
I was recently messing around with display managers and I disabled the the sddm and getty services and enabled the ly@tty1 service. Now, whenever I boot, it gets stuck at Reached target Graphical Interface with nothing but a blinking cursor. I even tried the Ctrl+Alt+F2 shortcut to try to login. Even then it was just a blinking cursor and I couldn't type anything there. So basically my PC is not usable at the moment and I can't even login.
Last edited by Anshunoob (2026-03-29 15:01:21)
Offline
boot with
systemd.unit=multi-user.targeteven still can't then try Ctrl+Alt+F2 again
Edit:
which should "hopefully" let you login
Last edited by 5hridhyan (2026-03-29 13:25:20)
---
Offline
The line just above the reached target graphical interface one reads : "OK Reached Target Multi-User System." So I think multi-user.target is already in there
Offline
If you're not going to listen to people's advice, why ask for help in the first place?
Offline
You reach the multi-user.target before progressing to the graphical.target and 5hridhyan's suggestion was to skip the latter and stop at the multi-user.target to fix your system from there (by disabling ly)
Edit: F5ck
Last edited by seth (2026-03-29 14:32:43)
Offline
Sorry @Scimmia i didn't mean to offend anyone or anything like that. So I did what 5hridhyan said and it still didn't work.
I am going to describe how I did it to make sure I didn't mess up:
I booted my PC
Pressed E at the boot menu
Typed systemd.unit=multi-user.target at the end of the line and pressed enter.
Offline
Apologies, I should have explained why I suggested systemd.unit=multi-user.target, it's to bypass the broken graphical target entirely. Thanks seth for clarifying.
@OP, if you still can't get to a prompt with that, your best bet is to boot from your install media, arch-chroot in, and re-enable sddm and getty. Once you have a working desktop again, you can troubleshoot why ly is failing (likely a config or dependency issue) (by journal logs & stuff)before trying to switch back...
---
Offline
Got it. Thank you everyone.
Offline
There's probably some issue w/ the framebuffer console then, you can add "nomodeset" to the kernel commandline, too.
Once you've returned to SDDM and can boot please post your complete system journal for the boot:
sudo journalctl -b | nc termbin.com 9999Offline
Turns out im a complete idiot(Not a big surprise). I think what caused the issue was that instead of enabling the service i started it. I booted the live media and did arch chrooted my way in. I enabled the ly@tty1.service and voila. My problem is fixed.
Offline
The logs:
https://termbin.com/g38e
Offline
Pages: 1