[SOLVED] Messed up big time with another pacman crash

TotoShampoin · 2024-05-15 07:59:40

Okay, so...

I had yet another pacman crash resulting in broken packages

So I booted from a live boot. I did the pacman -Qkk into a tmp file, like usual.
But I did that from the chroot. It could output the broken packages, but I couldn't update it.
So instead, I left the chroot and redis that with root=mnt.

But the issue is that the mtree files were apparently remade, but also, the tmp file is gone now, so I can't reinstall any of the broken packages.

What can I do?

I'm guessing I could try to reinstall every single package, with pacman -Qq and pacman -S, but I'd like to know if there is another solution?

Last edited by TotoShampoin (2024-05-15 10:50:05)

seth · 2024-05-15 08:06:22

The packages w/ previously broken files (which is more relevant than the broken mtree, that's an intermediate step, necessary to fix teh actual problem) will still show up w/ broken files in "pacman -Qkk"

like usual

https://aur.archlinux.org/packages/nvidia-535xx-dkms

TotoShampoin · 2024-05-15 08:18:36

Okay, here's the pacman qkk (--root=/mnt)
https://0x0.st/XKkw.txt

I should mention that any attempt to use pacman in chroot, with root=mnt AND with pacstrap result in failures as a bunch of "usr/lib is empty, not checked"

TotoShampoin · 2024-05-15 09:01:29

Oh actually, reinstalling all packages with pacstrap did seem to work, even though a bunch of .so files are said to be missing and thus unchecked.

So, I'm rebooting, and... It still fails.
Failed to start Power Profiles daemon, User Login Management, D-Bus System Message Bus...

It didn't work, I'm missing a bunch of so files

TotoShampoin · 2024-05-15 09:31:09

Nevermind, I managed to reinstall the broken packages and reboot properly.

However, I am STILL missing .so files, and I think these are necessary for kde plasma to work, because sddm doesn't start (even though I can run things on tty).

EDIT: It crashed again, but some packages are still broken, apparently

Last edited by TotoShampoin (2024-05-15 10:10:35)

TotoShampoin · 2024-05-15 10:09:59

Okay, here's the missing .so files
https://0x0.st/XKdZ.txt

TotoShampoin · 2024-05-15 10:49:51

I fixed it all, by reinstall one by one each package owning the libs, with pacman -Qo and all.

Solved!

Awebb · 2024-05-15 10:53:40

How did you tell dependencies apart from explicitly installed packages?

seth · 2024-05-15 13:30:49

pacman -S preserves the installation reason by default

The empty objects should have shown up in "pacman -Qkk" as broken packages?
--dbonly only fixes the db, you'll then get linker warnings because the files themselves are still corrupted, that's "ok"-ish, just plow through and install the packages with deviating files (the mtree list is NOT sufficient to fix the system, it's only the package that need database sanitation before the actual fix)

TotoShampoin · 2024-05-15 13:54:14

Awebb wrote:

How did you tell dependencies apart from explicitly installed packages?

I installed a random package with pacman (curl, in this case), to get the ldconfig warning.
Then I extracted the missing/empty files from those.
Then, for each file, I did `pacman -Qo`.
And then, with a sort and uniq, I did a pacman -S of each broken package

And all worked out!

Among the broken packages were various kde plasma apps n modules, and mesa

Last edited by TotoShampoin (2024-05-15 13:54:47)

Awebb · 2024-05-16 09:19:01

seth wrote:

pacman -S preserves the installation reason by default

I know, off-topic, but has this always been the case? Have I been working around a problem that doesn't exist for years?

seth · 2024-05-16 13:25:21

Mind to elaborate on the supposed problem and workaround?
https://bbs.archlinux.org/viewtopic.php?id=237109 ?

I can't tell whether this has at some point not been the case - you'd have to ask Allan as chances are that he broke it

Awebb · 2024-05-16 13:38:11

seth wrote:

Mind to elaborate on the supposed problem and workaround?
https://bbs.archlinux.org/viewtopic.php?id=237109 ?
I can't tell whether this has at some point not been the case - you'd have to ask Allan as chances are that he broke it

The "problem" was, that I "remember" from way back, that re-installing an already installed package marked as dependency with pacman -S sets the installation reason to explicit. The workaround in situations like in this thread, was to create two lists of packages and install one with --asdeps and the other without or with --asexplicit. I might have been wrong in the first place or the behavior changed at some point during the last decade.

Good to know it's easy "now".

Trilby · 2024-05-16 14:08:50

The suspicion that pacman would not preserve the installation reason has been around for ages - and it just will not go away. But I don't believe the suspicion was ever valid (at least in the ~15 years I've been using arch).

TotoShampoin · 2024-05-20 18:28:26

So, I have been hit with another pacman crash... Only this time, it's very weird:

It was only 3 packages from "extra". I just don't remember which ones it was.
After the crash, I tried booting anyway, instead of live usb, and... It boots normally?

But also, I can see there is 1 systemd fail, which is "WPA supplicant" (https://0x0.st/XPxD.txt)
I still have access to internet from the ethernet cable, so I guess there is that...

But when I do pacman -Qkk, it seems unable to find any broken mtree (or any unusual altered file...)

Do I have a way to retrieve those 3 obviously broken packages and reinstall them?

EDIT: So, I'm doing the thing again from live usb, and it could find and fix my broken packages.
Moral of the story: When pacman update crashes, assume nothing works normally.

Last edited by TotoShampoin (2024-05-20 18:51:05)

seth · 2024-05-20 20:48:43

Did you consider switching to https://aur.archlinux.org/packages/nvidia-535xx-dkms or nvidia-open in order to hopefully prevent those frequent crashes during updates?

TotoShampoin · 2024-05-25 10:51:57

seth wrote:

Did you consider switching to https://aur.archlinux.org/packages/nvidia-535xx-dkms or nvidia-open in order to hopefully prevent those frequent crashes during updates?

I happen to be using nvidia dkms, yes

But I don't see why nvidia would be what's crashing?

seth · 2024-05-25 13:42:34

The point isn't about "DKMS" but "535xx", https://bbs.archlinux.org/viewtopic.php?id=293400

TotoShampoin · 2024-05-25 20:23:30

Oooooh I see, okay

Do I have to uninstall nvidia-dkms first, or will pacman automatically uninstall it?
(I'll find out soon, I just don't have my laptop in the immediate moment)

EDIT: It asks to uninstall. Well, it asks once for nvidia-utils, fails, then asks again for both 550 and utils, which does succeed.

All done! Hopefully it won't break anymore

Last edited by TotoShampoin (2024-05-25 20:48:46)

Arch Linux

#1 2024-05-15 07:59:40

[SOLVED] Messed up big time with another pacman crash

#2 2024-05-15 08:06:22

Re: [SOLVED] Messed up big time with another pacman crash

#3 2024-05-15 08:18:36

Re: [SOLVED] Messed up big time with another pacman crash

#4 2024-05-15 09:01:29

Re: [SOLVED] Messed up big time with another pacman crash

#5 2024-05-15 09:31:09

Re: [SOLVED] Messed up big time with another pacman crash

#6 2024-05-15 10:09:59

Re: [SOLVED] Messed up big time with another pacman crash

#7 2024-05-15 10:49:51

Re: [SOLVED] Messed up big time with another pacman crash

#8 2024-05-15 10:53:40

Re: [SOLVED] Messed up big time with another pacman crash

#9 2024-05-15 13:30:49

Re: [SOLVED] Messed up big time with another pacman crash

#10 2024-05-15 13:54:14

Re: [SOLVED] Messed up big time with another pacman crash

#11 2024-05-16 09:19:01

Re: [SOLVED] Messed up big time with another pacman crash

#12 2024-05-16 13:25:21

Re: [SOLVED] Messed up big time with another pacman crash

#13 2024-05-16 13:38:11

Re: [SOLVED] Messed up big time with another pacman crash

#14 2024-05-16 14:08:50

Re: [SOLVED] Messed up big time with another pacman crash

#15 2024-05-20 18:28:26

Re: [SOLVED] Messed up big time with another pacman crash

#16 2024-05-20 20:48:43

Re: [SOLVED] Messed up big time with another pacman crash

#17 2024-05-25 10:51:57

Re: [SOLVED] Messed up big time with another pacman crash

#18 2024-05-25 13:42:34

Re: [SOLVED] Messed up big time with another pacman crash

#19 2024-05-25 20:23:30

Re: [SOLVED] Messed up big time with another pacman crash

Board footer