[Testing Update] 2026-05-26 - Kernels, Thunderbird, Firefox, Pipewire, Gstreamer

Announcements Testing Updates
1

Hello Manjaro user community, here we have another set of package updates. We are continuing our development of the upcoming release of ‘Bian-May’ which can be expected end of June, beginning of July. Development speed may be a little slower the upcoming weeks. However, still let us know any issues you may found thus far.

Current Promotions

Recent News

New in Manjaro GNOME!

When choosing an accent color in Settings, the folder colors will now change automatically to match when using the Papirus Dark or Papirus Light icon theme.

To try it out, install gnome-shell-extension-papirus-folders-colorizer from Add/Remove Software, logout / login and enable Papirus Folder Colorizer from Extensions.

Or, if you prefer the command line:

Install:

sudo pacman -Syu gnome-shell-extension-papirus-folders-colorizer

Enable the extension:

 gnome-extensions enable papirus-folders-colorizer@NiffirgkcaJ.github.com

Logout:

gnome-session-quit --logout

Also, when applying accent colors from Layout Switcher settings, it will also set the matching folder color. Requires accent-color-change r172.c761c84-2 or newer.

KDE Plasma users with SDDM can now migrate to Plasma Login Manager

After ensuring plasma-login-manager 6.5.90-1 (or newer) is installed, run the following:

sudo pacman -Syu plasma-login-manager
systemctl disable sddm
systemctl enable plasmalogin
sudo pacman -R sddm-kcm sddm
NVIDIA 590 driver drops Pascal support

With the update to driver version 590, the NVIDIA driver no longer supports Pascal (GTX 10xx) GPUs or older.

Impact: Updating the NVIDIA packages on systems with Pascal, Maxwell, or older cards will fail to load the driver, which may result in a broken graphical environment.

Intervention required for Pascal/older users: Users with GTX 10xx series and older cards must switch to a legacy driver to maintain support:

  • Install the official linuxXXX-nvidia-575xx, linuxXXX-nvidia-570xx, or related DKMS packages.
  • Manjaro 26.1 Bian-May - Preview released
  • Manjaro 26.0 Anh-Linh released
  • Manjaro Summit public Alpha now available
  • As of Linux 5.4.302, the 5.4 series is now EOL (End Of Life). Please install 5.10 LTS (Long Term Support) or 5.15 LTS.
  • As of Linux 6.16.12, the 6.16 series is now EOL (End Of Life). Please install 6.18 LTS (Long Term Support) and/or 6.12 LTS.
  • As of Linux 6.17.13, the 6.17 series is now EOL (End Of Life). Please install 6.18 LTS (Long Term Support) and/or 6.12 LTS.
  • As of Linux 6.19.14, the 6.19 series is now EOL (End Of Life). Please install 7.0, and/or 6.18 LTS (Long Term Support) and/or 6.12 LTS.
Previous News
Finding information easier about Manjaro

Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: News – Manjaro

image
image679×348 45.7 KB

Notable Package Updates

  • Kernels got all updated
    • linux617-rt got removed
    • linux-firmware uses now zst compression
  • Firefox 151.0.1
  • Thunderbird 151.0
  • Fixes to gstreamer and pipewire
  • Updates to Deepin and Python

Additional Info

Python 3.14 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.13.so.

Print a list of of packages that have files in /usr/lib/python3.13/ :

pacman -Qoq /usr/lib/python3.13/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.13)

Use rebuild-detector to see if anything else needs to be rebuilt:

 checkrebuild

* It’s recommended to clean your build cache first with pamac clean --build-files

Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.

For help with AUR packages, please create a new topic in Support > AUR and a helpful volunteer may be able to assist you.

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

Our current supported kernels

  • linux61 6.1.174
  • linux66 6.6.141
  • linux612 6.12.91
  • linux618 6.18.33
  • linux70 7.0.10
  • linux71 7.1.0-rc5
  • linux61-rt 6.1.167_rt62
  • linux66-rt 6.6.135_rt74
  • linux612-rt 6.12.89_rt18

Package Changes (5/26/26 07:53 CEST)

  • testing core x86_64: 37 new and 39 removed package(s)
  • testing extra x86_64: 1826 new and 1898 removed package(s)
  • testing multilib x86_64: 5 new and 5 removed package(s)

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

