Arch Linux

alexjackson

Member

From: London

Registered: 2018-01-29

Posts: 2

[SOLVED] Boot stalls after 'Reached target Graphical Interface'

Hi,
I rebooted my Arch installation earlier today and, for the first time, my boot stalls on reached target Graphical Interface. I can use my mouse and there is a cursor, I can also use the TTY.

I have checked journalctl, there does not seem to be any errors (although I admit I'm not quite sure what I'm looking for).

I spent the last couple hours googling to try and see if I could find a solution, I noticed in 2018 that people were having this issue when updating an xorg package. I checked my pacman log and I have not updated an xorg package recently.

I am not 100% sure when I rebooted, but I think I upgraded systemd and linux since the last reboot. In any case, they were updated 2 days ago. I have not installed any new packages since the last successful boot.

From the TTY, I have tried to run 'sddm' and this aborts with an error. Although, sddm has not been updated recently.

I would happily paste the output of the log commands; however, I really do not know how to do this as I can't boot. Apologies, I have been using Arch for years but never have I felt more like a noob.

Last edited by alexjackson (2020-04-26 20:20:43)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,381

Re: [SOLVED] Boot stalls after 'Reached target Graphical Interface'

If you can get to a tty you can post logs: https://wiki.archlinux.org/index.php/Li … in_clients at least a

sudo journalctl -b

during a problematic boot would be good.

Last edited by V1del (2020-04-26 20:05:53)

alexjackson

Member

From: London

Registered: 2018-01-29

Posts: 2

Re: [SOLVED] Boot stalls after 'Reached target Graphical Interface'

Thank you for your response V1del, I have now learned how to paste logs from the TTY.

As I was iteratively rolling back the updates over the last 2 days rebooting, I found this was an issue with the upgrade to dhcpcd-9.0.2-1. I rolled it back and I can now boot fine. I then searched for issues with this package and found someone had the same issue: https://bugs.archlinux.org/task/66424. This was wholly unexpected.

Thank you again for your quick response, I have marked the thread solved -- apologies for not rolling back more packages before posting.