[Testing Update] 2021-10-12 - Kernels, Haskell, Python, KDE Gear, KDE Frameworks, Thunderbird

Hello community,

Another testing branch update with some usual updates for you.

Don’t miss out on our new merch!

  • We updated our Kernels. Note that 5.13 series is marked EOL and 5.12 got removed!
  • Thunderbird is now at 91.2.0
  • KDE Gear got renewed to 21.08.2
  • KDE Frameworks is now at 5.87.0
  • Python and Haskell updates
  • Other regular upstream updates

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.288
  • linux49 4.9.286
  • linux414 4.14.250
  • linux419 4.19.210
  • linux54 5.4.152
  • linux510 5.10.72
  • linux513 5.13.19 [EOL]
  • linux514 5.14.11
  • linux515 5.15-rc3
  • linux510-rt 5.10.52_rt47

Package Updates (Tue Oct 12 10:03:53 CEST 2021)

  • testing community x86_64: 1524 new and 1490 removed package(s)
  • testing core x86_64: 21 new and 21 removed package(s)
  • testing extra x86_64: 555 new and 654 removed package(s)
  • testing kde-unstable x86_64: 381 new and 379 removed package(s)
  • testing multilib x86_64: 3 new and 3 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

New issues:

  • Nvidia drivers won’t work with GSync with some setups. It is known that some Monitors won’t work with the new 470.74 driver. We recommend to disable that feature for now, until Nvidia will fix it. They are tracking it via internal bug number 3382581.

  • 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. Due to protobuf update you may need to rebuild that package locally on your end. Compiz-easy-patch removed from repos

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

Older 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.

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.

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

Merch link doesn’t work.

link in OP is working now - https://manjaro.myspreadshop.net/

I had an issue after rebooting, I was greeted with a “Cannot load kernel modules” message, I then switched to a TTY and ran sudo pacman -Syyu and I had another update for all my kernels and headers and rebooting afterwards fixed the issue. I guess there was an issue that has been caught too late and new kernels got pushed shortly after.

Or not up-to-date mirrors :cowboy_hat_face:

I refresh mirror list, and force the Global mirrors so no I don’t think so.

sudo pacman-mirrors --country Global
sudo pacman -Syyu

Can’t give me outdated mirrors.

//EDIT: I got kernel updates initially too, so that tends to confirm my guess. No I got modules updates but I think the kernels were not pushed initially. That’s weird.
Maybe mirror wasn’t properly synced but pacman-mirror was seeing it as up to date so it’s weird.

It hasn’t been released yet. The release date is set to 2021-10-14. Then allow up to week or even more until it reaches Manjaro Testing.


Everything went fine.

Is it just me, or have mirrors been upgraded? The download speeds went sky-high. I have fiber-internet, but even with the best mirrors set, the download speeds were pretty limited. Today it was super quick, 1GB update downloaded in ca. 10s as if mirrors became much more efficient and the whole update processed in super speed. 1 minute and it was all over. Wow!

It depends on the mirror you have.

I got this error when applying this update.

error: failed to synchronize all databases (no servers configured for repository)

I don’t know exactly when the mirrors list got deleted, but it’s probably from the last update, because I don’t remember executing any elevated command between that update and this one. I just need to update the mirror, tho. There is no apparent changes to the URL from the newly downloaded mirrors list. But the fact that it got deleted is kinda weird. I hope it’s nothing to worry about. :sweat_smile:

OK found what I was looking at. “KDE Gear 21.08.2 will be released on October 7”.

3 posts were split to a new topic: Kde gear vs plasma release misunderstanding

inxi now gives an error when running inxi -Fxx with 2 or more of the “x” flag. It stops after displaying Bluetooth information and gives the error:

Not an ARRAY reference at /usr/bin/inxi line 16007.

If I just use inxi -F or inxi -Fx, it works as expected.

Edit: inxi -Fazy gives the same error.

