After updating yesterday (12/23/2024), system gets stuck repeatedly starting Light Display Manager

Updated my computer yesterday and shut it down. This morning when I tried to boot it up I couldn’t even reach the login screen - the system seemed to get stuck starting the Light Display Manager over and over.

This seems to happen whether I boot in 6.12.6-arch1-1, 6.6.67-1-lts, or their fallback versions.

What can I do to fix this?


Edit: tried again and this time waited. Now I’m stuck on this.

Did you get a lightdm or X11 update yesterday (I don’t have either installed)?

Maybe? I don’t remember…

And if that were the problem, how can I revert the update?

It depends, if you have snapshots setup or if you still have previous versions in your cache, etc.
I’ve never had to do it. I would usually simply update again and typically problems like this would be solved by the next day.

I don’t have anything like that, I don’t think - and even if I did, I can’t even access the login screen when the computer’s like this, let alone update or revert to a snapshot.

Search for ‘arch-chroot’ and you may learn a solution.

So I dug into some of my old flash drives and discovered that if I plug in my old installation media of xubuntu, I can access my file system. Is there a way I can revert the update to ldm that way?

As said above, search for “arch-chroot”: https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

So, to answer your question:

Yes, but best to use an EndeavourOS or Arch-based ISO.

And maybe you might want to try another dm, I find (opinion again) lightdm prone to issues. Sddm seems to have less (for me at least).

Ok, I’m trying to create an EndeavourOS usb flash drive to do arch-chroot in but I’m having a problem getting the boot media to be recognized.
The boot drive for Xubuntu works fine by me.
I used Balena Etcher to flash the EndeavourOS iso file onto a different flash drive but it doesn’t show up during startup.
Should I be using some other program to flash EndeavourOS onto the flash drive, or is there something else I should be doing?

Edit: I’ve got Safe Boot disabled in my BIOS.

Another thread complained about issues with Balena today. You might go look there. Right off, I don’t remember the title.
Found it:

Ok, I’ve tried balena, disk image writer, and dd, but none of them seem to be being picked up by my laptop.

I’m starting to consider just installing Xubuntu for the time being while I try to get things working here…

If that’s the case, I would suspect some sort of hardware issue or corrupted file.
Like I said, dd doesn’t fail, unless you remove it before the write is completed.
I typically use a ‘sync’ command to ensure before undocking or rebooting after an operation to a USB drive.

What does the command look like usually? I might give it a try one more time before I go to Xubuntu…

sync

It may be the ISO itself with the issue. You could maybe download a previous ISO instead, since you’re just gonna use arch-chroot, not actually install it.

If you can’t find a previous EndeavourOS ISO, you can try another Arch-based distro’s ISO.

That’s possible, can’t say I’ve arch-chroot’d for several months ;0

Well, you’ve got a wiki to read, so no need to memorise how to do it. :wink:

Downloading a PDF/HTML/Markdown copy of it would be a good idea, though.

Oh i totally know how to do it…but I assume your comment was to the OP?

Oh, yeah, didn’t even realise. :sweat_smile: