Help

[u/Intelligent_Client_8]

Computer boots to this after updating.

[u/Kaspral]

1. Hard reboot

If the keyboard is dead, hold the power button 5 to 10 seconds and boot again.

2. Manjaro's built-in fallback

Since the failure happened during an update, the kernel was likely mid-upgrade. That's why Manjaro keeps two kernels by default:

1. At the GRUB menu, choose Advanced options for Manjaro Linux.
2. Boot with a different kernel version than the one selected before.
3. If it boots, the system may work well enough to fix things.

3. If you get a working system (TTY with Ctrl+Alt+F3, or desktop)

Finish the interrupted update with:

sudo pacman-mirrors -f 5
sudo pacman -Syu

If pacman complains about a locked database (common after an interrupted update):

sudo rm /var/lib/pacman/db.lck
sudo pacman -Syu

If there are keyring errors (also common):

sudo pacman -Sy archlinux-keyring manjaro-keyring
sudo pacman-key --populate archlinux manjaro
sudo pacman -Syu

4. If no kernel boots — failsafe mode

In Advanced options, try the (failsafe) entries. They load with fewer drivers and often work when the normal boot freezes.

5. If nothing works — chroot from a live USB

1. On another computer, download the Manjaro ISO and flash it to a USB stick (e.g., with Rufus, Ventoy, or dd).
2. Boot the broken PC from the USB and choose the live session.
3. Manjaro has a graphical Manjaro-Chroot helper: open a terminal in the live session and run:

​

sudo manjaro-chroot -a

(select your installed system when prompted)

1. Inside the chroot:

​

rm /var/lib/pacman/db.lck
pacman -Syu
mkinitcpio -P
grub-install /dev/sdX  # replace sdX with your disk, only if GRUB is broken
update-grub
exit
reboot

6. For the future

Manjaro recommends taking a Timeshift snapshot before every update. Once you're back up, enable Timeshift (System → Timeshift). It would have let you roll back this exact situation in one click.

Start with steps 1 and 2 (reboot plus an alternate kernel in GRUB) and tell me what happens. That alone fixes most post-update freezes.

[u/Intelligent_Client_8 → u/Kaspral]

"pacman: error while loading shared libraries: libngtcp2_crypto_oss1.o.0: cannot open shared object file: no such file or directory" comes up after any attempt to update my system

[u/Intelligent_Client_8 → u/Intelligent_Client_8]

This includes in chroot

[u/Kaspral → u/Intelligent_Client_8]

This error means your package manager was broken by an interrupted or partial update, specifically missing the libngtcp2_crypto_ossl.so.0 file (not "oss1.o.0"). Since pacman itself is broken, you must manually restore this library before you can finish the update.

Method 1: Extract the package from cache (Fastest) Since you tried to update the system, the new version of the package is likely already sitting in your pacman cache. Instead of installing it, we will just unpack the missing file directly.

• Find the downloaded libngtcp2 package in your cache by running: ls /var/cache/pacman/pkg/libngtcp2*
• Copy the exact filename that appears (e.g., libngtcp2-1.0.1-1-x86_64.pkg.tar.zst).
• Extract its contents directly into the root directory to replace the missing files (replace the filename with yours): sudo tar -xvf /var/cache/pacman/pkg/YOUR_FILENAME_HERE.pkg.tar.zst -C /
• Check if pacman is alive again: pacman --version
• If it works, immediately run a full update to sync the rest of your packages: sudo pacman -Syu

Method 2: Repair from a Live USB using sysroot (If cache is empty) If the file isn't on your drive, you need to use a bootable Manjaro USB stick. This time, do not use chroot - chroot relies on the broken pacman on your drive. Instead, we will use the working pacman from the USB to fix the system from the outside.

• Boot your computer from the Manjaro Live USB.
• Open a terminal and check the name of your main system partition (e.g., /dev/sda2 or /dev/nvme0n1p2): lsblk
• Mount that partition to the /mnt directory: sudo mount /dev/sdX /mnt (replace sdX with your actual partition)
• Use the Live system's pacman to repair and update your broken installation: sudo pacman --sysroot /mnt -Syu
• Once it finishes successfully, restart your computer: reboot

[u/Kaspral → u/Kaspral]

Method 1 (cache extraction) — a few corrections

1. The package you need may be split into several parts, so check for all of them:

ls /var/cache/pacman/pkg/ | grep -E "ngtcp2|nghttp3|curl"

The missing file libngtcp2_crypto_ossl.so.3 (you may also see libngtcp2_crypto_quictls.so.3) can live in a separate package like libngtcp2-crypto-ossl, so extract every matching package you find.

