Hello community, here we have another set of package updates. Since I’m preparing to move back to Europe from Asia, I might be less responsive on the forum. So lets test these packages throughly 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: Get 4 months extra
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.
We’d like to raise awareness about the rsync security release version 3.4.0-1 as described in our advisory ASA-202501-1.
An attacker only requires anonymous read access to a vulnerable rsync server, such as a public mirror, to execute arbitrary code on the machine the server is running on. Additionally, attackers can take control of an affected server and read/write arbitrary files of any connected client. Sensitive data can be extracted, such as OpenPGP and SSH keys, and malicious code can be executed by overwriting files such as ~/.bashrc or ~/.popt.
We highly advise anyone who runs an rsync daemon or client prior to version 3.4.0-1 to upgrade and reboot their systems immediately. As Arch Linux mirrors are mostly synchronized using rsync, we highly advise any mirror administrator to act immediately, even though the hosted package files themselves are cryptographically signed.
All infrastructure servers and mirrors maintained by Arch Linux have already been updated.
All seems well so far (besides pamac crash to desktop as with the last update, hope to remember to use pacman next time). After Grub (which I have set to show with a 3 second timeout), I see;
Loading Linux 6.14.0-rc4-1-MANJARO x64 …
Loading initial ramdisk …
_
for maybe 2 seconds before the KDE login screen pops up. Not sure if this is an intentional part of the boot process now. Will update if anything goes awry. Thank you.
If your update fails because of a dependency error, icu for example:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron29
The solution is not to ignore icu. Check the package that is blocking the update; there is a decent chance that it is an orphan and should be removed.
Manjaro Unstable users seem to have largely avoided this issue, but there were several posts on the Arch and EndeavourOS forums where people tried to ignore icu, which can end up breaking pacman.
It seems to be that the grub version that is in testing / unstable is buggy.
To be more precise: os-prober is seg-faulting, therefor the grub installation in / for dual-boot systems is failing.
This leads to some error messages directly after BIOS execution - something like “wrong UUID” - but it leads to grub after pressing a key.
Workaround for me: I re-installed the previous grub-version from a second manjaro-installation on my drive. This works, I can boot into my day2day system without any issues.
On github it is mentioned, that another workaround would be to mount the windows system partition before the grub installation / os-prober run.
I did not test this as my system is working at the moment
Reason is a change in /etc/grub.d/10_linux
Edit as root using Meld this file of grub 2.12-3 and change old to new
or replace 10_linux bei version taken from grub 2.12-3
After this sudo update-grub needed!
Same here. After installing and rebooting the machine booted directly to Linux without showing the boot menu. Downgrading grub to 2.12-3 resolved this issue.
That’s what I did: I replaced the file 10_linux, but apparently, it’s not enough in my case.
I still get those os-probe errors when I run update-grub.
When I boot, I see my Grub menu, but not all the items: I cannot see the Manjaro and Advanced options.
I only see Windows and my BTRFS snapshots, and I’m currently booted into my latest snapshot.
So i can’t boot into my updated system.
EDIT : downgrading to grub 2.12-3 solved the issue
I am also getting this error, but oddly enough, everything still works. . I’m not worrying for now.
I also did not get the grub menu. I went into /etc/default/grub and changed GRUB_TIMEOUT_STYLE=hidden to GRUB_TIMEOUT_STYLE=menu to make the desired behaviour explicit
Deadbeef was blocking the update because of Flac library. I had laready switched to Qmmp, was keeping Deadbeef around to see if they had resolved issues I had with it.
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-01
. I’m not worrying for now.