[SOLVED] Unable to Boot After Package Upgrades/Installations

tony5429 · 2023-01-26 19:35:38

In an attempt to install MapTiler, I upgraded xz (from 5.2.6-1 to 5.4.1-1) and its dependencies, and installed gdal 3.6.2-1, dpkg 1.21.19-1, perl-io-string 1.08-12, and perl-test-pod 1.52-7. I then proceeded to attempt to install the .deb file for MapTiler with dpkg. After getting 2 or 3 layers into .deb dependencies required for MapTiler and, I believe, not actually successfully installing any .deb packages, I noticed that I was unable to start any programs on my computer. The programs I already had opened were working fine but whenever I tried to open anything new, nothing would happen. I then proceeded to restart the computer, but the restart button (in KDE) was non-responsive. So I powered off with the physical power button. Upon attempting to restart the computer, I was met with this message: https://i.imgur.com/gFNhDoN.jpg

So, I figured I would just boot into Linux with my Arch USB installer, mount the relevant partitions, arch-chroot in, and revert the changes I'd made. However, upon trying to arch-chroot in, I am being met with this error:

/bin/bash: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE

Does anyone have any ideas what's going on or how/if I can fix it? I see the warning about using dpkg to install .deb packages in Arch, but I didn't actually install anything - I just attempted to. (Maybe that was sufficient to break the system?)

Last edited by tony5429 (2023-01-26 21:07:41)

Trilby · 2023-01-26 19:51:04

tony5429 wrote:

I upgraded xz (to 5.4.1-1) and its dependencies

That sounded fishy when I first read it - before I even saw the resulting symptoms. How exactly did you do this? It sounds like you did a partial upgrade. And doing a partial upgrade with a package as "low level" as xz would likely result in errors like what you are seeing.

The solution is to fully upgrade your system from the iso using pacman on the iso with the --sysroot flag, e.g. mount your partitions properly under /mnt, then `pacman -Syu --sysroot /mnt`

EDIT: I overlooked the use of dpkg as noted below. You can use dpkg in a PKGBUILD (as the maptiler PKGBUILD does) to install to a $pkgdir that will be turned into an arch package. You could also alternatively try debtap to convert a .deb to a .pkg.tar.xz, but if you ran dpkg as root and installed debian libraries over the arch ones, you have more to fix than an -Syu - you'll need to reinstall any affected packages. You could search for these with invocations of `pacman -Qk` or `pacman -Qkk`, but really it's probably easier to just reinstall all base packages. So from the live medium:

## ensure all partitions are properly mounted to /mnt, then
pacman --sysroot /mnt -Syu base

That should get you back to being able to boot up. Then once back in your system, explore further with the -Qk{k} to see if other packages have been affected.

Last edited by Trilby (2023-01-26 21:03:49)

teckk · 2023-01-26 19:52:28

I upgraded xz (from x to y) and its dependencies

Partial updated are not supported by arch. Update the whole box with:

pacman -Syu

Then install a package from the repo with:

pacman -S <package>

Or use makepkg on a PKGBUILD from the AUR. If you are going to build/install random stuff, don't put it in your file system tree. Put it somewhere in /home and run it. Or create a PKGBUILD for the software that you want to build (maybe not easy), and make a package, then install the package with:

pacman -U <package>

In an attempt to install MapTiler,

From where?
https://aur.archlinux.org/packages/maptiler
https://aur.archlinux.org/packages/maptiler-oss

I then proceeded to attempt to install the .deb file for MapTiler with dpkg.

If you overwrite system files with something outside of the package manager, you are going to have a mess real quick.

I don't know what you have overwritten. Do you? Does dpkg keep a log of what it did?

seth · 2023-01-26 20:54:01

In case "pacman --sysroot /mnt -Syu base" fails as well because of the degraded state of the installation, try

pacman --root /mnt --cachedir /mnt/var/cache/pacman/pkg -Syu

tony5429 · 2023-01-26 21:07:11

Thanks for all the feedback! In hindsight, yes, it was pretty silly of me. I was, in fact, doing a partial upgrade. Using the sysroot option on pacman, I was able to revert the changes I'd made (in terms of new and upgraded packages), but was still having the same issue with arch-chroot, kernel panic on boot, and the symbol lookup error. I resolved it by reinstalling glibc (same version, just reinstalling). Now it's fixed, and my lesson has been learned. So, a relieved and joyful 1000th post for me here.

Last edited by tony5429 (2023-01-26 21:08:30)

Arch Linux

#1 2023-01-26 19:35:38

[SOLVED] Unable to Boot After Package Upgrades/Installations

#2 2023-01-26 19:51:04

Re: [SOLVED] Unable to Boot After Package Upgrades/Installations

#3 2023-01-26 19:52:28

Re: [SOLVED] Unable to Boot After Package Upgrades/Installations

#4 2023-01-26 20:54:01

Re: [SOLVED] Unable to Boot After Package Upgrades/Installations

#5 2023-01-26 21:07:11

Re: [SOLVED] Unable to Boot After Package Upgrades/Installations

Board footer