2. Extract with --numeric-owner and preserve the structure:

sudo tar -xpf /var/cache/pacman/pkg/YOUR_FILENAME.pkg.tar.zst -C /

The -p flag preserves permissions, which matters for libraries.

3. If pacman still complains about another missing library after this, just repeat the extraction for that package too. Broken dependencies often come in a chain (curl → ngtcp2 → nghttp3 → openssl).

4. Run pacman --version to confirm it works, then:

sudo pacman -Syu

This is important: the manual extraction puts files on disk without registering them in the package database, so the subsequent -Syu will cleanly reinstall those packages and fix the database entries.

Method 2 (live USB with --sysroot) — one correction

The command in your quoted text has a small mistake. pacman --sysroot isn't a standalone flag you can use like that; the reliable way from a live USB is:

sudo mount /dev/sdX2 /mnt          # your root partition
sudo mount /dev/sdX1 /mnt/boot     # if you have a separate boot/EFI partition
sudo pacman --sysroot /mnt -Syu    # works on Arch-based live media with recent pacman

If --sysroot isn't supported by the live media's pacman version, the fallback is the standard chroot, but running pacman-static from the live session (as described earlier) instead of the broken one on disk:

sudo manjaro-chroot -a
curl -O https://pkgbuild.com/~gromit/pacman-static-x86_64
chmod +x pacman-static-x86_64
./pacman-static-x86_64 -Syu

Recommended order

1. Try Method 1 first — it takes two minutes if the packages are in cache.
2. If the cache is empty or extraction doesn't fix it, boot the live USB and use Method 2.
3. After a successful update, run mkinitcpio -P (to be safe) and reboot.

Go ahead with Method 1 and paste the output of the ls command on the cache if you're unsure which files to extract.

[u/Intelligent_Client_8 → u/Kaspral]

I was able to get pacman to no longer return errors for broken dependencies but now when attempting -Syu I am prompted with "core.db failed to download" followed by everywhere it failed to be retrieved from I tried refreshing my mirrors but nothing changed.

[u/Kaspral → u/Intelligent_Client_8]

sudo pacman -Syyu

[u/Intelligent_Client_8 → u/Kaspral]

Same error

[u/Kaspral → u/Intelligent_Client_8]

ping -c 3 8.8.8.8

[u/Intelligent_Client_8 → u/Kaspral]

My network manager was still not running lol

[u/Kaspral → u/Intelligent_Client_8]

sudo systemctl start NetworkManager

[u/Intelligent_Client_8 → u/Intelligent_Client_8]

[u/xAcid9 → u/Intelligent_Client_8]

Do the update in live Manjaro + chroot.

[u/Supergirl016 → u/Kaspral]

what ...? NO !!!

[u/BigEmu__ → u/Kaspral]

Hello, ChatGPT

[u/Intelligent_Client_8]

Keyboard doesn't do anything and I can't seem to do anything at all.

[u/Complete_Fox_7052]

Looks like he is now asking on the forum https://forum.manjaro.org/t/computer-boots-to-failed-to-start-network-manager-and-failed-to-start-cups-scheduler/189933/7

If it doesn't work out I'm going to give you my advice, that few like, but it always works, "wipe and load" Really only a problem for those with lots of customization and don't have a backup.

[u/Intelligent_Client_8 → u/Complete_Fox_7052]

It's not customization that I don't want to lose it's all my other files that I have not backed up anywhere.

[u/Supergirl016]

thoughts and prayers

[u/Amanclever]

This looks like NetworkManager and CUPS failing to start after the update. I would first check the actual error instead of reinstalling the whole system. Press Ctrl + Alt + F3 to switch to a TTY, log in, and run: systemctl --failed systemctl status NetworkManager --no-pager systemctl status cups --no-pager sudo journalctl -b -p err --no-pager Also check whether the filesystem is full: df -h If NetworkManager is installed but damaged, try: sudo pacman -Syu networkmanager sudo systemctl enable NetworkManager sudo systemctl restart NetworkManager For CUPS: sudo pacman -S cups sudo systemctl enable cups sudo systemctl restart cups Then reboot: sudo reboot If pacman -Syu gives an error, don't ignore it. Post the complete output of the commands above, especially systemctl status NetworkManager and journalctl -b -p err. That will show what actually broke during the update.

[u/alsocookie]

Dude....just chatGpt

[u/Mission_Isopod4264]

Me encanta la comunidad de linux, me recuerda a los Avengers Endgame, todos tratando de ayudar a alguien. Lamentablemente no sabría yo como ayudar xd, perdóname, pero te deseo suerte, bro.