[Testing Update] 2022-02-09 - Kernels, Haskell, Cutefish 0.7, Deepin, Firefox, Maui 2.1.1, Systemd

Hello community,

Another testing branch update with some usual updates for you.


Checkout our latest spin of Cutefish!

  • Most of our Kernels got updated
  • Cutefish got updated to 0.7
  • Some more Deepin packages got updated
  • Firefox is now at 97.0
  • Maui got renewed to 2.1.1
  • systemd drops cloudflare from fallback DNS servers
  • The usual upstream updates including Haskell and Python

:information_source: You may need to rebuild any AUR packages that install files to site-packages … :information_source:

You may need to rebuild any Python packages you’ve installed from the AUR. To get a list of them, you can run:

pacman -Qoq /usr/lib/python3.9

And to rebuild them all at once with an AUR helper such as yay, you can do:

yay -S $(pacman -Qoq /usr/lib/python3.9) --answerclean All

But if any of the packages don’t work with Python 3.10 yet, this might fail halfway through and you’ll have to do rebuild the remaining ones one or a few at a time.

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You get the latest stable releases of Manjaro from CDN77.

Our current supported kernels

  • linux44 4.4.302 [EOL]
  • linux49 4.9.299
  • linux414 4.14.264
  • linux419 4.19.227
  • linux54 5.4.178
  • linux510 5.10.98
  • linux515 5.15.21
  • linux516 5.16.7
  • linux517 5.17-rc3
  • linux515-rt 5.15.18_rt28
  • linux516-rt 5.16.2_rt18

Package Updates (Wed Feb 9 08:02:28 CET 2022)

  • testing community x86_64: 374 new and 363 removed package(s)
  • testing core x86_64: 26 new and 26 removed package(s)
  • testing extra x86_64: 79 new and 176 removed package(s)
  • testing kde-unstable x86_64: 314 new and 314 removed package(s)
  • testing multilib x86_64: 8 new and 8 removed package(s)

A detailed list of all package changes may be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:


Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

New issues:

Python packages from PIP and AUR - how to upgrade them - detailed instructions

Read this post.

freetype2 update might result in font characters becoming squares

Don’t worry, a relogin to your UI should fix it. We recommend to do the update in a TTY. Affected UIs so far: Gnome, Phosh, Cinnamon.

compiz packages like compiz-easy-patch got dropped from our repositories.

compiz packages like compiz-easy-patch got dropped from our repositories. Due to protobuf update you may need to rebuild that package locally on your end. Compiz-easy-patch removed from repos

Announcement for PipeWire users

Re-enable any per-user enabled pipewire-media-session.service manually:

You should re-enable any per-user pipewire-media-session.service manually to establish a new service alias for pipewire-session-manager.service added with 0.3.38.

systemctl --user enable pipewire-media-session

See the PipeWire Release Notes for more info

New warnings when building the fallback initcpio - Possibly missing firmware for module: bfa, qed, qla1280, qla2xxx

That’s due to the recent changes to the linux-firmware package. Note these are warnings, not errors. You only need those firmwares if you have Mellanox Spectrum switches, Marvell devices, Qualcomm SoCs, Cavium LiquidIO server adapters, QLogic devices and Broadcom NetXtreme II 10Gb ethernet adapters. if you have that hardware you can install linux-firmware-qlogic to get rid of those warnings. If you do not have that hardware you can safely ignore those warnings.

pamac install linux-firmware-qlogic

Older Issues

OS prober does not run and add other operating systems*

To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub

For more information, see opening post in [Stable Update] 2021-03-08.

