[SOLVED] Failed to start D-Bus System Message Bus after update crashed

TotoShampoin · 2024-03-01 10:58:15

Yesterday, I did another yay update, but it crashed (the computer frozen, with the caps lock led blinking). So I force rebooted it (which I know is a very bad thing to do with an update going...)

And ever since, everytime I boot up, I get a working SDDM, but logging in does nothing. And I'm able to alt-f3 then alt-f1 to get this (sorry for using a pic, I don't know how to turn that into text that I could send)

https://cdn.discordapp.com/attachments/ … 3061b5b2e&

It's worth mentioning that I *can* boot on a live arch usb, chroot on my disk, and yay update from there just fine. I know that because I did that earlier. Didn't solve the thing.

How can I fix it?

Last edited by TotoShampoin (2024-03-03 08:33:20)

TotoShampoin · 2024-03-01 11:05:17

Actually, doing a pacman update outputs this

https://cdn.discordapp.com/attachments/ … 56b7fcc5a&

So actually, that didn't work...

Last edited by TotoShampoin (2024-03-01 11:18:53)

seth · 2024-03-01 11:08:15

Please replace the oversized image with a link.

Boot the iso, chroot and check how bad it is:

sudo LC_ALL=C pacman -Qkk 2>&1 | grep -v ', 0 altered files'

You'll have to fix the broken packages by explicitly re-installing them (you might have to restore the mtree w/ --dbonly)

If the system still doesn't boot, remove the "quiet" kernel parameter so you're hopefully getting more informative boot messages.

TotoShampoin · 2024-03-01 11:18:15

Extremely bad

https://media.discordapp.net/attachment … b58e419f5&
https://media.discordapp.net/attachment … b3c439c6f&
https://media.discordapp.net/attachment … a9c4d558d&
https://media.discordapp.net/attachment … fe4f41c4f&

fstab, group, passwd, locale, mkinitcpio, and much more are modified

And some packages even say "no mtree file" (idk what a mtree is, btw)

How do I reinstall *all* the broken packages? Would I be better off just force reinstalling all the packages?

seth · 2024-03-01 11:33:01

You'll have to re-install the packages that lack the mtree w/ "--dbonly" or you'll get a lot of spurious file collision errors.

Some deviations are perfectly normal and expectable, every difference in /usr/lib and /usr/bin is a massive problem.
If you need others to go through the corrupted packages, please rediredt the output into a file (... >/tmp/package.status) and upload that to https://0x0.st - it has instructions on how to do that w/ curl from the console.

TotoShampoin · 2024-03-01 11:47:33

That didn't go smoothly, curl seg faulted in chroot.
I had to put the file in my home directory and use curl outside of chroot to send it.

In any case...

https://0x0.st/HRn8.txt

seth · 2024-03-01 12:06:13

It's not sooooo bad.
Reinstall the packages that lost the mtree first w/ "-S --dbonly", then again, explicitly w/ -S only.
Then attempt an -Syu

TotoShampoin · 2024-03-01 12:13:06

Live typing this message

"there is nothing to do", it said. So, let's try and reboot, now...

IT'S FIXED! Thank you Seth!

seth · 2024-03-01 15:40:36

\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.

wolfisraging · 2024-04-01 10:52:11

I’m having same issue here, any single command to all the broken packages and fix the issue by reinstalling them all? I tried reinstalling all the package I have… didn’t solve the issue. Any suggestions?

seth · 2024-04-01 12:32:40

Post the output of

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

Arch Linux

#1 2024-03-01 10:58:15

[SOLVED] Failed to start D-Bus System Message Bus after update crashed

#2 2024-03-01 11:05:17

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#3 2024-03-01 11:08:15

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#4 2024-03-01 11:18:15

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#5 2024-03-01 11:33:01

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#6 2024-03-01 11:47:33

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#7 2024-03-01 12:06:13

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#8 2024-03-01 12:13:06

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#9 2024-03-01 15:40:36

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#10 2024-04-01 10:52:11

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

#11 2024-04-01 12:32:40

Re: [SOLVED] Failed to start D-Bus System Message Bus after update crashed

Board footer