[Testing Update] 2026-04-23 - Kernels, Heroic Games Launcher, Mesa, Virtualbox, LXQt, COSMIC

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 April, beginning of May. 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.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

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

  • linux510 5.10.252
  • linux515 5.15.202
  • linux61 6.1.168
  • linux66 6.6.134
  • linux612 6.12.83
  • linux618 6.18.24
  • linux619 6.19.14 [EOL]
  • linux70 7.0.1
  • linux61-rt 6.1.167_rt62
  • linux66-rt 6.6.133_rt73
  • linux612-rt 6.12.79_rt17
  • linux617-rt 6.17.5_rt7

Package Changes (4/23/26 19:19 CEST)

  • testing core x86_64: 24 new and 24 removed package(s)
  • testing extra x86_64: 1612 new and 1715 removed package(s)
  • testing multilib x86_64: 5 new and 5 removed package(s)

A list of all 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:

4 Likes
[Testing Update] 2026-04-18 - KDE Gear 26.04, ROCm 7.2.2, Deepin, Haskell
[Testing Update] 2026-05-01 - Kernels (CVE-2026-31431), NVIDIA, LibreOffice, Mesa, Deepin
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-04-23

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:

1 Like
5

ISOs including this update can be found here: Release 202604231912 · manjaro/release-review · GitHub

1 Like
6

I recently had to replace the CMOS battery on my desktop (Asrock B550 Taichi). After doing so, I immediately installed the Linux 7.1 RC (linux71). Since then, at boot I’m getting two new messages, although everything seems to be working just fine.

The first:

Apr 23 18:50:45 manjaro kernel: virt/tdx: TDX not supported by the host platform
Apr 23 18:50:45 manjaro kernel: rtc_cmos PNP0B00:00: error -ENXIO: IRQ index 0 not found

The second:

Apr 23 18:51:20 NSR-Manjaro systemd-cryptsetup[985]: Cannot use device /dev/disk/by-uuid/d451c1ac-623e-45da-abd3-f9513f4cd1c5 which is in use (already mapped ormounted).
Apr 23 18:51:20 NSR-Manjaro systemd-cryptsetup[985]: Failed to activate with key file '/crypto_keyfile.bin': Device or resource busy
Apr 23 18:51:20 NSR-Manjaro systemd[1]: Failed to start Cryptography Setup for luks-d451c1ac-623e-45da-abd3-f9513f4cd1c5.

This refers to the partition containing root.

lsblk --output NAME,TYPE,UUID,FSTYPE,MOUNTPOINT                                                                                                  ✔
NAME                                          TYPE  UUID                                 FSTYPE      MOUNTPOINT
nvme0n1                                       disk
├─nvme0n1p1                                   part  90AC-55E7                            vfat
├─nvme0n1p2                                   part
├─nvme0n1p3                                   part  ab49b28e-6279-4c2b-aee3-7345a4727d8b BitLocker
├─nvme0n1p4                                   part  28DC2465DC242F8C                     ntfs
├─nvme0n1p5                                   part  CEAD-B4B0                            vfat        /boot/efi
├─nvme0n1p6                                   part  d451c1ac-623e-45da-abd3-f9513f4cd1c5 crypto_LUKS
│ └─root                                      crypt 8ed69b41-f1a4-4371-ad67-b818a65365c1 ext4        /
├─nvme0n1p7                                   part  11c72dfa-2d96-4fa6-a9e8-71652d1e9633 crypto_LUKS
│ └─luks-11c72dfa-2d96-4fa6-a9e8-71652d1e9633 crypt edb50610-7a53-476f-888c-8161b1f03c63 ext4        /Timeshift
└─nvme0n1p8                                   part  e0462f35-4da7-4d0f-b7e0-40ad5a181732 crypto_LUKS
└─luks-e0462f35-4da7-4d0f-b7e0-40ad5a181732 crypt d61fdf15-15bc-40d9-8a79-538829ddafef ext4        /Docs
nvme1n1                                       disk
└─nvme1n1p1                                   part  154ae411-7d0a-407d-aef3-ca9566e16b40 crypto_LUKS
└─luks-154ae411-7d0a-407d-aef3-ca9566e16b40 crypt 6a839ffa-6928-4f3c-a12d-723bcbf775e0 ext4        /MediaFiles

Other than taking a longer time (and many more iterations of the crypotography setup) there seem to be no ill effects. But if there are suggestions on how to make it happier, I’m happy to try them

7

It has nothing to do with changing your battery - I can assure you of that. I’ve had the same issue since upgrading to 7.1rc0. But I don’t feel like checking right now; everything’s working fine anyway.

2 Likes
8

I’m now running 7.1rc0, So far I’ve noticed no issues.

3 Likes
9

What we have in common is the motherboard manufacturer, Asrock.

Asrock B650M PG Lightning

1 Like
11

Heads up; AUR is having some issues right now…

AUR down?

4 Likes
12

on ASUS - issue too.

2 Likes
13

In the RSS feed, I see the update reported as 2026-12-23, which is clearly a typo. Maybe it has already been fixed and my reader still gets the wrong entry from some cache.

1 Like
14

I think the only way that changing a CMOS battery might “cause issues” would be if:

  1. The battery swap was “slow”, the on-board capacitors drained, and CMOS settings got reset.
  2. Depending how far away your CMOS settings were (and now are) from “defaults”, this could have a number of impacts (i.e. stability) if you weren’t able to recreate all the settings the way they were before.

But, if the battery swap was quick and CMOS settings were retained… things should as fine as they were before the swap.

15

That is “normal” on AMD machines, the first issue says that it cannot use intel-emu
(btw.: Intel inside - Idiot outside was a very old meme when using AMIGA)
The second issue is fixed with rc1.

16