Nvidia card owners
  • We simplified nVidia driver installation. This means we dropped legacy drivers.
    • We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DO here for your particular card.

    • If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:

      sudo mhwd -a pci nonfree 0300
      If proprietary drivers don't fix everything, please click the ► at the beginning of this line to view more info
      1. try installing kernel 5.4 LTS (Long Term Support)
      2. If that doesn’t fix it, take a full system backup, go to a console using Ctrl+Alt+F2 and:
      • Backup /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually
      • remove all nVidia related drivers and applications:
        pacman --remove nvidia*
      • Note which applications are being removed and keep them handy in a list
      • Install the driver first:
        mhwd --install video-hybrid-XXX-nvidia-prime
        (Where XXX is amd or intel if you have hybrid graphics or the whole thing is video-nvidia if you’re on an nVidia-only system)
      • reboot and see if you at least get a screen.
      • Install all the other applications from your handy list that you still need one by one.
      • Restore /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually
      • If that wouldn’t solve the issue open a new issue here referring to this update and posting at a minimum the full output of:
        inxi --admin --verbosity=7 --filter --no-host --width

      If you however still have issues with your Nvidia card, you may open a new thread in our forum: Graphics & Display - Manjaro Linux Forum or look at our tutorial on compiling old Nvidia drivers.

For AMD GPU users having a black screen with kernel 5.10

Due to a bug in the AMD drivers, please try the following first:


  1. Open a terminal or a TTY
  2. Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
  4. Add amdgpu.dc=0
  5. Save
  6. Execute sudo update-grub and reboot

For systemd-boot:

  1. Open a terminal or a TTY
  2. Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
  3. Add amdgpu.dc=0 to the end of the line options
  4. Save & reboot

For rEFInd:

  1. Open a terminal or a TTY
  2. Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: "Boot using default options" "root=
  4. Add amdgpu.dc=0
  5. Save & reboot
Possible 2 Min delay on shutdown with Gnome
  • If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
    • Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:

      ExecStart=/usr/lib/gnome-session-ctl --restart-dbus
    • Click this link For more information

Touchpad on a ThinkPad stops working

Restart again, please.

$PKGNAME warning: directory permissions differ on $Directoryname

followed by:

Filesystem: NNN package MMM

  • The solution:

    sudo chmod MMM DirectoryName

    Where obviously MMM is the second number you see (the correct one)

  • The explanation:
    Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.

Systemd error message: .slice: Failed to migrate controller cgroups

If you have a similar error message like this:

systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied

… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.

Python 3.9 Requires Rebuilds

Instructions for quickly and easily rebuilding affected AUR packages:

# Install yay
sudo pacman -S --needed --noconfirm yay

# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")
libtraceevent>=5.9-1 update requires manual intervention

2020-10-23 - Sébastien Luttringer

The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors

libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/libtraceevent.so.1

to perform the upgrade.

Arch Linux - News: libtraceevent>=5.9-1 update requires manual intervention

OpenVPN connection times out

Workaround: downgrade openvpn (2.5.0-1 => 2.4.9-2).
For a proper solution follow this bug report on Arch Linux: FS#68480 : [openvpn] running unprivileged with iproute no longer working

PAM and PAMBASE got updated, which might prevent you from login

Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.

Typical issue:

For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”

System takes a long time to boot

If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here
Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here:
systemctl disable cups.service
systemctl enable cups.socket

I think I've some font problems

With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

I’m surprised that this testing update batch doesn’t have Plasma 5.24, which was released yesterday. I don’t mind waiting for it to be available, honestly, but it’s just an observation I would like to point out.

plasma-desktop 5.24 is available in the unstable branch, how to check: Manjaro - Branch Compare

The update went through without any major showstoppers.

A few things I noticed during the update process:

Applying kernel sysctl settings...
Couldn't write '1' to 'kernel/unprivileged_userns_clone', ignoring: No such file or directory

What does that mean?

Second, I seem to still have two graphics drivers in DKMS config:

==> dkms install --no-depmod nvidia/510.39.01 -k 5.17.0-1-MANJARO
==> dkms install --no-depmod nvidia/495.46 -k 5.17.0-1-MANJARO
Error! Bad return status for module build on kernel: 5.17.0-1-MANJARO (x86_64)
Consult /var/lib/dkms/nvidia/495.46/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/495.46 -k 5.17.0-1-MANJARO' exited 10

As I am currently using driver 510.39.01: How can I remove 495.46 from the DKMS config and prevent this error from occurring?

