[Testing Update] 2025-07-03 - Kernels, Linux-Firmware, Systemd, NVIDIA, Firefox, GStreamer

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

Notable Package Updates

  • Some Kernels got updated
    • linux613-rt and linux614-rt got dropped from the repos
    • linux-firmware got split into smaller packages. A meta-package ensures basic firmware installation. For stripping it down you may remove it after you have done the upgrade.
  • Systemd 257.7
  • GNOME 48.3
  • NVIDIA 575.64.03
  • Phosh 0.48.0
  • Firefox 140.0.2
  • GStreamer 1.26.3
  • OpenSearch 3.0
  • PipeWire 1.4.6

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.186
  • linux61 6.1.142
  • linux66 6.6.95
  • linux612 6.12.35
  • linux615 6.15.4
  • linux616 6.16.0-rc4
  • 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 (Thu Jul 3 09:14:58 CEST 2025)

  • testing core x86_64: 85 new and 81 removed package(s)
  • testing extra x86_64: 1902 new and 2010 removed package(s)
  • testing multilib x86_64: 45 new and 45 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:


1 Like

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

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.

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

signal-desktop with wayland and Nvidia is only starting with
“signal-desktop --ozone-platform=x11” on my nvidia machine. On an intel notebook it runs without an issue even with native wayland

Spectacle refuses to start.

error while loading shared libraries: libopencv_imgproc.so.411: cannot open shared object file: No such file or directory

OpenCV was updated to 4.12, but 4.11 is expected.

3 Likes

A post was split to a new topic: Keyboard layout switched from German to English after [Testing Update] 2025-07-03

Thanks @dennis.b. If you haven’t done so already, downgrading opencv will solve it :

sudo manjaro-downgrade opencv

Select 4.11 at prompt.

https://wiki.manjaro.org/index.php?title=Downgrading_packages

2 Likes

Thx, might need a rebuild. Next Tuesday 6.3.6 should come out, but I will add a rebuild now.

3 Likes

One tiny glitch. I tried updating via the GUI but the system froze. I retried doing the update via tty and updated with no problem. I also noted the system was running much cooler and with more memory free and with less cpu usage.

I am getting this weird error from dkms

Install DKMS modules                                                                                              [17/32]
==> dkms install --no-depmod hid-xpadneo/0.9.r222.gcd25680 -k 6.12.35-1-MANJARO
Deprecated feature: CLEAN (/var/lib/dkms/hid-xpadneo/0.9.r222.gcd25680/source/dkms.conf)
==> dkms install --no-depmod it87/287.4bff981 -k 6.12.35-1-MANJARO
Deprecated feature: CLEAN (/var/lib/dkms/it87/287.4bff981/source/dkms.conf)
==> dkms install --no-depmod zenpower3/0.2.0 -k 6.15.4-4-MANJARO
==> dkms install --no-depmod ryzen_smu/0.1.5 -k 6.12.35-1-MANJARO
Deprecated feature: CLEAN (/var/lib/dkms/ryzen_smu/0.1.5/source/dkms.conf)
==> dkms install --no-depmod zenpower3/0.2.0 -k 6.12.35-1-MANJARO
==> dkms install --no-depmod ryzen_smu/0.1.5 -k 6.15.4-4-MANJARO
Deprecated feature: CLEAN (/var/lib/dkms/ryzen_smu/0.1.5/source/dkms.conf)
==> dkms install --no-depmod it87/287.4bff981 -k 6.15.4-4-MANJARO
Deprecated feature: CLEAN (/var/lib/dkms/it87/287.4bff981/source/dkms.conf)
==> dkms install --no-depmod hid-xpadneo/0.9.r222.gcd25680 -k 6.15.4-4-MANJARO
Deprecated feature: CLEAN (/var/lib/dkms/hid-xpadneo/0.9.r222.gcd25680/source/dkms.conf)

I have found its nothing to be alarmed but the CLEAN line should be removed somewhere.

https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=1012043

EDIT: This is the root cause deprecate CLEAN by anbe42 · Pull Request #514 · dell/dkms · GitHub

Works, thank you.

On KDE, I noticed that ksystemstats has been removed from the Manjaro repos, but that plasma-systemmonitor and plasma-workspace both depend on ksystemstats :

Output : pamac info ksystemstats
LANG=C pamac info ksystemstats                                                                 ✔ 
Name                  : ksystemstats
Version               : 6.4.0-1
Description           : A plugin based system monitoring daemon
URL                   : https://kde.org/plasma-desktop/
Licenses              : LGPL-2.0-or-later
Repository            : None
Installed Size        : 1.6 MB
Groups                : plasma
Depends On            : gcc-libs glibc kcoreaddons kcrash ki18n kio libksysguard lm_sensors qt6-base solid
Optional Dependencies : libnl: network usage monitor [Installed]
                        networkmanager-qt: network usage monitor [Installed]
                        systemd-libs: GPU monitor [Installed]
Required By           : plasma-systemmonitor plasma-workspace
Optional For          : --
Provides              : --
Replaces              : --
Conflicts With        : --
Packager              : Tomaz Canabrava <tcanabrava@archlinux.org>
Build Date            : Wed 18 Jun 2025 21:58:20
Install Date          : Fri 20 Jun 2025 01:27:57
Install Reason        : Installed as a dependency for another package
Validated By          : Signature
Backup files          : --