2 Likes
[Testing Update] 2026-05-23 - Blender, Nvidia, Firefox, Thunderbird, Qt5
[404] not found error for package changes in stable update 2026-05-27
2

Known issues and solutions

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

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

Note: Do not forget to review your .pacnew files:

:arrow_right: 2026-05-26

2026-05-11

A week after Copy Fail, researcher Hyunwoo Kim disclosed a second Linux kernel flaw in the same broad area — IPsec ESP and rxrpc — that they have named Dirty Frag. The bug lives in the in-place decryption fast paths of esp4, esp6, and rxrpc: when a socket buffer carries paged fragments that are not privately owned by the kernel (e.g. pipe pages attached via splice(2)/sendfile(2)/MSG_SPLICE_PAGES), the receive path decrypts directly over those externally-backed pages, exposing or corrupting plaintext that an unprivileged process still holds a reference to.

Like the previous Copy Fail vulnerability, Dirty Frag immediately yields root on all major distributions. Every supported Manjaro release is affected. Dirty Frag chains two distinct kernel bugs, each with its own CVE: CVE-2026-43284 covers the IPsec ESP half (esp4 / esp6), and CVE-2026-43500 (NVD entry pending) covers the rxrpc half. Per Hyunwoo Kim’s public disclosure on oss-security (2026-05-07), the responsible-disclosure embargo was broken before distributions could coordinate, and a working exploit is publicly available. A second public exploit, Copy Fail 2: Electric Boogaloo, targets the same vulnerability under a different name; both reach root through the same esp4/esp6/rxrpc code paths and are blocked by the same fix.

Temporary mitigation

You can neutralize the attack surface by blacklisting the affected modules. None of esp4, esp6, or rxrpc are loaded on a typical workload that does not use IPsec transport mode or AFS, so on most systems this is safe to apply immediately:

sudo sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; true"

This writes a modprobe config that prevents the three modules from loading, and unloads them if they happen to be loaded already (the rmmod is best-effort and silent if the module isn’t present). To revert, remove /etc/modprobe.d/dirtyfrag.conf.

The Dirty Frag exploit works by corrupting page-cache pages of sensitive files (such as /etc/passwd or /usr/bin/su). If you suspect the system may have already been targeted before you applied the mitigation, drop the page cache so any tampered pages are evicted and the next read comes fresh from disk:

sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'

This is safe to run on a live system — it only frees clean cache and dentry/inode entries — and pairs well with the blacklist above.

2026-05-01

On 29 April 2026, a high local privilege escalation vulnerability in the Linux kernel, tracked as CVE-2026-31431 and named “Copy Fail”, was publicly disclosed. The vulnerability affects Manjaro Linux since 2017. A public proof-of-concept exploit has been released.

We have patched most of our kernels and released them to our testing and unstable branches:

  • patched kernels are: 5.10.254+, 5.15.204+, 6.1.170+, 6.6.137+, 6.12.85+, 6.18.22+, 6.19.12+, 7.0-rc7+
  • affected kernels are: 6.1.167_rt62, 6.6.133_rt73, 6.12.79_rt17, 6.17.5_rt7 and lower

Temporary Mitigation

Disable the algif_aead kernel module persistently on all affected systems until a patched kernel is available:

sudo su
echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
rmmod algif_aead 2>/dev/null || true
exit

More Information: CERT-EU - High Vulnerability in the Linux Kernel ("Copy Fail")

2026-04-06

udev-usb-sync and kernel 7.0-rc

If you experience slow transfers to USB attached disks, remove the package udev-usb-sync. It is not known why the 7.0-rc kernel causes this. There may be a regression of some sort. Awaiting the final release of the 7.0 kernel before jumping to conclusions.

See [Unstable Update] April 2026 thread for more info

2026-04-23T22:00:00Z
The issue is solved with the release of 7.0 kernel

Previous testing threads:

3

On one of the laptops, linux-firmware-meta (this package wasn’t on my desktop, also on Testing Branch) showed up as Orphaned via pamac after the update. I uninstalled it, then all the linux-firmware-xx packages showed up as Orphaned. :distorted_face: Feeling I shouldn’t reboot at this point, I installed the default linux-firmware package, all the other files vacated from Orphaned and rebooted without problem. OpenRazer 3.12.2 [included in this update] works fine with 7.1.0-rc5 although 3.12.3 was released 5 days ago to address an error with 7.1.0-rc4+ et alia Kernels.

