[Testing Updates] 2025-06-11 - Kernels, Mesa, KDE Gear, LibreOffice, AMD ROCm

Announcements Testing Updates
1

Hello community, here we have another set of package updates.

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
image679×348 45.7 KB

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.295
  • linux510 5.10.237
  • linux515 5.15.185
  • linux61 6.1.141
  • linux66 6.6.93
  • linux612 6.12.33
  • linux614 6.14.11 [EOL]
  • linux615 6.15.2
  • linux616 6.16.0-rc1
  • linux61-rt 6.1.134_rt51
  • linux66-rt 6.6.87_rt54
  • linux612-rt 6.12.28_rt10
  • linux613-rt 6.13_rt5
  • linux614-rt 6.14.0_rt3
  • linux615-rt 6.15.0_rt2

Package Changes (Tue Jun 10 18:34:17 CEST 2025)

  • testing core x86_64: 23 new and 23 removed package(s)
  • testing extra x86_64: 1171 new and 1144 removed package(s)
  • testing multilib x86_64: 18 new and 28 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
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-06-11

2025-06-01

2025-06-01 - avahi-discover python script

avahi-discover fails when attempting to write the discovered services to a sqlite database in /usr/lib/avahi due to lack of permissions.

The issue can be reproduced using a pristine Arch LInux system - it appears from the issues at GitHub - avahi/avahi: Avahi - Service Discovery for Linux using mDNS/DNS-SD -- compatible with Bonjour the issue is known - but not fixed.

→ Use of dbm causes problems with Python 3.13 · Issue #670 · avahi/avahi · GitHub
→ Fix issue with dbm.sqlite3 on readonly directories by mickael9 · Pull Request #698 · avahi/avahi · GitHub

Even though the issue has been known to upstream since december 2024, the behaviour on unstable branch has changed fairly recently - perhaps 4 weeks.

Temporary workaround
The workaround it is not optimal - but if you rely on avahi discover service - it will work

Move /usr/lib/avahi to /var/lib and symlink it back to /usr

sudo mv /usr/lib/avahi /var/lib/ && sudo ln -s /var/lib/avahi /usr/lib/

Change the ownership of the folder /var/lib/avahi including files

sudo chown root:avahi /var/lib/avahi -R

Change permissions to allow avahi group to write into the folder including the existing db file

sudo chmod g+w /var/lib/avahi -R

Finally add yourself to the avahi group

sudo gpasswd -a $USER avahi

Logoff and login to activate the new group.

Topic in German section
Avahi zeroconf browser zeigt nichts an

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-05-02
community has been re-created as an empty repository so that systems where package manager configuration /etc/pacman.conf has not been updated can still be used to update packages from other repositories

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:

3

The application was obviously badly designed, because /usr is a read-only filesystem hierarchy, and nothing should be expecting to be able to write to anything under /usr.

A better workaround would therefore be to move the database to /var/lib and create a symlink to it under /usr/lib.

2 Likes
4

Video wallpapers have a cool new cyberpunk aesthetic(it flickers too):

Example

V-Wallpaper_20250613_164401
V-Wallpaper_20250613_1644011280×800 150 KB

Now to be fair, it’s been a while since I updated the video wallpapers engine, so should probably do that, but figured it’s worth reporting here anyways.

Edit: updating the Wallpaper engine didn’t fix it, and it’s very likely a codec issue not a GPU driver issue(though never say never) and the GPU(rx 6600 xt) itself works fine - it’s just the video wallpaper. The driver update might have exposed a pre-existing issue in a codec perhaps, but that’s just a guess on my part.

6
7

@Aragorn It is a wiki post. When tested you can update the latest as needed before it gets posted in our stable branch announcement.

8

I have edited the wiki post. But that still doesn’t negate the fact that the application was ill-designed if it attempts to write to /usr.

9

You suggested to move the database to /var/lib and create a symlink to it under /usr/lib. That needs testing … @Aragorn

10

No need. The symlink under /usr/lib will forward every access to the actual location under /var/lib, and I’ve adapted the rest of the commands in the wiki post to directly address the directory under /var/lib.

Remember, symlinks are transparent to the application, because they are constructs in the filesystem layer itself. The application doesn’t know the difference between a symlink and an actual file or directory.

11

double check if today’s announcement also has your changes included …

12

Good point. It didn’t, so I edited it there too. :wink: