[Stable Update] 2025-12-15 - Kernels, NVIDIA, Plasma, Cosmic, Firefox

Hello community, here we have another set of package updates. Welcome to our new development cycle of Manjaro 25.1.0, code-named ‘Anh-Linh’.We will focus on Plasma 6.5 series and will introduce GNOME 49, maybe Cosmic 1.0 (Beta).

We managed to stabilize ‘Anh-Linh’ enough to release this update to our stable branch. However, users of Plasma and GNOME may lose their X11 session support. Therefore read our Known issues and solutions section before restarting your systems!

Current Promotions

Recent News

Valkey to replace Redis in the [extra] Repository

2025-04-17 - Andrew Crerar

Valkey, a high-performance key/value datastore, will be replacing redis in the [extra] repository. This change is due to Redis modifying its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024.

Arch Linux Package Maintainers intend to support the availability of the redis package for roughly 14 days from the day of this post, to enable a smooth transition to valkey. After the 14 day transition period has ended, the redis package will be moved to the AUR. Also, from this point forward, the redis package will not receive any additional updates and should be considered deprecated until it is removed.

Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes.

Arch Linux - News: Valkey to replace Redis in the [extra] Repository

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

  • Kernels got updated
  • NVIDIA 580.119.02
    • current 580xx driver seems to be super unstable. Users who face issues are recommended to report to NVIDIA and may want to switch to the older 575xx driver via mhwd. You’re been warned …
  • COSMIC Epoch 1
  • KDE Gear 25.12
  • KDE Plasma 6.5.4
  • Firefox 146.0 and 147.0b1
  • Updates to Deepin, Python and Haskell

Additional Info

Python 3.13 info

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

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

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

Rebuild them all at once:*

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

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.

ISOs including this update can be found here:

Anh-Linh 25.1-pre2 (2025-12-15)

  • TBD

Our current supported kernels

  • linux54 5.4.302 [EOL]
  • linux510 5.10.247
  • linux515 5.15.197
  • linux61 6.1.159
  • linux66 6.6.119
  • linux612 6.12.62
  • linux617 6.17.12
  • linux618 6.18.1
  • linux61-rt 6.1.158_rt58
  • linux66-rt 6.6.119_rt67
  • linux612-rt 6.12.57_rt14
  • linux617-rt 6.17.5_rt7

Package Changes (12/12/25 17:36 CET)

  • stable core x86_64: 20 new and 20 removed package(s)
  • stable extra x86_64: 936 new and 1069 removed package(s)
  • stable multilib x86_64: 7 new and 7 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:


3 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable 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:

:warning: Prepare the update beforehand

Preparation steps

From [INFO] Stable branch - BIG update BEST practice

  1. Create a list of custom packages for later reference
pamac list --foreign > ~/alien-pkgs.txt
  1. Remove all foreign packages
pamac remove $(pamac list --foreign --quiet)
  1. Remove all orphans and other unneeded packages
pamac remove --orphans --unneeded
  1. Run a simulated update
pamac update --dry-run
  1. Looking good? Repeat the above without --dry-run
reboot
  1. Consult the list of packages created in the first step and rebuild only those you really need

good morning!

I’ve tried pacman -Syu and got notification, that I can not update as nvidia package is in conflict with other nvidia that uses some library,

I just wanted list of packages without updating, as I had to go to work

through pamac I’m sure it’ll be solved

I’ll check in the afternoon, when I return from work :slight_smile:

Have a nice day everyone !

If all you want is a list

checkupdates

will provide a list without updating metadata

Also be sure to prepare your system for the update.

So far, I haven’t encountered any problems.

As a preventive measure, I run the following after a major update, but definitely after a Plasma update:

rm -rf ~/.cache/* ; QT_LOGGING_RULES="*.debug=true" kbuildsycoca6 --noincremental

This has saved me a lot of trouble. After booting, journalctl only showed the usual suspects.

1 Like

are you referring to removing all AUR packages before upgrade? is this the “new way” we should do things here or one time thing hopefully? :face_with_spiral_eyes:

1 Like

It is just best practise - you can do as you see fit - you are the sysadmin.

Custom package(s) will always be a joker - with the possibility of making the update run sideways - thus best practise is to remove them from the equation.

With the last update I saw a topic where the member ran into an hour-long rebuild of a qt5 package that was moved to AUR.

But if you are sure your custom packages are safe, by all means, you are the local system administrator.

The recommendation was behind a disclosure element in Stable Update 2025-12-08 – judging by some of the issues (post-update) few bothered to “click the dropdown” – now, it’s more obvious.

Hopefully these preparation steps will be observed by those who need them the most.

This kind of preparation has been unofficially suggested for a long time, but for those who can’t (or won’t) perform regular maintenance, steps such as these can be vital to update success.

1 Like