It doesn’t for me.
If I’m reading the source correctly it’s got something todo with hardware raid info parsing (which my machine doesn’t have).
Better open up a bug report upstream:

1 Like

My system follows the stable branch, but I do like to peak here to see what’s on the horizon from time to time… and I recall inxi updated for me on the 11th to v3.3.07.1-1.

I understand my total installed package list is not in step, but on the off chance this is related to the same inxi version (unless another inxi version was released after the 11th)… I just wanted to share that I had no issues between the inxi -Fxx command (v3.3.07.1-1) and my mdadm array.

terminal results
$ inxi -Fxx
System:    Host: AM4-5600X-Linux Kernel: 5.14.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: KDE Plasma 5.22.5
           tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:   Type: Desktop System: Micro-Star product: MS-7C35 v: 2.0 serial: <superuser required>
           Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0 serial: <superuser required> UEFI: American Megatrends LLC.
           v: A.80 date: 01/22/2021
CPU:       Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache: L2: 3 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 88834
           Speed: 4360 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 4360 2: 2393 3: 3544 4: 2878 5: 2875
           6: 2886 7: 2202 8: 2198 9: 3023 10: 2862 11: 2878 12: 2877
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
           vendor: XFX Limited XFX Speedster MERC 319 driver: amdgpu v: kernel bus-ID: 2f:00.0 chip-ID: 1002:73bf
           Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: amdgpu,ati unloaded: modesetting,radeon
           alternate: fbdev,vesa resolution: 1: 2560x1440~144Hz 2: 2560x1440~144Hz s-dpi: 96
           OpenGL: renderer: AMD Radeon RX 6800 XT (SIENNA_CICHLID DRM 3.42.0 5.14.10-1-MANJARO LLVM 12.0.1)
           v: 4.6 Mesa 21.2.3 direct render: Yes
Audio:     Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel v: kernel bus-ID: 2f:00.1
           chip-ID: 1002:ab28
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
           v: kernel bus-ID: 31:00.4 chip-ID: 1022:1487
           Device-3: Corsair CORSAIR VIRTUOSO SE USB Gaming Headset type: USB driver: hid-generic,snd-usb-audio,usbhid
           bus-ID: 3-4:3 chip-ID: 1b1c:0a3d
           Sound Server-1: ALSA v: k5.14.10-1-MANJARO running: yes
           Sound Server-2: sndio v: N/A running: no
           Sound Server-3: JACK v: 1.9.19 running: no
           Sound Server-4: PulseAudio v: 15.0 running: yes
           Sound Server-5: PipeWire v: 0.3.38 running: yes
Network:   Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel port: f000 bus-ID: 27:00.0
           chip-ID: 10ec:8125
           IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: 2c:f0:5d:ae:5e:89
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:2 chip-ID: 8087:0029
           Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:      Device-1: md127 type: mdraid level: mirror status: active size: 7.28 TiB
           Info: report: 2/2 UU blocks: 7813893120 chunk-size: N/A super-blocks: 1.2
           Components: Online: 0: sdb1 1: sdc1
Drives:    Local Storage: total: 19.33 TiB used: 8.18 TiB (42.3%)
           ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB speed: 63.2 Gb/s lanes: 4
           serial: ######### temp: 40.9 C
           ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS100T3X0C-00SJG0 size: 931.51 GiB speed: 31.6 Gb/s lanes: 4
           serial: ######### temp: 37.9 C
           ID-3: /dev/nvme2n1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB speed: 63.2 Gb/s lanes: 4
           serial: ######### temp: 40.9 C
           ID-4: /dev/nvme3n1 vendor: Western Digital model: WDS200T2B0C-00PXH0 size: 1.82 TiB speed: 31.6 Gb/s lanes: 4
           serial: ######### temp: 31.9 C
           ID-5: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s serial: #########
           ID-6: /dev/sdb vendor: Western Digital model: WD80EFAX-68KNBN0 size: 7.28 TiB speed: 6.0 Gb/s serial: #########
           ID-7: /dev/sdc vendor: Western Digital model: WD80EFAX-68KNBN0 size: 7.28 TiB speed: 6.0 Gb/s serial: #########
