[Testing Update] 2026-03-11 - Kernels, Plasma, KDE Gear, COSMIC, NVIDIA, LibreOffice

Hello community, here we have another set of package updates. This might mark most likely the last 26.0.4 update for Anh-Linh release series. Let us know if you see some issues with those package updates.

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

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.165
  • linux66 6.6.128
  • linux612 6.12.75
  • linux618 6.18.16
  • linux619 6.19.6
  • linux70 7.0.0rc3
  • linux61-rt 6.1.164_rt60
  • linux66-rt 6.6.127_rt69
  • linux612-rt 6.12.74_rt16
  • linux617-rt 6.17.5_rt7

Package Changes (3/11/26 19:36)

  • testing core x86_64: 93 new and 182 removed package(s)
  • testing extra x86_64: 3294 new and 3470 removed package(s)
  • testing multilib x86_64: 46 new and 49 removed package(s)

Overlay Changes

  • testing core x86_64: 3 new and 1 removed package(s)
  • testing extra x86_64: 70 new and 5 removed package(s)

More details about the 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:


1 Like

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-03-11

2025-12-29

NVIDIA 590 driver drops Pascal and Maxwell support

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

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

Intervention required: Switch to a legacy driver to maintain support:
Install the official linuxXXX-nvidia-575xx, linuxXXX-nvidia-570xx, or related DKMS packages. You can use nvidia-driver-assistant to figure out which driver would support your hardware best.

2025-12-09

.NET packages may require manual intervention

2025-12-11 - George Rawlinson

The following packages may require manual intervention due to the upgrade from 9.0 to 10.0:

  • aspnet-runtime
  • aspnet-targeting-pack
  • dotnet-runtime
  • dotnet-sdk
  • dotnet-source-built-artifacts
  • dotnet-targeting-pack

pacman may display the following error failed to prepare transaction (could not satisfy dependencies) for the affected packages.

If you are affected by this and require the 9.0 packages, the following commands will update e.g. aspnet-runtime to aspnet-runtime-9.0:

pacman -Syu aspnet-runtime-9.0

pacman -Rs aspnet-runtime

Arch Linux - News: .NET packages may require manual intervention

2025-11-10

mkinitcpio v40 disabled fallback image creation for new installs

mkinitcpio v40, packaging changes and kernel-install - Arch-dev-public - lists.archlinux.org
This is only affects new installs as we can’t change the hook files on existing installs.

To disable fallback image creation on older installed systems

  • Change PRESETS=('default' 'fallback') line to PRESETS=('default') in the respective .preset files in /etc/mkinitcpio.d/.
  • Regenerate initramfs - sudo mkinitcpio -P
  • Update boot loader - sudo update-grub

Warning
Disabling all fallback initramfs generation will deprive you of another option to boot into the system in case a default initramfs fails. Before proceeding, make sure you have a bootable installation medium for rescue purposes on hand.

Previous testing threads:

I ask for forgiveness if it’s not the right venue for this question, but do you have a notion of when the mesa will get updated? I have an OpenGL crash with a game that doesn’t occur with mesa-devel, so I’m curious.

Thank you for your work, in any case.

You mean the game started failing after you updated with the version included in this update?

No, it already crashed before. It’s not specific to this update - but on the last testing update, it happened, and didn’t if I used the locally compiled mesa-devel.

Since it’s not reproducible on demand, I can’t test it right away, but from what I gathered, it’s most probably related to the mesa package/kernel version. I had kernel 6.19, and the Mesa 25.3.5.

It didn’t happen on Mesa 26.1.0 (the devel version, if I remember correctly) so as the next version to be distributed is by Arch is the 26.0, I’m curious to see if it crashes again (and eager, but that’s not very relevant :p).
I have changed the kernel to 7.0, for that same reason.

EDIT : I’m sorry to waste your time - I see that the mesa has been updated. I must have missed the line in the log. Happy to be able to test it out!

This is the first update I have done with the GTK4 version of pamac-manager, and it crashed d my system, taking me out to the Grub Boot Menu.

Fortunately, in my case, grub config had already been updated, so a simple reboot was all that was required.

Other than some minor issues with my local config settings, everything is back and working.

Just now Booted into the copy of Testing I have on a USB (Same Hardware, other than running of USB SSD). Ran the update with the old GTK3 version of pamac-manager. No update issues… as usual.

I suspect all the Pamac issues are with the GTK4 Version.

The plasma-desktop package seems to be missing from this update - it is no longer in the Testing repos:

mbn info plasma-desktop -q
Branch         : archlinux
Name           : plasma-desktop
Version        : 6.6.2-1
Repository     : extra
Build Date     : Wed 04 Mar 2026 08:26:01 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : unstable
Name           : plasma-desktop
Version        : 6.6.2-1
Repository     : extra
Build Date     : Wed 04 Mar 2026 08:26:01 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : stable
Name           : plasma-desktop
Version        : 6.5.5-1
Repository     : extra
Build Date     : Wed 14 Jan 2026 07:11:15 
Packager       : Tomaz Canabrava <tcanabrava@archlinux.org>

Seeing the message that it was now an orphaned package had me scratching my head, however I made the silly assumption that maybe its functionality had been merged into another part of Plasma (possibly plasma-workspace), so I took the risk of removing it after the update:

[2026-03-12T08:11:46+1100] [ALPM-SCRIPTLET] foreign     plasma-desktop
[2026-03-12T08:15:03+1100] [ALPM] removed plasma-desktop (6.5.5-1)

Of course, my assumption was wrong. When I rebooted, I ended up with a black desktop.

I resolved the situation by switching to a TTY & installing the plasma-desktop v6.5.5 package stored in the cache:

sudo pacman -U /var/cache/pacman/pkg/plasma-desktop-6.5.5-1-x86_64.pkg.tar.zst
[2026-03-12T08:30:04+1100] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/plasma-desktop-6.5.5-1-x86_64'
[2026-03-12T08:30:19+1100] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/plasma-desktop-6.5.5-1-x86_64.pkg.tar.zst'
[2026-03-12T08:30:24+1100] [ALPM] installed plasma-desktop (6.5.5-1)

I now have a desktop again.

2 Likes

It seems there were several failures in @philm’s Plasma 6.5.6 CI run.

1 Like

Bluez 8.86-4 is buggy too.

I’m not too surprised. After all, the Plasma 6.5.6 bugfix release was out only a couple of days ago. So, in this case, it has gone from Arch straight into Testing branch, bypassing Unstable branch (which is now on Plasma 6.6).

1 Like

To be clear, Phil built 6.5.6 independently, hence the CI run. Arch went from 6.5.5 to 6.6.0 a few weeks ago. 6.6.2 is currently in Arch stable & Manjaro unstable.

1 Like

Could someone clarify what this means for a Manjaro testing KDE user today? Should one skip this update for now?

1 Like

Best would be to wait until @philm has managed to sort things out. He’ll post here on the thread when he’s taken care of it.

4 Likes

Since this is testing, Manjaro could follow Arch and include Plasma 6.6.2 in this update.

2 Likes