[Testing Update] 2021-02-24 - Kernels, Plasma 5.21.1, Frameworks 5.79, Firefox, Thunderbird, Python

Hello community,

Another testing branch update with some usual updates for you.

Get your Plasma desktop updated to the lastest stable release! #stayhome, #staysafe, #stayhealthy

  • Most of the Kernels got updated
  • Firefox is now at 86.0
  • Thunderbird got updated to 78.8.0
  • For fans of KDE Software we have now Plasma 5.21.1 and Frameworks 5.79 added to our repos!
  • Other regular upstream updates including python and haskell

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You can also help us with the Stable-Review images, so the upcoming installer ISOs are solid for Newcomers!

Our current supported kernels

  • linux44 4.4.258
  • linux49 4.9.258
  • linux414 4.14.222
  • linux419 4.19.177
  • linux54 5.4.100
  • linux59 5.9.16 [EOL]
  • linux510 5.10.18
  • linux511 5.11.1
  • linux54-rt 5.4.93_rt51
  • linux59-rt 5.9.1_rt19

Packages Changes (Wed Feb 24 11:47:21 CET 2021)

  • testing community x86_64: 1410 new and 1388 removed package(s)
  • testing core x86_64: 50 new and 49 removed package(s)
  • testing extra x86_64: 574 new and 611 removed package(s)
  • testing kde-unstable x86_64: 281 new and 253 removed package(s)
  • testing multilib x86_64: 27 new and 27 removed package(s)

A detailed list of all package changes can 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

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: 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

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.

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

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.

No issues (KDE), except for one widget (memory) that has vanished from the panel and a text change from upstream in another one (“Usage” instead of “CPU core #” something).

have a choice depot
between glfw-x11 and glfw-wayland
( applied X11 as Xfce )

1 Like

No issues here,after update ithe firewall entry on plasma settings was not there, I needed to install plasma-firewall with ufw or firewalld. :+1:

The new system monitor on KDE was missing, had to install it manually. Otherwise seems fine.

package name?


1 Like

I had the following errors show in my log:

kwin_x11[912]: kwin_xkbcommon: XKB: Couldn't process include statement for 'gb(\0)'
kwin_x11[912]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
kwin_x11[912]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
kwin_x11[912]: kwin_xkbcommon: XKB: Failed to compile keymap

fixed by editing ~/.config/kxkbrc and changing VariantList=\\0 (an incorrect value?) to VariantList=basic.


No issues so far on cinnamon :+1::+1:

New KDE crashed during loading but then I remembered I was using kwin-lowlatency from aur. Changed that for the standard version and all was well.

Kde-Plasma5.21.1,no problems. Everything is running well so far.
System monitor is available for me. runs.

Kernel 5.11.1-1 ,just installed, so far all good.
No problems detected yet.

Looks like everything here went smooth :slight_smile:

Seems good.

Installed the new plasma-system-monitor and plasma-firewall, cool additions.

On a side note, the new KDE application menu is garbage to me. Why did they do that?!! Very unhappy for that. If there is a way of having the old one back… I would be pleased.

//EDIT: seems like I have a solution, will read and report Plasma 5.21 - KDE Community

If you prefer the old Kickoff app launcher however, it is only few clicks away in KDE’s software store.

//EDIT2: installed ocs-url, and then clicked install on the KDE Store page for Legacy Kickofff application menu, and I could switch to the old application menu. Perfect.


Only issues I’ve noticed so far have been cosmetic.

Having all the appearance settings under a sub-menu is nice, but the lack of the section title looks like something’s missing:

The screen orientation example icons have turned into blank file icons:

1 Like

It doesn’t even have an empty category for me, in French, it took me 3 minutes to find it:

It is above everything, very top left…

Kernel 5.11.1-1 does not report temperature, fanspeed, clocks etc. for my 6800XT GPU. Rc 7 and current 5.10.18-1 do. Switched Kernel so all is well for now.
New Powerdevil 5.21.1 seems to be blocking shutdowns/restarts for me since the process cannot be stopped. Switching back to 5.20.5 resolved that problem.
Otherwise all is well.

Installation all went well. Only thing that I noticed was that the Icon-Only icons became large again after this update. I believe that in the 5.20 update they were made smaller and had padding around them which looked quite clean but that seems to have disappeared for me now.

A post was split to a new topic: After update it appears my system hang


update went well with no issues on plasma(and related) stacks.

only issue i did find was pipewire-media-session crashing. logs;


kernel: pipewire-media-[1244]: segfault at 10 ip 000055d40e54603b sp 00007ffe5060c700 error 4 in pipewire-media-session[55d40e532000+29000]
kernel: Code: 51 48 8d 5c 24 30 48 8d 15 c6 68 01 00 41 89 4c 24 10 31 c0 be 40 00 00 00 48 89 df ff 15 a5 db 02 00 49 8b 45 10 48 8b 50 38 <48> 8b 42 10 48 85 c0 74 1f 48 8b 40 10 48 85 c0 74 16 48 8b 7a 18
kernel: audit: type=1701 audit(1614220831.882:108): auid=1000 uid=1000 gid=1000 ses=3 pid=1244 comm=“pipewire-media-” exe="/usr/bin/pipewire-media-session" sig=11 res=1

systemd[1]: Started Process Core Dump (PID 1253/UID 0).
audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@0-1253-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
kernel: audit: type=1334 audit(1614220832.069:109): prog-id=15 op=LOAD
kernel: audit: type=1334 audit(1614220832.069:110): prog-id=16 op=LOAD
kernel: audit: type=1130 audit(1614220832.069:111): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-coredump@0-1253-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
systemd-coredump[1254]: Process 1244 (pipewire-media-) of user 1000 dumped core.

   Stack trace of thread 1244:
   #0  0x000055d40e54603b n/a (pipewire-media-session + 0x2003b)
   #1  0x000055d40e544a6b n/a (pipewire-media-session + 0x1ea6b)
   #2  0x00007fb132adedf4 n/a (libpipewire-module-protocol-native.so + 0x16df4)
   #3  0x00007fb132ad8aa2 n/a (libpipewire-module-protocol-native.so + 0x10aa2)
   #4  0x00007fb132ad8ff8 n/a (libpipewire-module-protocol-native.so + 0x10ff8)
   #5  0x00007fb13bbccd9b n/a (libspa-support.so + 0x6d9b)
   #6  0x00007fb13bb415ab pw_main_loop_run (libpipewire-0.3.so.0 + 0x425ab)
   #7  0x000055d40e5327dc n/a (pipewire-media-session + 0xc7dc)
   #8  0x00007fb13b804b25 __libc_start_main (libc.so.6 + 0x27b25)
   #9  0x000055d40e532c5e n/a (pipewire-media-session + 0xcc5e)
   Stack trace of thread 1252:
   #0  0x00007fb13b8dc39e epoll_wait (libc.so.6 + 0xff39e)
   #1  0x00007fb13bbd61f1 n/a (libspa-support.so + 0x101f1)
   #2  0x00007fb13bbccd04 n/a (libspa-support.so + 0x6d04)
   #3  0x00007fb13bb27f50 n/a (libpipewire-0.3.so.0 + 0x28f50)
   #4  0x00007fb13b9b3299 start_thread (libpthread.so.0 + 0x9299)
   #5  0x00007fb13b8dc053 __clone (libc.so.6 + 0xff053)