Also, ksystemstats still appears in the Arch extra repo :

https://archlinux.org/packages/extra/x86_64/ksystemstats/

Could someone please shed some light on the context for the removal ? Is it normal for a package to be removed from a Manjaro repo if other packages still depend on it, and the removed package still exists in an Arch repo ? Thanks.

My guess is that the Plasma 6.4.0 version was prematurely rolled out to Testing (& Stable) branches, and subsequently removed from Testing, but the version for Plasma 6.3.5 hasn’t been returned to the repo:

mbn info ksystemstats -q | grep -Ev 'Name|Repository|Packager'
Branch         : archlinux
Version        : 6.4.2-1
Build Date     : Wed 02 Jul 2025 16:43:01 
Branch         : unstable
Version        : 6.4.2-1
Build Date     : Wed 02 Jul 2025 16:43:01 
Branch         : stable
Version        : 6.4.0-1
Build Date     : Wed 18 Jun 2025 19:58:20 

mbn can be found in the manjaro-check-repos package

Here’s my installation/update history for it:

Output of paclog --grep=ksystemstats
paclog --grep=ksystemstats
[2023-11-09T08:41:03+1100] [ALPM] upgraded ksystemstats (5.27.8-2 -> 5.27.9-1)
[2023-12-10T11:49:52+1100] [ALPM] upgraded ksystemstats (5.27.9-1 -> 5.27.10-1)
[2024-03-13T12:45:03+1100] [ALPM] upgraded ksystemstats (5.27.10-1 -> 5.27.11-1)
[2024-05-08T17:57:01+1000] [ALPM] upgraded ksystemstats (5.27.11-1 -> 6.0.4-1)
[2024-05-23T11:58:48+1000] [ALPM] upgraded ksystemstats (6.0.4-1 -> 6.0.5-0)
[2024-05-27T19:25:48+1000] [ALPM] upgraded ksystemstats (6.0.5-0 -> 6.0.5-1)
[2024-09-08T11:20:02+1000] [ALPM] upgraded ksystemstats (6.0.5-1 -> 6.1.4-1)
[2024-09-13T17:43:41+1000] [ALPM] upgraded ksystemstats (6.1.4-1 -> 6.1.5-1)
[2024-10-11T09:01:14+1100] [ALPM] upgraded ksystemstats (6.1.5-1 -> 6.2.0-1)
[2024-10-17T10:31:13+1100] [ALPM] upgraded ksystemstats (6.2.0-1 -> 6.2.1-1)
[2024-10-24T13:56:32+1100] [ALPM] upgraded ksystemstats (6.2.1-1 -> 6.2.2-1)
[2024-11-06T17:15:23+1100] [ALPM] upgraded ksystemstats (6.2.2-1 -> 6.2.3-1)
[2024-11-27T22:48:05+1100] [ALPM] upgraded ksystemstats (6.2.3-1 -> 6.2.4-0)
[2024-11-28T14:31:13+1100] [ALPM] upgraded ksystemstats (6.2.4-0 -> 6.2.4-1)
[2025-01-04T21:42:34+1100] [ALPM] upgraded ksystemstats (6.2.4-1 -> 6.2.5-1)
[2025-02-17T19:21:13+1100] [ALPM] upgraded ksystemstats (6.2.5-1 -> 6.3.0-1)
[2025-02-19T16:43:45+1100] [ALPM] upgraded ksystemstats (6.3.0-1 -> 6.3.1-1)
[2025-03-01T14:48:18+1100] [ALPM] upgraded ksystemstats (6.3.1-1 -> 6.3.2-1)
[2025-03-13T09:51:23+1100] [ALPM] upgraded ksystemstats (6.3.2-1 -> 6.3.3-1)
[2025-04-05T20:12:14+1100] [ALPM] upgraded ksystemstats (6.3.3-1 -> 6.3.4-1)
[2025-05-10T10:16:15+1000] [ALPM] upgraded ksystemstats (6.3.4-1 -> 6.3.5-1)
[2025-06-19T19:30:24+1000] [ALPM] upgraded ksystemstats (6.3.5-1 -> 6.4.0-1)
2 Likes

Should been fixed by now. Seems during some sync a 6.4.0 version was somehow added by Arch … [manjaro-packages] [BoxIt] Memo (x64)

3 Likes

Thanks @philm . The 6.4.0 → 6.3.5 version downgrade has been successfully installed from the Global mirrors:

sudo pacman -Syuu
[sudo] password for scotty: 
:: Synchronizing package databases...
 core is up to date
 extra                                               8.5 MiB  4.81 MiB/s 00:02 [--------------------------------------------] 100%
:: Starting full system upgrade...
warning: ksystemstats: downgrading from version 6.4.0-1 to version 6.3.5-1
resolving dependencies...
looking for conflicting packages...

Packages (1) ksystemstats-6.3.5-1

Total Installed Size:   1.49 MiB
Net Upgrade Size:      -0.04 MiB

:: Proceed with installation? [Y/n] y
1 Like