It’s synchronised, right? It’s way too complicated to repair.
Check if there is a dangling lockfile
I have the same issue. Numerous warnings occur when “Building image from preset”. I did confirm that I can boot using this newly created image.
( 9/21) Updating module dependencies...
depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/4.19.251-1-MANJARO: No such file or directory
(10/21) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
-> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
==> Starting build: 4.19.251-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
install: cannot stat '/lib/modules/4.19.251-1-MANJARO/modules.builtin.modinfo': No such file or directory
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.9o3whd/root/lib/modules/4.19.251-1-MANJARO: No such file or directory
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
-> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
==> Starting build: 4.19.251-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
install: cannot stat '/lib/modules/4.19.251-1-MANJARO/modules.builtin.modinfo': No such file or directory
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.M02rTA/root/lib/modules/4.19.251-1-MANJARO: No such file or directory
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
1 Like
In this upgrade, inside file mkinitcpio.conf, in HOOKS line systemd was replaced by udev, should apply the new change ?
mkinitcpio.conf : HOOKS=(base systemd autodetect modconf block filesystems keyboard fsck)
mkinitcpio.conf.pacnew : HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
1 Like
Cinnamon is still version 5.4.2, which is full of bugs. 
1 Like
I also get this error. If you go to Hamburger - Help - More troubleshooting information, then it lists there recent crashes. If you click on the crash, it’ll show some details and matched bugs on Bugzilla.
Here is the bug report it matched: 1777927 - Crash in [@ XDisplayString]: Consider blocking vdpau_drv_video.so from being loaded
Based on the report, I went to ~/.mozilla/%your_profile%/prefs.js, and set media.ffmpeg.vaapi.enabled to false. The old profile works now.
5 Likes
Hey, I do have issue with this update in regard to python-pip package…
:: Proceed with installation? [Y/n]
(225/225) checking keys in keyring [----------------------------------] 100%
(225/225) checking package integrity [----------------------------------] 100%
(225/225) loading package files [----------------------------------] 100%
(225/225) checking for file conflicts [----------------------------------] 100%
error: failed to commit transaction (conflicting files)
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/commands/__pycache__/index.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/commands/index.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/index/__pycache__/sources.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/index/sources.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/__init__.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/__pycache__/__init__.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/__pycache__/_distutils.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/__pycache__/_sysconfig.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/__pycache__/base.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/_distutils.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/_sysconfig.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/locations/base.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/__init__.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/__pycache__/__init__.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/__pycache__/base.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/__pycache__/pkg_resources.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/base.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/__init__.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/__pycache__/__init__.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/__pycache__/_compat.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/__pycache__/_dists.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/__pycache__/_envs.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_compat.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_dists.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/metadata/pkg_resources.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/operations/build/__pycache__/build_tracker.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/operations/build/__pycache__/metadata_editable.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/operations/build/__pycache__/wheel_editable.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/operations/build/build_tracker.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/operations/build/metadata_editable.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/operations/build/wheel_editable.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/utils/__pycache__/_log.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/utils/__pycache__/egg_link.cpython-310.pyc exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/utils/_log.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/_internal/utils/egg_link.py exists in filesystem
python-pip: /usr/lib/python3.10/site-packages/pip/py.typed exists in filesystem
Errors occurred, no packages were upgraded.
-> error installing repo packages
Not really want to remove pip to re-install it as I have some packages already, but my version is older than the updated one :
$ pip3 -V
pip 22.1.1 from /home/roiarthurb/.local/lib/python3.10/site-packages/pip (python 3.10)
Any idea how to fix ? 
Fixed by allowing overwrite in independantly upgrading pip with this command :
sudo pacman -S python-pip --overwrite "/usr/lib/python3.10/*"
After updating and booting with Kernel 5.18.10-1, smb-mounts for my Synology NAS I did set up via systemd mounts fail.
Reverting back to Kernel 5.17.15-1 or 5.15.53-1 brings back the mounts.
As I am not a deeply technical user, I kind of struggle to figure out, what happens here … …
set
media.ffmpeg.vaapi.enabledtofalse
This setting can also be changed using Firefox about:config
search for ‘vaapi’ and press toggle button: ⇌ (or reset: ↶) to change setting to false
Also I wonder why Manjaro reverted zstd compression by default. I noticed that after fixing .pacnew mkinitcpio started to generate gzip compressed images.
Not all of the kernels available to install support zstd compression (I forget from which version it is compatible).
Since 5.9 IIRC. Makes sense for old kernels, though I don’t have anything older than latest LTS (5.15) on my machine 
1 Like
Xfce: I have five systems with Manjaro xfce. I updated one, no problems. Moved on to the next one. No problems, EXCEPT, for some reason the update installed “pipewire 1:0.3.54-1”.
None of my systems have pipewire.
I removed it, I just don’t understand why that was installed on one system and not the other.
Oh well, we’ll see what happens with the remaining three systems.
I was on track and currently using my profile by deleting/renaming the prefs.js! Just woke up and will try the suggested solution (high hopes now). Thank you for this in advance.
Hello everyone,
After today’s update, I encountered a minor issue with the python-docutils package and the Spyder IDE.
Here’s the error message when I tried to start Spyder:
pkg_resources.DistributionNotFound: The 'docutils<0.19,>=0.14' distribution was not found and is required by sphinx
Reverting to python-docutils-1:0.18-1 fixes this compatibility issue
I get the following warnings:
depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/4.19.251-1-MANJARO: No such file or directory
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.FRmAU8/root/lib/modules/4.19.251-1-MANJARO: No such file or directory
==> WARNING: errors were encountered during the build. The image may not be complete.
How can I resolve this? Deinstall kernel 4.19?
Besides, a mkinitcpio.conf has been installed as mkinitcpio.conf.pacnew with the following line:
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
My current mkinitcpio.conf has this line:
HOOKS=(base udev autodetect modconf block keyboard keymap filesystems fsck)
Additionally, the mkinitcpio.conf.pacnew has the following block:
# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"
What should I do?
That was not possible for me, because Firefox didn’t run on my profile. I had to edit the file manually like suggested before and now everything is fine and back.
It is, for sure. But Arch is still at 5.4.2 ( or at least the Arch VM I run, updated last night ) so Manjaro wouldn’t have above that
According to mkinitcpio - ArchWiki, keymap is used in HOOKS for vconsole… and from what I can tell about digging into what a “virtual console” is, they are the screens we get when we switch from tty1 to say tty4 (CTRL-ALT-F4)
So I’m confused why keymap is being removed from HOOKS when vconsoles are used pretty frequently.
1 Like