As of Linux 6.14.11, the 6.14 series is now EOL (End Of Life). Please install 6.15 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 AUR and a helpful volunteer may be able to assist you.
Warning: ksystemstats: local (6.4.0-1) is newer than extra
If you get this warning, run the following command…
sudo pacman -Syuu
VLC does not play (certain) videos
For this update, the VLC packages were split up, and not all codecs may be installed on your system. You can install the additional codecs individually, or install the vlc-plugins-all meta-package, which will pull in all available plugins.
sudo pacman -S vlc-plugins-all
2025-06-19
Possible breaking changes to pacman-mirrors
With pacman-mirrors 5.0-1, the global mirrors.json data file has been moved from /usr/share/pacman-mirrors to /var/lib/pacman-mirrors. This move introduce a possible breaking change if you have custom scripts relying on the mirrors data file. The moving of the file is the only change and has been made to make it possible for users to have their /usr-tree on a separate read-only partition or btrfs subvolume.
Updated, but it wasn’t smooth. The Grub update was problematic. Needed a recovery USB to repair it - based on that experience I’d strongly recommend anyone yet to update to make sure you’ve got a recovery USB to hand! Despite all that, grateful for the update, thank you!
Anything from logs might be able to help others? Update went smooth on my desktop and another laptop. I’ve only had to do that recently after updating the BIOS and having to reinstall GRUB
upgrade was mostly fine. I updated the last 3-4 weeks of testing releases in one batch.
Only issue I have seen so far was mhwd looking for an old libhd.so file. I reinstalled using pacman but that didn’t fix it. I then added a symlink /usr/lib/libhd.so.24 -> /usr/lib/libhd.so.25.0, which appears to have resolved it for now. May be an issue with my setup but figured I’d post here in case others run into the same problem.
mhwd version: v0.6.6-4
hwinfo version: 25.0-1
Exact error was: mhwd: error while loading shared libraries: libhd.so.24: cannot open shared object file: No such file or directory
The actual error that greeted me at boot was “grub is using legacy shim lock protocol not found”. I’ve been through the logs and can see Grub was definitely updating the EFI partition. It created grubx64.efi just fine, no errors at that point. Reinstalled it after chrooting in and it’s now fine.
The shim lock protocol is usually only used by grub when Secure Boot is enabled. Or you have a buggy UEFI firmware. In the latter case I would recommend to install grub with --disable-shim-lock option.
If you have an off-standard boot situation better not use the ìnstall-grub script.
It is a tool which may work 98% on most default UEFI systems. Since your system seems to be problematic I suggest to maintain grub on your end manually. Arch and Manjaro normally don’t maintain grub at all. So the grub version you install via the install media is the one installed to your UEFI or MBR. Read my post again to get the needed background what we tried to achieve with this script: Install-grub: a new way to keep your EFI/MBR in-sync with grub package
Same! At this point my default assumption is that if I’m going to update a manjaro system, it will bork the grub. Every time. But YMMV I guess.
Everyone should ideally always make sure to have such, no matter what. But yes. A life saver.
Something I’ve noticed tho, and multiple times over the past 3 years of running manjaro, pamac-manager has a habit of closing the GUI randomly in the midst of the update. Update still happens in the BG but you just can’t keep any track of it.
Best you can do is relaunch pamac-manager, press update again and see it complain about another instance already running… until it stops complaining about that and then assume that it’s done…
…except you often restart before it’s had a chance to update grub I guess.
Honestly a rather terrible experience. I don’t think pamac should just randomly close itself like that in the middle of an update. Something is definitely wrong with that.
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-07-19