Hello community, here we have another set of package updates. Since I’m still recovering from my move back to Europe from Asia, I might be less responsive on the forum. So lets test these packages thoroughly so we can do another stable branch snap.
Current Promotions
Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
Protect your personal data, keep yourself safe with Surfshark VPN: See current promotion
As of Linux 6.13.12, the 6.13 series is now EOL (End Of Life). Please install 6.14 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.
System may hang during splash screen when Nvidia 570 drivers are used
A lot of users with older Nvidia cards report system hanging on Plymouth splash screen after installing Nvidia 570 drivers. In the past we had issues with plymouth in general combined with Nvidia drivers. Therefore we didn’t update plymouth in our stable and testing branch.
As a workaround splash could be removed from /etc/default/grub file followed by a update-grub cmd to remove plymouth from starting. Another alternative is to test the newer plymouth and give feedback if that solves the issue:
Similar to Arch we removed our [community] repos from our mirrors and servers. You may want to check your pacnew files or manually remove [community] and [kde-unstable] when used in your /etc/pacman.conf file.
2025-02-16
Update only regular repository packages first, no AUR
Follow the best practice of first updating only regular repository packages, followed separately by AUR packages.
Update regular repository packages first with
pamac update --no-aur or
sudo pacman -Syu
Then, if needed, update AUR packages.
Failure to follow this practice may result in the installation of packages that you may not need, and may cause problems. For further details, see:
I have issue with kernel upgrades and gpu passthrough (vfio).
Using manjaro as a host with qemu to have different vms running gpu passthrough.
It seems that the gpu (I’m testing a 6900xt) is not reset properly with these kernels:
5.15.180
6.13.12 (EOL)
I cannot reboot any of my vms (windows, mac os and linux) nor shutdown the vm and switch to another, without restarting or shutting down the host system.
First boot is ok, however on first boot ovmf (upgraded to latest stable, but same behaviour with older versions) bios screen is not displayed on screen with the gpu passed through, it starts displaying the os screens.
Next boots are not ok.
Reverting back to 5.15.179 solves the issue.
Kernel 6.14.4 doesn’t have this issue, so it’s ok.
No relevant logs in dmesg…
If you are using kernel 5.15 (like me) and you use vms with gpu passwthrough I recommend to not upgrade to 5.15.180.
stay on it, qemu v.10 is upcoming. qemu v.10 has a lot of new improvements and i expect this will already cause a lot of adjustments on your/ours existing vm’s. there’s no need for speed at the actual moment.
there is a bug with the latest virtio-modules, i suggest that they are designed for the upcoming qemu v.10 and are not fully functional with the actual qemu.
This reverts commit 479380efe1625e251008d24b2810283db60d6fcd.
The reset_method attribute on a PCI device is only intended to manage
the availability of function scoped resets for a device. It was never
intended to restrict resets targeting the bus or slot.
In introducing a restriction that each device must support function
level reset by testing pci_reset_supported(), we essentially create a
catch-22, that a device must have a function scope reset in order to
support bus/slot reset, when we use bus/slot reset to effect a reset
of a device that does not support a function scoped reset, especially
multi-function devices.
This breaks the majority of uses cases where vfio-pci uses bus/slot
resets to manage multifunction devices that do not support function
scoped resets.
Hi, I just encountered an error with drawio-desktop on both of my computers. The program does not start; shows an error with two arguments given instead of one.
With manjaro-downgrade I upgraded to the unstable-recent version 26.2.15-2, which works flawless (26.1.1 had graphical glitches, so I used this approach).
Probably got mentioned somewhere, but a few updates ago I had the problem that Dolphin wouldnt remember which Tabs I had opened, I think since this update or the one before that it works again!
Thanks for your work!