Well, I think I won’t even try to do an update for at least 24 hours or more. Live and learn
I reviewed the repos, checked my mirrorlist file, ran pacman-mirrors --fasttrack and checked my mirrorlist against the web page again. I used pacman -Syu and tried pacman -Syyu and the same results. I’m on a VM and restored for each attempt.
The last two errors have been "error: could not extract .... (Zstd decompression failed: Corrupted block detected), as mentioned here. It has been different files. I think the repos are still syncing (United_States), even though there is a checkmark indicating “Up to date”.
My conf was also overridden:
[2020-11-05T06:55:32+0100] [ALPM] warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew
I have no idea how I can restore the previous values present in the conf
At this time, mkinitcpio.conf was updated and a pacnew was created. The only difference was the use of “()” verses “""” for array lists. The only place encrypt appears is in an example HOOKS which is commented.
You should be able to confirm the creation of a pacnew file by looking at /var/log/pacman.log. I found it there. I also run pacman and pipe it to tee and save it in a timestamped file. I look for the following specifically:
less --pattern='(Generating|warning:|error:|New|Optional|[0-9]+/[0-9]+)'
The grub.pacnew in the last update is a good example. On my side, I rejected all the confilcts as I am not using the quiet splash + I have a grub theme + I am using custom kernel parameters.
So merging these files depends on your custom settings and may vary from one user to antoher.
After every update just run: DIFFPROG=meld pacdiff
It will take you through every pacnew and you can view, skip, remove. Read man page. meld is a super nice gui diff tool. You can compare files side-by-side.
The pacnew files cannot be merged without being reviewed first. Some will get you in big trouble.
Thank you very much! My system is working now again too. I also didn’t have a /etc/mkinitcpio.conf.pacnew. I had a grub.cfg.pacnew but this didn’t contain any critical changes (mainly some new spaces).
My system is asking for the encryption password twice now. Do you have this behavior too?
I run a couple of laptops with Manjaro-Xfce on AMD hardware. Yesterday’s upgrade worked fine, but I was wondering as to why the upgrade pulled certain KDE components. I haven’t noticed that before, but then I don’t watch it all the time, hence I might missed it.
Fixed it. Had to install the last stable version from the Arch Linux Archive.
I think the problem in my case is the older vpn Server I try to connect to.
First uninstall openvpn via pacman. After this install it from the Archive in an older version:
