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. Since only two day’s of 2025 are left, we may bump the version of ‘Anh-Linh’ also to 26.0 …
Current Promotions
Get the latest Gaming Laptop by Slimbook powered by Manjaro: Slimbook Manjaro III
Protect your personal data, keep yourself safe with Surfshark VPN: See current promotion
Recent News
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.
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 stable and/or 6.12 LTS (Long Term Support).
As of Linux 6.17.13, the 6.17 series is now EOL (End Of Life). Please install 6.18 stable and/or 6.12 LTS (Long Term Support).
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.
Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering 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 conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
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
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
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.
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 or Maxwell cards will fail to load the driver, which may result in a broken graphical environment.
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.
mhwd now support multiple profiles which should also help in a more automatic way to choose the proper driver for your NVIDIA card.
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.
the problem with xfce compositing introduced in nvidia 580.119 still exists in nvidia 590.48. fortunately it’s easy to work around by disabling compositing in settings > window manager tweaks. this issue has been given an nvidia internal tracking number: 5758240
this is NOT a soluce to says , it not a NVIDIA driver bug but one Xfce Bug !
if they have frozen code from 580 series 105 ( just before 119) , Xfce & X11 will still working for part closed / legacy source.
you have not read all others reports bugs from december 11 , there are many others that are not fixed with this 580 series.
for maxwell and pascal ( series 750 , 900 , 1000 and mobile )
we should have a legacy ( closed source) with NO drivers nvidia-open things
that why version mhwd 570xx and 575xx cant work because on install , nvidia-open come with , and then no more drm , udm nvidia module part are installed here by the script , there will be no module working with kernel
for the others video cards : ==> nvidia-open drivers with wayland.
Since I have a NVIDIA 1060, I had to stay away from the nvidia-590-Update, but unfortunately, even 570 and 575 led into a black screen without graphical output after boot.
(installed both in a terminal boot and error messages appeared: nvidia_drm could not be added.)
Installed nvidia-580xx-dkms and got a system with working graphical output again … guess, I need a new graphics card soon.
just for your info , there is still 5% that use a maxwell or pascal GPU nvidia cards on Steam survey.
so why version mhwd 470 & 570 & 575 cant work with theses cards ?
mhwd only detects the hardware based on a database and then installs drivers via pacman based on the profile suggested.
If a module cant be loaded, there might be an issue with the pre-compiled one. You can remove it and try with its dkms version instead. That is used when pre-compiling.
580xx is generally super broken but currently the production driver series by Nvidia. We currently rethink if a rolling Nvidia driver makes even sense or if it is better to tag each version and the user has to manually upgrade driver series similar as we do with kernels. That we had in the past already.
I logged in with the Manjaro Live installer, but I couldn’t access the Manjaro forum because I kept getting an error, so I couldn’t say anything else. I was forced to do a new reinstallation with a new version of Manjaro. However, I already had certain problems with the zoom windows, or the terminal, and even the bottom bar of Manjaro disappearing and reappearing constantly.
I like the rolling approach but maybe it should be rolling only within one major version number such that the user has to choose that but then get updates within it but never gets a version bump?
That’s the very definition of a point-release distribution. Manjaro is not that, even though we do have the Manjaro Summit branch, which is an immutable distribution — and which still requires more people to test it.
Well we had that approach exactly in the past. When a user installed with 570xx drivers updates within that driver series he would get. Similar as like a kernel series, lets say linux612.
When a new series like 575xx would be available the user would need to explicitly choose that driver series to get updates wothin that series.
However nvidia managed to release also regressions within a driver series so that version locking is needed. That a Debian based distribution would offer:
Oddly the branch name per packages gets there dropped, which we did already for the rolling Nvidia packages…
You will need to rebuild any AUR Python packages that install files to site-packages or link to 
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.
2025-12-29
