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).
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
As of Linux 6.16.12, the 6.16 series is now EOL (End Of Life). Please install 6.17 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.
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.
After switching branches from stable to testing and updating the system, I was met with the Error: symbol 'grub_memcpy' not found during boot. I fixed it by chrooting to the system from a live usb and then
cd /boot
cp grub/x86_64-efi/core.efi efi/EFI/BOOT/BOOTX64.EFI
Running install-grub from chroot didn’t fix the issue. Also, this only happened on a laptop installed with the Manjaro Cinnamon ISO (manjaro-cinnamon-25.0.3-250609-linux612.iso). Two other laptops installed with Manjaro GNOME ISO (manjaro-gnome-25.0.10-251013-linux612.iso) didn’t exhibit this issue after switching.
Random Steam games, with the new 6.18.0rc6-2 build, fail to launch. Switching to 6.17 fixed the issue.
Addendum; coincidentally, the unresponsiveness I was experiencing in Firefox is also gone.
Plasma, AMD GPU/CPU
EDIT 2: Tried 6.18.0rc6-2 again, Steam itself is failing to launch. rc6-1 was fine
EDIT 3: Uninstalled/reinstalled 6.18.0rc6-2 from Manjaro Settings Manager (oddly grub showed up as text-only). Steam launches but same errors launching same games. [IMHO] of note, while running journalctl -f in background, a whole lot of the following;
ERROR: ld.so: object ‘/home/username/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
systemd[746]: Started Launch DrKonqi for a systemd-coredump crash (PID 1142/UID 1000).
Also, this only happened on a laptop installed with the Manjaro Cinnamon ISO (manjaro-cinnamon-25.0.3-250609-linux612.iso ). Two other laptops installed with Manjaro GNOME ISO (manjaro-gnome-25.0.10-251013-linux612.iso ) didn’t exhibit this issue after switching.
I now have further info regarding this observed behavior. The laptop that was installed using Manjaro Cinnamon ISO is a Chromebook that was flashed using RW_LEGACY firmware aka edk2 UEFI bootloader. This is not a full firmware ROM replacement for the one that came with ChromeOS.
Because of this, the bootloader by default uses the path EFI/BOOT/BOOTX64.efi to load Grub, whereas the other two laptops with two different vendor BIOS use the correct path set by install-grub, which is EFI/Manjaro/grubx64.efi. Boot entries aren’t saved under RW_LEGACY, and it looks like EFI/BOOT/BOOTX64.efi doesn’t get updated whenever a Grub update is installed.
Well 'rc’ means 'release candidate’ so it’s really something to be avoided for folks who want stable systems okay for testing on non-critical systems to report bugs.
LTS is stable, but there are plenty of stable kernels to choose from.
I know all that.
I simply tried 6.18.0rc6-2 to check if the steam problem appeared there. I thought, I had seen someone posting that for him the RC worked fine. And I thought that showing that the problem appears on an AMD system might be an interesting data point.
You are free to dismiss that, of course.
OK, we may look into install-grub to also keep the legacy compat efi file synced as we only search for efi_boot_file=“bootx64.efi” …
@braveheartleo would you try to change efi_target_file="$(find $path -name $efi_boot_file)" to efi_target_file="$(find $path -iname $efi_boot_file)" in /usr/bin/install-grub and tell me if this might fix your issue with your fallback file?
I have manuallly copied the updated file atm to fix the issue, but from your proposed fix it looks like the case-insensitive matching would do the trick.
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-11-10
