[SOLVED] Freeze during boot

confuso · 2024-06-22 06:46:14

Hi
Since my last update yesterday, my Arch is not booting completely anymore.
During boot up, log looks fine but is also too fast to really read. A second later, my screen turns black and I only see a frozen _ Cursor on the top left.

I expect it's gnome which is freezing/crashing, since at the beginning everything looks fine.
My problem is, I can't do troubleshooting. Changing shell by pressing Ctrl+alt+fX does not work. Ctrl+alt+del just leads to reboot.

Any idea how I can get out of this frozen screen and open a shell?
Is there a way to use grub parameters to prevent gnome from loading?

Thanks

Confuso

Last edited by confuso (2024-06-26 19:47:55)

seth · 2024-06-22 07:09:30

2nd link below

confuso · 2024-06-22 08:11:11

thanks, but I am afraid that this will not really help me, as I don't get a shell until freeze.. I would need to use a live usb to do, which of course would be an option.

However, meanwhile I found an easier way: Booting with the "single" option, so adding "single" to the kernel load options in grub helped me getting into a rescue shell. I deactivated gdm.service and now can start with the troubleshooting.

seth · 2024-06-22 15:27:51

meanwhile I found an easier way: Booting with the "single" option

Found where? The second link below…? (It's equivalent to "systemd.unit=rescue.target")

Do you know why GDM fails? Otherwise check/post the system journal for a compromised boot, eg.

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous boot ("-1")

confuso · 2024-06-26 19:01:54

Hi
sorry, you are right, haven't read until the end.

I couldn't solve the issue so far.. currently using sddm to launch Gnome, which is working fine.
Here's the log of the attempt to launch GDM. Broke with an recent update: https://0x0.st/XmAR.txt

Still confused about the Xorg failure log... shouldn't GDM use Wayland? /etc/gdm/custom.conf has Wayland enabled.

Thanks

seth · 2024-06-26 19:16:10

Jun 26 20:42:28 Thinkpad systemd-logind[761]: New session 6 of user gdm.
Jun 26 20:42:28 Thinkpad systemd[1]: Created slice User Slice of UID 120.
Jun 26 20:42:28 Thinkpad systemd[1]: Starting User Runtime Directory /run/user/120...
Jun 26 20:42:28 Thinkpad systemd[1]: Finished User Runtime Directory /run/user/120.
Jun 26 20:42:28 Thinkpad systemd[1]: Starting User Manager for UID 120...
Jun 26 20:42:28 Thinkpad (systemd)[17969]: pam_access(systemd-user:account): access denied for user `gdm' from `systemd-user'
Jun 26 20:42:28 Thinkpad (systemd)[17969]: PAM failed: Permission denied
Jun 26 20:42:28 Thinkpad (systemd)[17969]: user@120.service: Failed to set up PAM session: Operation not permitted
Jun 26 20:42:28 Thinkpad (systemd)[17969]: user@120.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Jun 26 20:42:28 Thinkpad systemd[1]: user@120.service: Main process exited, code=exited, status=224/PAM
Jun 26 20:42:28 Thinkpad systemd[1]: user@120.service: Failed with result 'exit-code'.

GDM / X11 is probably a hail-mary, w/ PIDs in the 17000 and 18000 we're long in that boot - god knows what has happened before there.
But it's also in https://bbs.archlinux.org/viewtopic.php?id=297137 so systemd 256 likely broke it.

confuso · 2024-06-26 19:20:10

Thanks for your support. Yes you are right, I didn't reboot before uploading the log, just stopped sddm and started GDM. Failure is the same, however, I can redo it in a fresh boot.

The PAM access denied failure I also recognized, so I guess there is no immediate solution and just hope for a fix?

seth · 2024-06-26 19:25:05

You could check your pacman log to gage whether it was likely the systemd up that broke it and test to downgrade to ther last 255 release.

Then there's probably something common between you and the linked thread and that might hint at the cause (because otherwise there'd probably be more cases)
On a wild guess: I see now systemd-homed spam in the provided excerpt, have you configured that or disabled the pam module?
Do you have a custom /etc/security/access.conf ?

confuso · 2024-06-26 19:43:11

Oh, nice, that's actually the case.

Content of /etc/security/access.conf is

 +:root:LOCAL
-:root:ALL
+:user1:LOCAL
+:user2:LOCAL
+:(wheel):LOCAL
+:(adm):LOCAL
-:ALL:ALL

Changing to

 +:root:LOCAL
-:root:ALL
+:gdm:LOCAL
+:user1:LOCAL
+:user2:LOCAL
+:(wheel):LOCAL
+:(adm):LOCAL
-:ALL:ALL

fixed the issue...

Last edited by confuso (2024-06-26 19:43:33)

seth · 2024-06-26 19:46:18

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

confuso · 2024-06-26 19:47:33

Thanks

Arch Linux

#1 2024-06-22 06:46:14

[SOLVED] Freeze during boot

#2 2024-06-22 07:09:30

Re: [SOLVED] Freeze during boot

#3 2024-06-22 08:11:11

Re: [SOLVED] Freeze during boot

#4 2024-06-22 15:27:51

Re: [SOLVED] Freeze during boot

#5 2024-06-26 19:01:54

Re: [SOLVED] Freeze during boot

#6 2024-06-26 19:16:10

Re: [SOLVED] Freeze during boot

#7 2024-06-26 19:20:10

Re: [SOLVED] Freeze during boot

#8 2024-06-26 19:25:05

Re: [SOLVED] Freeze during boot

#9 2024-06-26 19:43:11

Re: [SOLVED] Freeze during boot

#10 2024-06-26 19:46:18

Re: [SOLVED] Freeze during boot

#11 2024-06-26 19:47:33

Re: [SOLVED] Freeze during boot

Board footer