[Testing Update] 2025-07-15 - Kernels, KDE Frameworks, NetworkManager, Poppler, UMU

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.239
  • linux515 5.15.188
  • linux61 6.1.145
  • linux66 6.6.98
  • linux612 6.12.38
  • linux615 6.15.6
  • linux616 6.16.0-rc5
  • linux61-rt 6.1.134_rt51
  • linux66-rt 6.6.94_rt56
  • linux612-rt 6.12.28_rt10
  • linux615-rt 6.15.0_rt2

Package Changes (Tue Jul 15 09:23:53 CEST 2025)

  • testing core x86_64: 6 new and 6 removed package(s)
  • testing extra x86_64: 1050 new and 1046 removed package(s)
  • testing multilib x86_64: 4 new and 4 removed package(s)

Overlay Changes

  • testing core x86_64: 9 new and 9 removed package(s)
  • testing extra x86_64: 58 new and 59 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:

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-07-15

2025-07-10

Warning: ksystemstats: local (6.4.0-1) is newer than extra

If you get this warning, run the following command… :point_down:

sudo pacman -Syuu
VLC does not play (certain) videos

For this update, the VLC packages were split up, and not all codecs may be installed on your system. You can install the additional codecs individually, or install the vlc-plugins-all meta-package, which will pull in all available plugins. :point_down:

 sudo pacman -S vlc-plugins-all

2025-06-19

Possible breaking changes to pacman-mirrors

:warning: With pacman-mirrors 5.0-1, the global mirrors.json data file has been moved from /usr/share/pacman-mirrors to /var/lib/pacman-mirrors.
:warning: This move introduce a possible breaking change if you have custom scripts relying on the mirrors data file.
:information_source: The moving of the file is the only change and has been made to make it possible for users to have their /usr-tree on a separate read-only partition or btrfs subvolume.

2025-06-14

xkeyboard-config 2.45 issue with symlinks

You may fail to upgrade from 2.44 to 2.45 due to some changes to symlinks. A discussion about it can be found here: Cannot update xkeyboard-config to 2.45 / Pacman & Package Upgrade Issues / Arch Linux Forums

The solution is to update the AUR packages depending on xkeyboard-config or move the files to the new folder /usr/share/xkeyboard-config-2.

More information about it here: xkeyboard-config 2.45 issue with symlinks (#1) · Issues · Arch Linux / Packaging / Packages / xkeyboard-config · GitLab

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.

→ GitHub · Where software is built
→ 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

What’s holding KDE 6.4 to going on testing?

4

I only can guess, have a look into this:
https://archlinux.org/news/plasma-640-will-need-manual-intervention-if-you-are-on-x11/

3 Likes
5

Pamac failing to launch; journalctl -f yields

krunner[1936]: kf.kio.core: "" contains supported protocols but doesn't use %u or %U in its Exec line! This is inconsistent.
plasmashell[1204]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/delegates/DelegatePopup.qml:147:17: QML Body: Binding loop detected for property "width"
plasmashell[1204]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/delegates/DelegatePopup.qml:147:17: QML Body: Binding loop detected for property "width"

Notification in pop-up after fail;
Error launching Add/Remove Software:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

6
  • Possible memories of 5.25
  • Realisation that most Manjaro users never visit the forum or read update threads.

Plasma 6.4.1 fixed several bugs - and obviously there are backported patches which we get in 6.3.6 which is a proven version.

Testing is supposed to be pretty stable… our first buffer against the storm of Arch’s rapid updates.

So perhaps we’re waiting for cumulative fixes to appear for some critical stability issues in a later 6.4.x release before promoting to Testing :wink:

  • krunner killall pamac
    Try again… Log out/in… Reboot.
7

After a janky (read; I had to force reboot, facing a black screen with my theme’s pointer loaded) attempt at logging in after running this in Konsole, logging in after the reboot, was slower with a handful of services (ie; audio) not loading and a akonadi_migration_agent pop-up sitting on the desktop… I rebooted again, login was smooth “as usual.”

pamac launches smoothly but Refresh databases or selecting Preferences yields an instant Package Manager: Authentication failed pop-up window with a ‘Close’ button instead of being prompted for my password.

journalctl -f yields

xdg-desktop-portal-kde[1273]: xdp-kde-settings: Namespace  "org.gnome.desktop.a11y.interface"  is not supported
pamac-manager[4703]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

UPDATE: installed pamac-gtk3 as suggested by scotty65. Thank you. I wasn’t aware of the availability. It compliments my theme and, after a reboot, correctly prompts me for my password.

1 Like
8

As you are on Plasma, you should replace the pamac-gtk package with pamac-gtk3:

sudo pacman -Syu pamac-gtk3

pamac-gtk is reliant on Gnome’s Adwaita; pamac-gtk3 is more compatible with Plasma.

1 Like
10

As alternative to pamac you can also use octopi, which is Qt based.

1 Like
11

and it wouldn’t be ok to install plasma-x11-session and kwin-x11 for every one using Plasma.

Well, let’s consider this. The current state is that although wayland is the default session since 6.0 and everyone should be using it by now, everyone has also the x11 session still installed. Normally one should keep the users’ installation intact when updating and this implies one even has to install plasma-x11-session and kwin-x11 for every one using Plasma. Then the ones who don’t need the x11 session can remove these packages after the update manually (which they can’t do currently). On the other hand, not installing these packages on update would break the installation for the users still on the x11 session and just telling them they would have to fix their stuff manually (most likely they don’t know what happened). Now what exactly are the reasons to conclude breaking the installation for these users would be ok while installing something for users which they have installed already (because it’s all included in one package currently) wouldn’t be ok?