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.
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.
Update went through like a charm in tty, no .pacnew, nothing to rebuild
After the reboot I was even suprised to see that with the nvidia 570.133 driver and 6.13 kernel GNOME switched per default to wayland now …
I need zoom (AUR) - and this works much better with wayland.
Virtualbox (for my German Tax software that I need) started as well (so I am soooo very very happy that I am able to continue with my beloved tax - thanks for the update that was much better than the work I need to do today )…
Until now (20min uptime or so) this really looks like a cool update…
I was REALLY worried about the jump to nvidia 570 this round as before on unstable I just couldn’t get one of my hdmi displays working on that new-feature branch – I even downgraded back to testing because of this. Thankfully, no issues yet after updating today. Thank you team!
GDM fails to load for me with this update, and it’s definitely the Nvidia 570 drivers. Hardware is a GTX 1070. The boot process appears to go smoothly, but then once it says it’s starting GDM, it hangs at a black screen and a non-blinking cursor, and switching to tty2+ shows a blinking cursor but otherwise an unresponsive system.
I can investigate from a terminal by rebooting at runlevel 3. I don’t see any errors (red text) relevant during boot. Possibly relevant journal entries (non-contiguous):
gnome-shell[1266]: Failed to create view for Samsung Electric Company SAMSUNG on HDMI-1: Failed to allocate onscreen framebuffer for /dev/dri/card0: An EGLConfig argument does not name a valid EGL frame buffer configuration.
/usr/lib/gdm-wayland-session[1253]: dbus-daemon[1253]: [session uid=120 pid=1253 pidfd=5] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=1266 comm="/usr/bin/>
at-spi-bus-laun[1329]: unable to open file '/etc/dconf/db/gdm': Failed to open file “/etc/dconf/db/gdm”: open() failed: No such file or directory; expect degraded performance
/usr/lib/gdm-wayland-session[1253]: dbus-daemon[1253]: [session uid=120 pid=1253 pidfd=5] Successfully activated service 'org.a11y.Bus'
gnome-shell[1266]: Using public X11 display :1024, (using :1025 for managed services)
gnome-shell[1266]: Using Wayland display name 'wayland-0'
/usr/lib/gdm-wayland-session[1336]: dbus-daemon[1336]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=1266 comm=/usr/bin/gnome-shell)
gnome-shell[1266]: Saving monitor configuration failed: Error opening file “/var/lib/gdm/.config/monitors.xml”: Permission denied
/usr/lib/gdm-wayland-session[1336]: dbus-daemon[1336]: Successfully activated service 'org.a11y.atspi.Registry'
/usr/lib/gdm-wayland-session[1339]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
org.gnome.Shell.desktop[1337]: eglInitialize() failed
org.gnome.Shell.desktop[1337]: XWAYLAND: Disabling GLAMOR support
org.gnome.Shell.desktop[1337]: EGL setup failed, disabling glamor
org.gnome.Shell.desktop[1337]: Failed to initialize glamor, falling back to sw
systemd[1]: Starting Manage, Install and Generate Color Profiles...
When I disable Wayland entirely, GDM boots fine. But X11 has so many issues on my system, it feels like a waste of time troubleshooting that path. Wayland was running fine on my system with the 550 drivers.
Are the the three requirements met as listed here:
Yes; like I said Wayland was working fine with the 550 drivers.
GDM status report didn’t show anything out of the ordinary - it hadn’t started yet, when i started it from tty2 it hung, then when I stopped it from tty2 it was reported as having stopped.
I actually got GDM to boot by adding this line to my /etc/modprobe.d/nvidia-graphics-drivers-kms.conf:
options nvidia-drm fbdev=1
from this troubleshooting thread that was about a similar, but definitely not the same, issue. System is now working 100%. That was the first thing I tried changing actually; guess I got lucky. It’s odd that my boot params already had fbdev=1 but it also needed to be set here. Any idea why it wasn’t set to begin with, or alternately why it was necessary on my system but not others?
Hello! I see that bluez was part of this update. It seems that, while other bluetooth devices still work, my Logitech bluetooth mouse stopped working. I tried to downgrade from 5.80-1 to 5.79-1 and everything works again. As soon as I upgrade to 5.80-1, my mouse stops working. Anyone else experiencing problems?
Thanks!
Hi @luc4, you might check out my post regarding my wireless G305 several days ago. For me it was simply a case of re-plugging back in the dongle. I don’t believe mine is technically bluetooth and I don’t control it with the blueman-manager. However, I do have a pair of bluetooth Bose headphones so I’ll test those shortly and I’ll report back if I have sound problems.
I saw your profile card as you being on the stable branch so you may want to update your profile showing what branch you’re on and what you currently have running (and your mouse too.)
Just found out that nvidia-settings starts with a weird window-size and does not show Graphics information. Out of curiosity I installed nvidia-settings-beta from AUR which works as expected.
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-20
)…
