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
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:
Seems this was reported now multiple times. The current grub update larger than 2.13-3 might have some issues. What happens when the current stable version is used and any grub update ignored?
Also, a smaller issue, on boot I get the grub menu even though I did not get it 2-4 Updates ago, since I do not dual boot.
TLRD: GRUB menu shoes up even though I dont need it.
sudo grub-mkconfig -o /boot/grub/grub.cfg
A grub configuration file is generated …
Theme found: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.14-x86_64
Initrd image found: /boot/intel-ucode. img /boot/amd-ucode. img /boot/initramfs-6.14-x86_64.img
Found initrd fallback image: /boot/initramfs-6.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Initrd image found: /boot/intel-ucode. img /boot/amd-ucode. img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Warning: OS-prober will be launched to detect other boot partitions.
The result will be used to detect uploaded files and create new upload records.
Adds a boot menu item for UEFI firmware settings …
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
Not only “manjaro-settings-manager”, but also when launched from the terminal, it is displayed in English, so you can get a better image that is easy for many people to understand.
#change your lang to EN.
❱ LC_ALL=C manjaro-settings-manager
You are right. I rolled back the update, still having Plasma 6.3.3 and the bug is still there. Checked, vanilla test user and the same, so it’s not a matter of configs. How did I not see that earlier?
Will check on unstable then. Rolling even earlier backup is possible, but I am hesitant going so much back.
EDIT: On regular FF, PiP works, but on my installed web-app version is not and I can’t fix it, because settings are broken. Hard to choose from plethora of invisible options ;).
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-03-30
I’m using PiP too often.