[Testing Update] 2021-04-01 - Kernels, Gnome 40 Apps, Mesa 21.0.1, Kernels, Browsers

Hello community,

Another testing branch update with some usual updates for you.

The PinebookPro is back in Stock. Visit the Pine64 Store

  • We updated Gnome Apps to 40. Shell and extensions are kept at 3.38 series.
  • Most of our Kernels got updated
  • We updated pipewire, Wine and AMDVLK
  • Mesa is now at 21.0.1
  • 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.263
  • linux49 4.9.263
  • linux414 4.14.227
  • linux419 4.19.183
  • linux54 5.4.108
  • linux59 5.9.16 [EOL]
  • linux510 5.10.26
  • linux511 5.11.10
  • linux512 5.12-rc4
  • linux54-rt 5.4.106_rt54
  • linux59-rt 5.9.1_rt19

Packages Changes (Tue Mar 30 10:30:35 CEST 2021)

  • testing community x86_64: 1434 new and 1415 removed package(s)
  • testing core x86_64: 49 new and 49 removed package(s)
  • testing extra x86_64: 577 new and 738 removed package(s)
  • testing kde-unstable x86_64: 237 new and 236 removed package(s)
  • testing multilib x86_64: 37 new and 37 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.

Hello, after doing the upgrade I got no GUI; GDM stopped with the grey screen telling me to contact the system maintainer.
I had to rollback using timeshift as the error is the same that I had reportet in unstable thread:

Anyone got any idea what I should do?

pipewire no sound. removed garbage and installed pulseaudio

btw, gsd_housekeeping still core dumps after 6 months when /home is no atime partition

returned pipewire has to use pacnew conf files ; )
silly me, alway forgot to check


Try switching between ttys (Ctrl+Alt+F1/F2/F3 etc) - switching back to tty1 (that’s where gdm usually loads) gdm should show up again (at least that’s what did the trick for me as a workaround whenever gdm refused to load).

This may be fixed with gdm 40.0-1 (currently in unstable), although on the very first boot gdm chickened out again, but it didn’t happen again yet. I’m still suspicious though…

Nope - I switched TTYs a lot during recovery and trying to find a solution first. It did not recover even not if I killed it from TTY3 or ran it explicitely with sudo gdm from another TTY

No problem with i3 and no special GPU. Also, this was my first upgrade using pamac instead of pacman. It went perfect.

GreenWithEnvy’s fan curve graph has some rendering issues after this update

I did a rebuild, see if 0.15.2-2.0 helps. If not, it could be an issue with your application theme.

The Breath-Dark theme for GNOME/GTK applications seems to be the culprit.
I did the rookie mistake of not restarting the app after changing the theme :sweat_smile:

I’ll wait for the rebuild still.

Edit: Looks a bit better in Adwaita-dark, but still out-of-place. No update for me yet.

There is a downgrade for “Vivaldi”.?
Stable : 3.7.2218.52-1 Testing : 3.7.2218.49-1 Unstable : 3.7.2218.52-1
A few weeks ago the same on stable without real reason.

I’m on testing and vivaldi is showing 3.7.2218.52-1 for me

I got the update, but the background of the graph doesn’t change from white to dark grey when dark themes are used.
Probably something that has to be rectified by the application author?

Edit: A fix is coming.

Apparently the testing snap was taken before I pushed 3.7.2218.52-1. It’s updated (again) now.

1 Like

Having two issues here:

  1. Gnome-terminal is wonky. It has a completely transparent background and has “frames” inside it. Moving the terminal seems to visually overlay its window inside itself. Turning off “Use colors from system theme” eliminates this issue. I recall we had a similar problem a few months back with gnome-terminal that could be resolved the same way.

  2. Unable to log out of Gnome cleanly. When exiting I get the blinking underscore cursor in the upper left hand corner… that just keeps blinking forever. sudo killall gdm restarts the display without issues.

One note: I use Wayland for my Gnome session - I am not sure that effects anything.

Also, if I log into another window manager such as SwayWM, and attempt to open any Gnome apps like Nautilus or gnome-terminal, there is a long ~10 second delay before they start. This was not present before the update.

How did you fix this as I can’t seem to get any sound with pipewire now and it will not let me uninstall to try and fix it?

Just go to config dir and replace config files with pacnew versions.

1 Like

thank you very much all fixed :slight_smile:

I received these errors during the pacman-mirrors post-transaction hook.

(26/31) Configuring pacman-mirrors ...
::WARNING https://gitlab.manjaro.org 'HTTPSConnectionPool(host='gitlab.manjaro.org', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1123)')))'
::WARNING https://gitlab.manjaro.org 'HTTPSConnectionPool(host='gitlab.manjaro.org', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1123)')))'
::INFO Downloading mirrors from repo.manjaro.org
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 699, in urlopen
    httplib_response = self._make_request(
  File "/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 382, in _make_request
  File "/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 1010, in _validate_conn
  File "/usr/lib/python3.9/site-packages/urllib3/connection.py", line 411, in connect
    self.sock = ssl_wrap_socket(
  File "/usr/lib/python3.9/site-packages/urllib3/util/ssl_.py", line 428, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(
  File "/usr/lib/python3.9/site-packages/urllib3/util/ssl_.py", line 472, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.9/ssl.py", line 1040, in _create
  File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1123)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 755, in urlopen
    retries = retries.increment(
  File "/usr/lib/python3.9/site-packages/urllib3/util/retry.py", line 574, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='gitlab.manjaro.org', port=443): Max retries exceeded with url: /tools/maintenance-tools/manjaro-web-repo/raw/master/mirrors.json (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1123)')))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/pacman-mirrors", line 28, in <module>
  File "/usr/lib/python3.9/site-packages/pacman_mirrors/pacman_mirrors.py", line 101, in run
    httpFn.download_mirror_pool(config=self.config, tty=self.tty, quiet=self.quiet)
  File "/usr/lib/python3.9/site-packages/pacman_mirrors/functions/httpFn.py", line 193, in download_mirror_pool
    result = download_mirrors(config)
  File "/usr/lib/python3.9/site-packages/pacman_mirrors/functions/httpFn.py", line 59, in download_mirrors
    resp = requests.get(url=config["url_mirrors_json"],
  File "/usr/lib/python3.9/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/usr/lib/python3.9/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3.9/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python3.9/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python3.9/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='gitlab.manjaro.org', port=443): Max retries exceeded with url: /tools/maintenance-tools/manjaro-web-repo/raw/master/mirrors.json (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1123)')))
hint: use `pacman-mirrors` to generate and update your pacman mirrorlist.

Had to uninstall gdm3setup-utils (GitHub - Nano77/gdm3setup: An interface to configure GDM3, autologin options and change Shell theme) but that was probably overdue anyway.