[Testing Update] 2025-04-05 - Systemd, Bluez, Plasma, Firefox, Thunderbird, QEMU, Qt6, Mesa

Announcements Testing Updates
,
1

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

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.290
  • linux510 5.10.235
  • linux515 5.15.178
  • linux61 6.1.132
  • linux66 6.6.85
  • linux612 6.12.21
  • linux613 6.13.9
  • linux614 6.14.0
  • linux61-rt 6.1.128_rt49-1
  • linux66-rt 6.6.84_rt52
  • linux612-rt 6.12.16_rt9
  • linux613-rt 6.13_rt5

Package Changes (Sat Apr 5 09:37:42 CEST 2025)

  • testing core x86_64: 38 new and 39 removed package(s)
  • testing extra x86_64: 1851 new and 2125 removed package(s)
  • testing multilib x86_64: 26 new and 26 removed package(s)

A list of all 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:

3 Likes
2

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-05

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:

1 Like
3
  1. pacman-mirrors showed 3/8 mirrors updated…
  2. sudo pacman-mirrors --continent && pacman-mirrors got 6 fresh ones.
  3. sudo pacman -Syu went smoothly.
  4. flatpak upgrade pulled in 5 gnome/gtk upgrades.

All looks good.

1 Like
4

Pamac failed to install this update, but via terminal pacman installation was succesful. (some dependency issue with lib32-fontconfig)

1 Like
5

Have you removed the discontinued community repo from your pacman.conf?

3 Likes
6

It’s nice seeing these 700+ MiB updates come through on a more regular basis. No immediate problems for me on pacman. New orphan: vulkan-headers.

:information_source:
It’s probably also worth mentioning that for those of you with modern AMD motherboards, some manufacturers like Asus have started pushing out more uefi/bios updates that you should “probably” check and update as there are some security items relating to properly verifying future microcode updates. More reading here and here. I got a new update on my B550 board just a couple days ago on 1-apr (no joke.)

5 Likes
7

but there are also hardware-related problems actually like the electrical shorts and burned sockets mainly on asrock but they are not the only vendors.

8

@Olli, In my mind, bios updates from the manufacturer are a sensitive topic. Some people say don’t “fix” an unbroken system…but, if there’s discussion of better securing your system, then I would perform these particular firmware updates if you understand the literature and advisory notices. Just keep in mind that every bios update (in my experience,) wipes all your previous settings in there so before proceeding, be prepared to note (or possibly save) your current settings if you’re doing things like overclocking and whatever else. The only thing I really do on my 5950x is a small overclock for crypto mining and then enabling the XMP/DOCP profile for my ram. The choice is ultimately yours however.

2 Likes
10