[Testing Update] 2025-04-21 - Kernels, GNOME 48.1, NVIDIA 570.144, KDE Gear 25.04, Mesa

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

Recent News

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.

Arch Linux - News: Valkey to replace Redis in the [extra] Repository

Previous News
Finding information easier about Manjaro

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

image

Notable Package Updates

Additional Info

Python 3.13 info

:information_source: 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

:warning: 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.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux54 5.4.292
  • linux510 5.10.236
  • linux515 5.15.180
  • linux61 6.1.134
  • linux66 6.6.86
  • linux612 6.12.24
  • linux613 6.13.12 [EOL]
  • linux614 6.14.3
  • linux61-rt 6.1.134_rt51
  • linux66-rt 6.6.87_rt54
  • linux612-rt 6.12.16_rt9
  • linux613-rt 6.13_rt5
  • linux614-rt 6.14.0_rt3

Package Changes (Mon Apr 21 09:50:33 CEST 2025)

  • testing core x86_64: 73 new and 69 removed package(s)
  • testing extra x86_64: 3081 new and 3163 removed package(s)
  • testing multilib x86_64: 31 new and 31 removed package(s)

A list of all package changes can be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)
0 voters

Check if your mirror has already synced:


2 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed


Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Note: Do not forget to review your .pacnew files:

:arrow_right: 2025-04-21

2025-03-20

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:

sudo pacman -U https://mirrors.manjaro.org/repo/pool/overlay/plymouth-24.004.60-12-x86_64.pkg.tar.zst

2025-03-05

[community] repo removed from servers

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.

  1. Update regular repository packages first with
    • pamac update --no-aur
      or
    • sudo pacman -Syu
  2. 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:

Keyboard layout issues / Update issues with fcitx5

If a system had sdl2 installed and AUR updates enabled, fcitx5 might be installed as a make dependency

It is recommended to remove fcitx5 and any other orphan packages following the update

pamac remove --orphans

Update issues with fcitx5

Previous testing threads:

@philm - there is a typo that migth confuse some people … it should be “As of Linux 6.13.12”
Minor, I know, but …

Rest of the update went smooth, will see how the 570.144 works over the next days

1 Like

Lol @ this little dolphin that got added on the icon for Dolphin. Kinda cute. :slight_smile:
Screenshot_20250421_161219

4 Likes

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.

my 2cent after 1day with the update:

After working one day only with the Notebook

  • NVIDIA 2070
  • 570.144
  • Gnome
  • Wayland

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.

2 Likes

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.

2 Likes

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

Looks like networkmanager is not working with latest kernel and systemd-networkd will work: USB tethering not working after updating to latest kernel / Newbie Corner / Arch Linux Forums

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:

  1. Disable NetworkManager
systemctl stop NetworkManager.service
  1. Configure systemd-networkd: Create /etc/systemd/network/tether.network with content
[Match]
Name=wwp0s20u2

[Network]
DHCP=yes
  1. Start systemd-networkd and systemd-resolved
systemctl start systemd-networkd.service
systemctl start systemd-resolved.service

Update 3: Should be fixed in kernel 6.12.28, I will test when it gets in testing repo.

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.