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:
Encountered a problem with krdp server on a host machine post-update : could no longer connect krdc client on a client machine to krdp server on host. Both the client machine and the host machine run Manjaro KDE (testing).
Fixed on the host machine by removing / deleting RDP user from list of authorised RDP users (system settings → remote desktop), re-adding user, and restarting RDP server : krdc client now connects as expected to krdp server.
it seems to be that after the last hugh update with
new nvidia driver AND
systemd updated!
The OS is working more stable than before.
Sleep issues are gone (knocking on wood as hard as I can) at least for this one day. No issues anymore at all. Everything is working as it should .
My assumption at the moment (since a couple of weeks already) is, that the NVIDIA driver is heavily depending on the systemd version, and this setup is a working pair at the moment.
As of now - it is working great. I even close the lid again without asking myself if it works currently.
Upon switching branches from Stable to Testing and performing sudo pacman -Syu
I’m getting this message:
cannot resolve "alsa-lib=1.2.14", a dependency of "lib32-alsa-lib"
:: The following package cannot be upgraded due to unresolvable dependencies:
lib32-alsa-lib
I wanted to switch branches because of mesa 25.0.4 but if i skip resolving this dependency i’m not getting it however i do get a bunch of lib32- packages including lib32-mesa so i assume it is because of this dependency i can’y update properly, right? What do i need to do to resolve it?
EDIT
I’ve tried sudo pacman -Syyu and now i’m getting full updates, silly me.
After this update usb tethering from my android phone stopped working. I had to downgrade linux kernel from 6.12.24 to 6.12.21 to get it to work.
Here is dmesg output:
[ 35.401451] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[ 35.533381] usb 1-2: New USB device found, idVendor=05c6, idProduct=9024, bcdDevice= 5.04
[ 35.533387] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 35.533389] usb 1-2: Product: POCO X4 Pro 5G
[ 35.533391] usb 1-2: Manufacturer: Xiaomi
[ 35.533392] usb 1-2: SerialNumber: edaeace471e2
[ 36.173126] usbcore: registered new interface driver cdc_ether
[ 36.178570] rndis_host 1-2:1.0 wwan0: register 'rndis_host' at usb-0000:00:14.0-2, Mobile Broadband RNDIS device, 86:2a:43:ff:dc:2f
[ 36.178690] usbcore: registered new interface driver rndis_host
[ 36.187075] rndis_host 1-2:1.0 wwp0s20u2: renamed from wwan0
Update: A user on Arch Linux Forums said this problem is device specific, and I found that with kernel 6.12.24, while usb tethering from POCO X4 Pro (with custom ROM) is not working, Redmi Note 8T (with custom ROM) is working.
Update 2: I tried systemd-networkd and usb tethering is working. This is what I did:
Disable NetworkManager
systemctl stop NetworkManager.service
Configure systemd-networkd: Create /etc/systemd/network/tether.network with content
I face issues with my two GNOME online accounts. My Google account and my IMAP/STMP account got disconnected. The GNOME settings tell me the connection was lost and I should reconnect. my emailer Evolution tells me as well.
Still working on recovering, but yet unsuccessful to make them resume their service.