[Testing Update] 2021-04-22 - Kernels, Nvidia 465, Firefox 88, Mate 1.24.2, Virtualbox, Thunderbird

Hello community,

Another testing branch update with some usual updates for you.

Don’t miss out on the special offers for your Manjaro Cloud-Desktop!

  • Most of our Kernels got updated
  • Nvidia driver is at 465.24.02
  • Virtualbox got a new release
  • Firefox is now at 88
  • We updated Thunderbird to 78.10.0
  • Mate got a new point release to its 1.24 series
  • A lot of KDE-Dev package updates
  • Other regular upstream updates including python and haskell

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

Our current supported kernels

  • linux44 4.4.267
  • linux49 4.9.267
  • linux414 4.14.231
  • linux419 4.19.188
  • linux54 5.4.113
  • linux59 5.9.16 [EOL]
  • linux510 5.10.31
  • linux511 5.11.15
  • linux512 5.12-rc8
  • linux54-rt 5.4.106_rt54
  • linux59-rt 5.9.1_rt19

Packages Changes (Wed Apr 21 14:17:30 CEST 2021)

  • testing community x86_64: 603 new and 590 removed package(s)
  • testing core x86_64: 28 new and 28 removed package(s)
  • testing extra x86_64: 484 new and 582 removed package(s)
  • testing kde-unstable x86_64: 81 new and 81 removed package(s)
  • testing multilib x86_64: 12 new and 12 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:

  • OS prober does not run and add other operating systems

    Please click the ► at the beginning of this line to view this solution

    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.

Recent Arch Linux news:

PHP 8.0 and PHP 7 legacy packages are available

PHP 8.0 and PHP 7 legacy packages are available

2021-01-28 - Pierre Schmitz

The php package has been updated to version 8.0. Please refer to the upstream migration guide. As some applications are not compatible with PHP 8 yet we provide a php7 package which can be installed alongside version 8. Packages that depend on PHP reflect this update and will require php7 if needed. You might need to update your configuration accordingly. PHP 7 binaries and configuration have the “7” suffix:

  • /usr/bin/php → /usr/bin/php7
  • /etc/php → /etc/php7
  • /usr/bin/php-fpm → /usr/bin/php-fpm7
  • /usr/lib/systemd/system/php-fpm.service → /usr/lib/systemd/system/php-fpm7.service
  • /run/php-fpm → /run/php-fpm7

We also provide third party modules compiled for PHP 7:

Note that support for php7 will be limited and likely be dropped in about a year depending on how soon the majority of applications will be compatible with version 8.


Chromium losing Sync support in early March

Chromium losing Sync support in early March

2021-02-03 - Evangelos Foutras

Google has announced that they are going to block everything but Chrome from accessing certain Google features (like Chrome sync) starting on March 15. This decision by Google is going to affect Arch’s chromium package a bit earlier, on March 2, when Chromium 89 gets released.

We know for sure that data syncing will stop working (passwords, bookmarks, etc.). Other features such as geolocation or enhanced spell check might continue to function for a bit longer. Extensions integrating with Google Drive might misbehave and LibreOffice will lose access to documents stored there.

Other distros such as openSUSE and Fedora have already removed the soon-to-be-limited API keys from their Chromium 88 packages. Fedora’s advisory provides a great deal of perspective on this and I also found this Hackaday post to be quite informative.


Older Issues

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: https://forum.manjaro.org/c/support/Graphic-Cards/33 or look at our tutorial on compiling old Nvidia drivers.

For AMD GPU users having a black screen with kernel 5.10

Please click the ► at the beginning of this line to view more info

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

Please click the ► at the beginning of this line to view more info
  • 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.

You get [PKGNAME] warning: directory permissions differ on [Directory name]

followed by:

Filesystem: NNN package MMM

Please click the ► at the beginning of this line to view this solution
  • 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.


OpenVPN connection times out.

Workaround: donwgrade 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.

Gnome-shell-extension-pop-shell is currently incompatible with wayland

… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.

Corectrl is missing /usr/lib/libbotan-2.so.17.
Linked against /usr/lib/libbotan-2.so.18. Works
Might need a rebuild @nightmare-2021 ?
Thx in advance

1 Like

Rebuild (version 1.1.1-6 in unstable) is done


The “Maia transparent” theme kills Plasma tray and disables right click menu on the desktop. This theme was last updated 2 years ago. https://store.kde.org/p/1085371/

Other themes works fine.

1 Like

@nightmare-2021 on my GTX1650 I am not able to start SDDM anymore. I thought it was related to modeset, and I have disabled it by removing nvidia-drm.modeset=1 from the kernel line. I also removed everything related to fbcon and even vesafb.
The result is that the system starts with a very slow text console, and in the moment SDDM starts, it just hangs on a black screen.

From my journal:

Apr 22 22:49:16 <hostname> sddm[1309]: Initializing...
Apr 22 22:49:16 <hostname> sddm[1309]: Starting...
Apr 22 22:49:16 <hostname> sddm[1309]: Logind interface found 
Apr 22 22:49:16 <hostname> sddm[1309]: Adding new display on vt 1 ... 
Apr 22 22:49:16 <hostname> sddm[1309]: Loading theme configuration from ""
Apr 22 22:49:16 <hostname> sddm[1309]: Display server starting...
Apr 22 22:49:16 <hostname> sddm[1309]: Adding cookie to "/var/run/sddm/{a3235f7a-754f-4c9e-903a-3605868d1206}"
Apr 22 22:49:16 <hostname> sddm[1309]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{a3235f7a-754f-4c9e-903a-3605868d1206} -noreset -displayfd 17
Apr 22 22:49:16 <hostname> acpid[971]: client connected from 1312[0:0]
Apr 22 22:49:16 <hostname> acpid[971]: 1 client rule loaded
Apr 22 22:49:16 <hostname> kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000dffff window]
Apr 22 22:49:16 <hostname> kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs
Apr 22 22:49:20 <hostname> kernel: BUG: kernel NULL pointer dereference, address: 0000000000000170
Apr 22 22:49:20 <hostname> kernel: #PF: supervisor read access in kernel mode
Apr 22 22:49:20 <hostname> kernel: #PF: error_code(0x0000) - not-present page

And then I have to hard reset.

Could be this:

That is: drivers v465.24 do not work on Linux with “some monitors”…

@nightmare-2021 wouldn’t it be the case to offer the old nvidia drivers v460? I think v465 needs to be put aside until nvidia fixes it…

1 Like

This update broke my wifi connections, meaning, networkmanager was unable to connect to any network. It was constantly trying but without success.

I downgraded networkmanager to previous version, rebooted and wifi is working again.

Something seriously wrong happened to newest networkmanager.

1 Like

I’m the author of that theme. It seems to be working fine on my end after this update. Please, submit the bug on my github and we’ll see what is wrong. If needed, I’ll update the theme:

We downgraded the Nvidia driver back to 460.73.01 [production branch release]

Thanks :slight_smile:

Not that I’m concerned with that, but could someone shed some light on the reasons behind that? I mean are there any particular bugs with 465 driver version?

1 Like


Ok, but first, there are two versions ready to be installed. I tried to reinstall this plasma stlye. The first one fails because of missing meta informations.

I was able to install the second one, it did not killed the plasma tray, but there was no transparency anywhere. I think the 5.13+ is the newer version.