And finally, I got this during the required reboot while the system was shut down:

[35509.312925] sd-umoun[56020]: Failed to unmount /oldroot: Device or resource busy
[35509.317505] sd-umoun[56021]: Failed to unmount /oldroot/sys: Device or resource busy
[35509.322349] shutdown[1]: Failed to finalize file systems, ignoring.

Do I have to do anything here?

remove first ( see with yay or pamac or trizen )

you cant build dkms with old version nvidia ( 495.46 series ): failed to build , exit 10
you only get exit different from 0

Indeed, it looks like I had to (re-)install nvidia-dkms. With that, pamac removed the 495.46 package and re-installed nvidia-dkms and nvidia-utils for driver 510.47.03.

However, it was not able to remove the kernel module properly, the kernel complained about kernel module 510.36 not matching 510.47.03 in the dmesg output.
As a consequence, I got no graphical desktop.

Reinstalling nvidia-dkms using yay in the terminal seems to have fixed that now, fortunately.

Thanks a lot!

A post was split to a new topic: When will plasma 5.24 available in stable

13 posts were split to a new topic: Possibly missing firmware for module: xhci_pci

This is random error because of Nvidia driver (apparently it never does that without Nvidia driver installed). There is no solution, sometimes it does that on reboot/shutdown, sometimes it doesn’t, completely random with no workaround (you could read many attempts with “solutions” but in reality there is no solution to my knowledge).

//EDIT: For the warnings on fallback image creation, I’m using a good fix (I’m doing that since long time because it cuts down image creation a lot, especially when you have multiple kernels): I change the preset of each kernel to only build the default image, and NOT the fallback image :rofl:

Example for /etc/mkinitcpio.d/linux515.preset


Why I’m doing that is also because I never had to use the fallback kernel image, and the day I tried it didn’t even boot :clown_face:

thanks for the update, my sddm-greeter was dumping core on boot/start after the last one

Thanks a lot for pointing me in the right direction :+1:

Indeed, there appears to be a solution provided by Jonas Malhaco Filho here FS#63697 : systemd 243.0-1 poweroff/reboot umount errors

So what does that mean?
Create a script with the following contents

# Remove all Nvidia modules on shutdown
# to avoid errors like
# [35509.312925] sd-umoun[56020]: Failed to unmount /oldroot: Device or resource busy
# [35509.317505] sd-umoun[56021]: Failed to unmount /oldroot/sys: Device or resource busy
# [35509.322349] shutdown[1]: Failed to finalize file systems, ignoring.
for MODULE in nvidia_drm nvidia_modeset nvidia_uvm nvidia
rmmod $MODULE

Name this script, for example, nvidia.shutdown, make it executable as usual and place it in /usr/lib/systemd/system-shutdown.

Another version of this script was provided by Ivan Layapunov: FS#63697 : systemd 243.0-1 poweroff/reboot umount errors

Done. Error messages gone :slight_smile:


OK then there might be a solution now. Need to try this in the long run to confirm it works (the issue is sporadic on my system, most of the time I don’t have the issue, but once in a while it does it).

Anyone getting unusually high CPU usage when opening tabs in Firefox 97.0.1?

you mean :point_up: anyway can`t confirm this issue

No. This is the Testing Update thread. :wink:

This update fixed the issues I had here: [Testing Update] 2022-02-06 - Kernels, Pamac, Cleanups - #16 by sdwolfz

Thanks @dvgme for pointing out dash-to-dock!

I think they always wait for the first point release. So you’ll never get the 5.24 update, but you will get the 5.24.1 initial bugfix. I wish they weren’t this careful on testing, but I guessI could switch to unstable!

Yup, you always have the option to do that if you have the pressing need to try out Plasma 5.24 right now. I just remembered that it’s typical of Manjaro team to wait until the first couple bugfix releases before pushing a new Plasma version to testing and eventually to stable. :smile:

@philm after this update kmail crashes when opening a GPG-encrypted message:

This is upstream. The workaround is to downgrade qgpgme to v1.16.0-3.