[Testing Update] 2025-03-12 - Kernels, Plasma 6.3.3, KDE Gear, Firefox, Thunderbird, Pipewire 1.4

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: 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.234
  • linux515 5.15.178
  • linux61 6.1.130
  • linux66 6.6.82
  • linux612 6.12.18
  • linux613 6.13.6
  • linux614 6.14.0-rc6
  • linux66-rt 6.6.78_rt51
  • linux612-rt 6.12.16_rt9
  • linux613-rt 6.13_rt5

Package Changes (Wed Mar 12 15:24:00 CET 2025)

  • testing core x86_64: 21 new and 21 removed package(s)
  • testing extra x86_64: 2793 new and 2759 removed package(s)
  • testing multilib x86_64: 28 new and 27 removed package(s)

Overlay Changes

  • testing core x86_64: 18 new and 18 removed package(s)
  • testing multilib x86_64: 1 new and 1 removed package(s)
  • testing extra x86_64: 88 new and 262 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

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-03-12

2025-01-15

Critical rsync security release 3.4.0

2025-01-16 - Robin Candau

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.

Arch Linux - News: Critical rsync security release 3.4.0

2024-12-11

Kernel 6.11 and 4.19 has been marked End Of Life (EOL) on kernel.org

Previous testing threads:

Update went well, only thing I notice is that when playing audio through mpv I see some message printed:

[W][01:59:37.979665] pw.conf      | [          conf.c: 1204 pw_conf_load_conf_for_context()] setting config.name to client-rt.conf is deprecated, using client.conf

It happens when pipewire is used as audio output device (mpv --ao=pipewire on command line or in config).
But it still plays fine.

It also shows up in journalctl:

Mar 13 01:49:28 mpv[52039]: pw.conf: setting config.name to client-rt.conf is deprecated, using client.conf
Mar 13 01:49:28 xdg-desktop-por[14487]: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
Mar 13 01:50:57 mpv[52145]: pw.conf: setting config.name to client-rt.conf is deprecated, using client.conf
Mar 13 01:50:57 xdg-desktop-por[14487]: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
Mar 13 01:51:59 mpv[52205]: pw.conf: setting config.name to client-rt.conf is deprecated, using client.conf
Mar 13 01:51:59 xdg-desktop-por[14487]: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
Mar 13 01:52:56 mpv[52271]: pw.conf: setting config.name to client-rt.conf is deprecated, using client.conf
Mar 13 01:52:56 xdg-desktop-por[14487]: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
Mar 13 01:59:37 mpv[52488]: pw.conf: setting config.name to client-rt.conf is deprecated, using client.conf
Mar 13 01:59:37 xdg-desktop-por[14487]: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory

I can’t find any pw.conf, so not really sure if this is a config issue or what.

Hi, I have a small problem, which I cannot really pinpoint to a package. It just occurred directly after the reboot after the update.
In gnome, some photos are displayed incorrectly. These photos are HDR ones in a heif image format. When I convert them to another format, the colors also are displayed the same way.

You can see it on the attached screenshot. The small preview/icon image here is displayed correctly. It was my previous desktop background. You might imagine my surprise about seeing the wrong colors :smiley:

What furthe information do you need?

I also got a small issue after mpd upgrade to ver 0.24-1 :
using Plattenalbum mpd client , the ‘show’ option in context menu which is intended to open the selected song in the default file browser (thunar in my case) is resulting ‘grayed’, also, at first start, Plattenabum displayed an empty music collection and so I had to update it using the ‘update database’ option in menu. Note that neighter the db, nor the mpd.conf file have changed, and i didn’t notice any visible change in user persmissions. Very odd behaviour :slight_smile: Hope someone using Plattenalbum as mpd client could check and confirm back this issue is not only mine.

1 Like

Something changed in pipewire. MPV still tries to use the old pipewire configuration. The warning is harmless.

1 Like

MPV just had a minor update on unstable branch:

mpv (1:0.39.0-4 → 1:0.39.0-5)

1 Like

Yea, seems to be a rebuild from arch to fix exactly that:

I’ve installed it and it makes the warnings go away as expected.

Es gab ein kleines Problem. Community.db konnte nicht geöffnet werden. Habe Schlüssel und Mirrors aktualisiert. Danach lief die Aktualisierung problemlos durch.

1 Like

:de:
Hallo, Bitte auf English :slight_smile:

Lösung !

:uk:
[community] repo removed from servers

2 Likes

look here scroll

2 Likes

Since 1:0.39.0-5 just barely missed this testing update, I’ve pushed it to the testing branch.

2 Likes

This is important. Updates went smoothly on all computers only after commenting out the [Community] repo related lines of pacman.conf

1 Like

With Plasma 6.3.3 (running on Archlinux) I don’t get the crash on Inkscape.

2 Likes

2 posts were split to a new topic: Chromium 134.0.6998.88 crashes when screen sharing on Wayland

Google Meet but also several video and audio streaming wesites stopped working for me. I don’t get any sound or my headset micro isn’t working.
I will try swiching to X11 and test.

philm noted audio issues if using Pipewire with pulseaudio under ‘Notable Package Updates.’ Might removing pulseaudio help (if installed)?

Noticed the update to pipewire and checked the logs. The entry below has appeared in the logs for some time now, but installing pipewire-libcamera seems to have cleared it.

$ journalctl -r --grep=pipewire
Mar 18 14:42:40 XXXXXX wireplumber[1081]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
2 Likes

Every time a linux-firmware update comes along (20250311.b69d4b74-1 → 20250311.b69d4b74-2), my wireless G305 mouse tends to stop responding after a reboot but thankfully it’s easily solved by simply re-plugging back in the wireless usb dongle. So happy this process is fairly seamless.:green_heart:

No loss of sound from pulseaudio (17.0-43-g3e2bb) on my system after PipeWire update

[2025-03-15T07:13:19+0000] [ALPM] upgraded pipewire (1:1.4.0-2 -> 1:1.4.1-0)