[Stable Update] 2026-06-26 - Kernels, Systemd, PipeWire, NVIDIA, KDE, LibreOffice
Programs from the AUR that I haven't installed
Package not in AUR: linux-firmware-meta
4

It looks like linux-firmware now replaces linux-firmware-meta, however the package isn’t flagged as replacing linux-firmware-meta:

❯ pamac info linux-firmware
Name                  : linux-firmware
Version               : 20260519-1
Description           : Firmware files for Linux - Default set
URL                   : https://gitlab.com/kernel-firmware/linux-firmware
Licenses              : CC0-1.0
Repository            : core
Groups                : --
Depends On            : linux-firmware-amdgpu linux-firmware-atheros
                        linux-firmware-broadcom linux-firmware-cirrus
                        linux-firmware-intel linux-firmware-mediatek
                        linux-firmware-nvidia linux-firmware-other
                        linux-firmware-radeon linux-firmware-realtek
Optional Dependencies : linux-firmware-liquidio: Firmware for Cavium LiquidIO server adapters [Installed]
                        linux-firmware-marvell: Firmware for Marvell devices
                        linux-firmware-mellanox: Firmware for Mellanox Spectrum switches [Installed]
                        linux-firmware-nfp: Firmware for Netronome Flow Processors [Installed]
                        linux-firmware-qcom: Firmware for Qualcomm SoCs
                        linux-firmware-qlogic: Firmware for QLogic devices [Installed]
Provides              : --
Replaces              : --
Conflicts With        : --
Packager              : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date            : Wed 20 May 2026 10:22:54
Validated By          : MD5 Sum  SHA-256 Sum  Signature

I didn’t notice it when I updated as I removed linux-firmware-meta sometime ago so that I could remove linux-firmware-nvidia - the rest of my installed firmware packages I had already marked as explicitly installed, so nothing appeared in my orphans list.

Package not in AUR: linux-firmware-meta
Programs from the AUR that I haven't installed
[Stable Update] 2026-06-26 - Kernels, Systemd, PipeWire, NVIDIA, KDE, LibreOffice
5

linux-firmware-meta has been replaced by linux-firmware on unstable and testing branches, but has not been released to stable branch yet

Branch compare for Manjaro - linux-firmware
linux-firmware
    stable:    —
    testing:     20260519-1
    unstable:   20260519-1

linux-firmware-meta
    stable:      20260410-1
    testing:    —
    unstable:  —

https://termbin.com/bew3

                             PACKAGE           2026-05-23           2026-05-26
-------------------------------------------------------------------------------
                 linux-firmware-meta           20260410-1                    -

                      linux-firmware                    -           20260519-1
Package not in AUR: linux-firmware-meta
6 
sudo pacman -S linux-firmware $(pacman -Si linux-firmware | awk '/^Optional Deps/{flag=1; next} /^[A-Z]/{flag=0} flag' | awk -F: '{print $1}' | tr -d ' ')

will ask for:

:: linux-firmware-20260519-1 and linux-firmware-meta-20260410-1 are in conflict. Remove linux-firmware-meta? [j/N] j
1 Like
7

Manjaro previously had linux-firmware package overlays to support older kernels. That is no longer necessary, so they were dropped in favor of the original Arch packages.

linux-firmware is just a meta package to pull in all the firmware packages, so it can either be installed manually to replace linux-firmware-meta or the latter can be removed.

To mark the package(s) you want to keep as explicitly installed, use the Mark as explicitly installed button in Add/Remove Software or via CLI:

sudo pacman -D --asexplicit <package-name1> <package-name2>
3 Likes
Linux-firmware replaces linux-firmware-meta?
[Stable Update] 2026-06-26 - Kernels, Systemd, PipeWire, NVIDIA, KDE, LibreOffice
[Stable Update] 2026-05-27 - Kernels, NVIDIA, Firefox, Thunderbird, Mesa, Blender
Package not in AUR: linux-firmware-meta
Package not in AUR: linux-firmware-meta
Programs from the AUR that I haven't installed
Programs from the AUR that I haven't installed
8