![[keyword]](https://learnxyz.in/wp-content/uploads/2026/02/Test-Update-2026-01-03-COSMIC-101-Budgie-NVIDIA-Driver-Assistant.jpeg)
Hello Manjaro user community, here we have another set of package updates. We are continuing our development of the upcoming release of ‘Bian-Mei’ which can be expected at the end of April, beginning of May. Development speed may be a bit slower in the coming weeks. However, still let us know any issues you have found so far…
Current promotions
Recent News
New in Manjaro GNOME!
When an accent color is selected in Settings, the folder colors will now automatically change to match when using the Papirus Dark or Papirus Light icon theme.
Install to try it gnome-shell-extension-papirus-folders-colorizer from Add/Remove Software, sign out / sign in and activate Papirus Folder Colorizer from extensions.
Or, if you prefer the command line:
Install:
sudo pacman -Syu gnome-shell-extension-papirus-folders-colorizer
Activate the extension:
gnome-extensions enable papirus-folders-colorizer@NiffirgkcaJ.github.com
Sign out:
gnome-session-quit --logout
Also, when applying accent colors from Layout Switcher settings, it will also set the matching folder color. Require accent-color-change r172.c761c84-2 or newer.
KDE Plasma users with SDDM can now migrate to Plasma Login Manager
After the insurance 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 not load the driver, which may result in a broken graphics environment.
Intervention required for Pascal/older users: Users with GTX 10xx series and older cards should switch to a legacy driver to retain support:
- Install the official
linuxXXX-nvidia-575xx,linuxXXX-nvidia-570xxor 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
- Roman was there Froscon and has a talking about Manjaro
- Initial preview of Manjaro Immutable is now available!
- Novel we published new website
- Philip was at Computex and had the OrangePi Neo
- Manjaro team member @romang has a new library project with a guest post on it Phoronix.
- Some Manjaro team members attended FOSDEM 2024 and we displayed a prototype of the upcoming Orange Pi Neo Handheld Gaming Console!
- Check out the new Manjaro Slimbook Hero!
- Manjaro, like many other open source projects, relies on the generosity of its community donations and corporate sponsorships to support its growth and development. This donations is essential to cover the various expenses incurred in the operations of the project, such as server costs, software development tools, infrastructure expenses, training, flying people to events or events conferences and the salaries of key developers. With the help of these donations, Manjaro is able to ensure the necessary financial stability that allows the project to constantly improve and remain active. If you like Manjaro, consider it donate!
- As you may have seen, some of our team were able to attend FOSDEM 2023 and the conference was incredibly productive for us. See our blog post for more.
- Arch Linux and Manjaro on TUXEDO PCs – Arch Linux and Manjaro on TUXEDO PCs – TUXEDO PCs
- Linux, Judo, unicycles and… Baywatch?! How Vivaldi and Manjaro aim above the ordinary. | Vivaldi browser
- https://frame.work/blog/spotlight-on-manjaro-linux-interview-with-the-team
Find information about Manjaro more easily
Finding information about Manjaro more easily has always been a topic that needed solving. With our new search, we’ve put all Manjaro data accessible in one place and divided it by sections to make it easier to digest: News – Manjaro
Notable package updates
Additional information
Python 3.14 information
You will need to rebuild any AUR Python packages that install or link files to site packages libpython3.13.so.
Print a list of packages that have files in them /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 rebuilding:
checkrebuild
* It is recommended to first clean your build cache with pamac clean --build-files
Information about AUR packages
AUR (Arch User Repository) packages are not supported by Arch or Manjaro. Posts about them Announcements topics are off topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic 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 from 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 (23/04/26 19:19 CEST)
- test kernel x86_64: 24 new and 24 removed package(s)
- test extra x86_64: 1612 new and 1715 removed package(s)
- test multilib x86_64: 5 new and 5 removed package(s)
A list of all changes can be found here
- No problem, everything went smoothly
- Yes there was a problem. I was able to solve it myself.(Please post your solution)
- Yes, I am currently experiencing a problem due to the update. (Please post about it)
Check if your mirror has already synced:
4 Like
Know problems and solutions
This is a wiki post; please edit as needed.
Please consider subscribing to the Test Updates announcements RSS feed
Please RTFT (Read this fine thread) first before reporting the same issues over and over again!
Note: Don’t forget to review you .pacnew files:
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 some kind of regression. Wait for the final release of the 7.0 kernel before jumping to conclusions.
See (Unstable update) April 2026 thread for more information
2026-04-23T22:00:00Z
The issue is resolved with the release of 7.0 kernel
Previous Test Threads:
1 Like
ISOs including this update can be found here: Release 202604231912 · manjaro/release-review · GitHub
1 Like
I recently had to replace the CMOS battery on my desktop (Asrock B550 Taichi). After doing this, I immediately installed the Linux 7.1 RC (linux71). Since then, on startup I get two new messages, although everything seems to be working 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.
It 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 cryptography setup), there appear to be no ill effects. But if there are suggestions on how to make it happier, I’m happy to try
It has nothing to do with changing your battery – I can assure you of that. I had the same problem since upgrading to 7.1rc0. But I don’t feel like checking now; everything works fine anyway.
2 Like
I’m using 7.1rc0 now, so far I haven’t noticed any problems.
3 Like
What we have in common is the motherboard manufacturer, Asrock.
Asrock B650M PG Lightning
1 Like
Head up; AUR is currently having some issues…
AUR off?
4 Like
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 is still getting the wrong entry from some cache.
1 Like
I think the only way changing a CMOS battery could “cause problems” would be if:
- The battery change was “slow”, the onboard capacitors were draining, and CMOS settings were reset.
- Depending on how far your CMOS settings were (and now are) away from “default”, this could have a number of impacts (eg stability) if you couldn’t recreate all the settings the way they were before.
But if the battery swap was quick and CMOS settings were kept…things should be as good as before the swap.
This is “normal” on AMD machines, the first issue says that it can’t use Intel emu
(btw.: Intel inside – Idiot outside was a very old meme when AMIGA was used)
The second problem is solved with rc1.