Partition: ID-1: / size: 915.53 GiB used: 417.03 GiB (45.6%) fs: ext4 dev: /dev/nvme2n1p2
           ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme2n1p1
Swap:      ID-1: swap-1 type: file size: 38 GiB used: 5.8 MiB (0.0%) priority: -2 file: /swapfile
Sensors:   System Temperatures: cpu: 37.8 C mobo: N/A gpu: amdgpu temp: 46.0 C mem: 44.0 C
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:      Processes: 356 Uptime: 1d 14h 29m Memory: 31.27 GiB used: 6.88 GiB (22.0%) Init: systemd v: 249 Compilers:
           gcc: 11.1.0 Packages: pacman: 1404 Shell: Bash v: 5.1.8 running-in: konsole inxi: 3.3.07

I can’t reproduce it. Run inxi --recommends and see if you’re missing an optional dependency.

1 Like

This update appears to have introduced an issue regarding pci ports on my laptop.
Kernel 5.14, intel+nvidia hybrid, running optimus-manager + bbswitch switching. Nvidia module is unloaded, running only on intel graphics.

Anytime anything which requires hardware acceleration (mpv for example) is called, dmesg is spammed with

[  504.252426] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 1000 msec
[  504.252637] pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[  504.276581] pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[  504.295276] pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)

for a few seconds until system appears to “give up”. A hard-crash due to this has already occured during the playback of a long list of files.

PCI device 0000:00:1c.0 is, according to lspci, the Intel PCI bridge

00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)

This problem appears to go even further down, as any attempt to load the nvidia driver fails. Modprobe claims

modprobe: ERROR: could not insert 'nvidia': No such device

while journalctl logs

kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
kernel: NVRM: This is a 64-bit BAR mapped above 4GB by the system
        NVRM: BIOS or the Linux kernel, but the PCI bridge
        NVRM: immediately upstream of this GPU does not define
        NVRM: a matching prefetchable memory window.
kernel: NVRM: This may be due to a known Linux kernel bug.  Please
        NVRM: see the README section on 64-bit BARs for additional
        NVRM: information.
kernel: nvidia: probe of 0000:01:00.0 failed with error -1
kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).
kernel: NVRM: None of the NVIDIA devices were initialized.
kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 509

Any attempt to load the nvidia driver, either via optimus-manager or directly fails. Critical failure in optimus-manager appears to be due to the same issue, with logs outputting

Command 'modprobe nvidia NVreg_UsePageAttributeTable=1' returned non-zero exit status 1.

again a modprobe nvidia related issue.

Despite modprobing nvidia always failing with the specific error

modprobe: INFO: Failed to insert module '/lib/modules/5.14.11-1-MANJARO/extramodules/nvidia.ko.gz': No such device

modinfo returns the expected information

filename:       /lib/modules/5.14.11-1-MANJARO/extramodules/nvidia.ko.gz
firmware:       nvidia/470.74/gsp.bin
alias:          char-major-195-*
version:        470.74
supported:      external

As expected, Testing branch is once again left over. Testing of the package was done on Unstable and Stable-Staging, then pushed to Stable.

It’s been a recurring issue in the past months, updates are tested on Stable-Staging and not on Testing branch, then pushed to Stable, at some point Stable was more on par with Unstable branch than Testing. What are you doing guys, can you try to find out why this is regularly occurring and try to avoid that?

I want to stay on Testing branch but at some point if the update scheme makes no sense I’ll go back to Stable and forget about testing updates before they land to Stable…


I received an update today and:

error: failed to commit transaction (conflicting files)
hwinfo: /sbin exists in filesystem (owned by filesystem)
/usr/share/systemsettings/categories/manjaro-category.desktop exists in both 'manjaro-settings-manager-kcm' and 'manjaro-settings-manager-knotifier'
Errors occurred, no packages were upgraded.
 -> error installing repo packages