[Testing Update] 2025-08-16 - KDE Gear, Wine, Xfce, Python, Haskell

philm · 16 August 2025 21:55

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

Current Promotions

Get the latest Gaming Laptop by Slimbook powered by Manjaro: Slimbook Manjaro III
Protect your personal data, keep yourself safe with Surfshark VPN: See current promotion

Recent News

Development | Q&A | Zotac Gaming ZONE Pro - experience it live at Gamescom 2025
Development | Q&A | OrangePi Neo-01
Manjaro 25.0 Zetar released
Manjaro Summit public Alpha now available
As of Linux 6.14.11, the 6.14 series is now EOL (End Of Life). Please install 6.15 stable and/or 6.12 LTS (Long Term Support).

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

Roman was at Froscon and had a talk about Manjaro
Initial preview of Manjaro Immutable is now available!
Roman published our new Website
Philip was at Computex and showed off the OrangePi Neo
Manjaro Team member @romangg has a new library project with a guest post on Phoronix.
Some Manjaro team members attended FOSDEM 2024 and we showed off a prototype of the upcoming Orange Pi Neo Handheld Gaming Console!
Check out the new Manjaro Slimbook Hero!
Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
Arch Linux and Manjaro on TUXEDO computers - Arch Linux and Manjaro on TUXEDO computers - TUXEDO Computers
Linux, Judo, unicycles and … Baywatch?! How Vivaldi and Manjaro aim above the ordinary. | Vivaldi Browser
https://frame.work/blog/spotlight-on-manjaro-linux-interview-with-the-team

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

KDE Gear 25.08.0
Wine 10.13
Some Xfce updates
Python and Haskell updates

Additional Info

Python 3.13 info

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

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.296
linux510 5.10.240
linux515 5.15.189
linux61 6.1.148
linux66 6.6.102
linux612 6.12.42
linux615 6.15.10
linux616 6.16.1
linux617 6.17.0-rc1
linux61-rt 6.1.146_rt53
linux66-rt 6.6.99_rt58
linux612-rt 6.12.39_rt11
linux615-rt 6.15.0_rt2
linux616-rt 6.16.0_rt3

Package Changes (Sat Aug 16 23:28:59 CEST 2025)

testing core x86_64: 8 new and 8 removed package(s)
testing extra x86_64: 1379 new and 1383 removed package(s)
testing multilib x86_64: 4 new and 4 removed package(s)

Overlay Changes

testing extra x86_64: 7 new and 7 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:

Mirror-Check Service

discobot · 16 August 2025 21:56

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:

2025-08-16

2025-07-24

grub update - watch out

Before you reboot - ensure to run install-grub script to sync the efi-stubs and recreate the grub config.

[Testing Update] 2025-07-19 - Kernels, Mesa, Thunderbird, Grub, Perl, Vulkan - #19 by linux-aarhus

2025-07-10

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

If you get this warning, run the following command…

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.

 sudo pacman -S vlc-plugins-all

2025-06-19

Possible breaking changes to pacman-mirrors

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.
This move introduce a possible breaking change if you have custom scripts relying on the mirrors data file.
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

Previous testing threads:

philm · 16 August 2025 22:03

Zotac Gaming Pro at Gamescom 2025

Together with Zotac we will present Manjaro GamingOS at Gamescom 2025 on all Zotac Zone Handheld devices. Visit us at Hall 10.1 at the be quiet! booth to speak with the team at Zotac Gaming from Germany and Hong Kong. Additionally we have a meeting room at Hall 2.2 in C51 Gibl.

wpkg · 18 August 2025 14:41

Something is broken in the this update. Trying to play a video using vaapi results in no video (just a blue screen) with audio playing along.

mpv --hwdec=vaapi Demystifying\ Python\'s\ Async\ and\ Await\ Keywords.mp4
● Video  --vid=1               (h264 1920x1080 59.9401 fps) [default]
● Audio  --aid=1  --alang=eng  (aac 2ch 44100 Hz 128 kbps) [default]
Using hardware decoding (vaapi).
[autoconvert] Converting vaapi[nv12] -> vaapi[bgr0]
[ffmpeg] filter: Hardware does not support output format bgr0.
[ffmpeg] filter: Failed to configure output pad on filter
[lavfi] failed to configure the filter graph
Cannot convert decoder/filter output to any format supported by the output.
Attempting next decoding method after failure of h264-vaapi.
AO: [pipewire] 44100Hz stereo 2ch floatp
[ffmpeg/video] h264: co located POCs unavailable
[ffmpeg/video] h264: co located POCs unavailable
VO: [gpu] 1920x1080 yuv420p
[vo/gpu/libplacebo] Allocation of size 8640K failed: VK_ERROR_OUT_OF_DEVICE_MEMORY!
[vo/gpu/libplacebo] Memory heaps supported by device:
[vo/gpu/libplacebo]     0: flags 0x1 size 4096M
[vo/gpu/libplacebo]     1: flags 0x0 size   11G
[vo/gpu/libplacebo] Memory pool 0:
[vo/gpu/libplacebo]     Compatible types: 0x3
[vo/gpu/libplacebo]     Optimal flags: 0x1
[vo/gpu/libplacebo]     Slab  0: ffffffffffffffff x  4096:     0 used     0 res  256K alloc from heap 0, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Pool summary:     0 used     0 res  256K alloc, efficiency 100.00%, utilization 0.00%
[vo/gpu/libplacebo] Memory pool 1:
[vo/gpu/libplacebo]     Compatible types: 0xffffffff
[vo/gpu/libplacebo]     Required flags: 0x2
[vo/gpu/libplacebo]     Optimal flags: 0x8
[vo/gpu/libplacebo]     Buffer flags: 0x3
[vo/gpu/libplacebo]     Slab  0:        0 x 3153K:   12M used   12M res   12M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Slab  1:        0 x 3153K:   24M used   24M res   24M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Slab  2:     ffc0 x 3153K:   18M used   18M res   49M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Pool summary:   55M used   55M res   86M alloc, efficiency 100.00%, utilization 64.29%
[vo/gpu/libplacebo] Memory summary:   55M used   55M res   86M alloc, efficiency 100.00%, utilization 64.10%, max page:  256M
[vo/gpu/libplacebo]   Backtrace:
[vo/gpu/libplacebo]     #0  0x00007fdf2df9a7f0 in +0x0 at /usr/lib/libplacebo.so.351+0xad7f0
[vo/gpu/libplacebo]     #1  0x00007fdf2df9b0e2 in +0x0 at /usr/lib/libplacebo.so.351+0xae0e2
[vo/gpu/libplacebo]     #2  0x00007fdf2df9baab in +0x0 at /usr/lib/libplacebo.so.351+0xaeaab
[vo/gpu/libplacebo]     #3  0x00005563744606db in +0x0 at mpv+0x1276db
[vo/gpu/libplacebo]     #4  0x00005563744419be in +0x0 at mpv+0x1089be
[vo/gpu/libplacebo]     #5  0x0000556374444140 in +0x0 at mpv+0x10b140
[vo/gpu/libplacebo]     #6  0x00005563744525be in +0x0 at mpv+0x1195be
[vo/gpu/libplacebo]     #7  0x000055637445a245 in +0x0 at mpv+0x121245
[vo/gpu/libplacebo]     #8  0x00005563743b935b in +0x0 at mpv+0x8035b
[vo/gpu/libplacebo]     #9  0x0000556374457d5d in +0x0 at mpv+0x11ed5d
[vo/gpu/libplacebo]     #10 0x00007fdf2ba969cb in +0x0 at /usr/lib/libc.so.6+0x969cb
[vo/gpu/libplacebo]     #11 0x00007fdf2bb1aa0c in +0x0 at /usr/lib/libc.so.6+0x11aa0c
[vo/gpu/libplacebo] No slab to serve request for 2160K bytes (with alignment 0x400) in pool 0!
[vo/gpu/libplacebo] Allocation of size 2400K failed: VK_ERROR_OUT_OF_DEVICE_MEMORY!
[vo/gpu/libplacebo] Memory heaps supported by device:
[vo/gpu/libplacebo]     0: flags 0x1 size 4096M
[vo/gpu/libplacebo]     1: flags 0x0 size   11G
[vo/gpu/libplacebo] Memory pool 0:
[vo/gpu/libplacebo]     Compatible types: 0x3
[vo/gpu/libplacebo]     Optimal flags: 0x1
[vo/gpu/libplacebo]     Slab  0: ffffffffffffffff x  4096:     0 used     0 res  256K alloc from heap 0, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Pool summary:     0 used     0 res  256K alloc, efficiency 100.00%, utilization 0.00%
[vo/gpu/libplacebo] Memory pool 1:
[vo/gpu/libplacebo]     Compatible types: 0xffffffff
[vo/gpu/libplacebo]     Required flags: 0x2
[vo/gpu/libplacebo]     Optimal flags: 0x8
[vo/gpu/libplacebo]     Buffer flags: 0x3
[vo/gpu/libplacebo]     Slab  0:        0 x 3153K:   12M used   12M res   12M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Slab  1:        0 x 3153K:   24M used   24M res   24M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Slab  2:     ffc0 x 3153K:   18M used   18M res   49M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Pool summary:   55M used   55M res   86M alloc, efficiency 100.00%, utilization 64.29%
[vo/gpu/libplacebo] Memory summary:   55M used   55M res   86M alloc, efficiency 100.00%, utilization 64.10%, max page:  256M
[vo/gpu/libplacebo]   Backtrace:
[vo/gpu/libplacebo]     #0  0x00007fdf2df9a7f0 in +0x200000001 at /usr/lib/libplacebo.so.351+0xad7f0
[vo/gpu/libplacebo]     #1  0x00007fdf2df9b0e2 in +0x200000001 at /usr/lib/libplacebo.so.351+0xae0e2
[vo/gpu/libplacebo]     #2  0x00007fdf2df9baab in +0x200000001 at /usr/lib/libplacebo.so.351+0xaeaab
[vo/gpu/libplacebo]     #3  0x00005563744606db in +0x200000001 at mpv+0x1276db
[vo/gpu/libplacebo]     #4  0x00005563744419be in +0x200000001 at mpv+0x1089be
[vo/gpu/libplacebo]     #5  0x0000556374444140 in +0x200000001 at mpv+0x10b140
[vo/gpu/libplacebo]     #6  0x00005563744525be in +0x200000001 at mpv+0x1195be
[vo/gpu/libplacebo]     #7  0x000055637445a245 in +0x200000001 at mpv+0x121245
[vo/gpu/libplacebo]     #8  0x00005563743b935b in +0x200000001 at mpv+0x8035b
[vo/gpu/libplacebo]     #9  0x0000556374457d5d in +0x200000001 at mpv+0x11ed5d
[vo/gpu/libplacebo]     #10 0x00007fdf2ba969cb in +0x200000001 at /usr/lib/libc.so.6+0x969cb
[vo/gpu/libplacebo]     #11 0x00007fdf2bb1aa0c in +0x200000001 at /usr/lib/libc.so.6+0x11aa0c
[vo/gpu/libplacebo] No slab to serve request for  600K bytes (with alignment 0x400) in pool 0!
[vo/gpu/libplacebo] Allocation of size 2400K failed: VK_ERROR_OUT_OF_DEVICE_MEMORY!
[vo/gpu/libplacebo] Memory heaps supported by device:
[vo/gpu/libplacebo]     0: flags 0x1 size 4096M
[vo/gpu/libplacebo]     1: flags 0x0 size   11G
[vo/gpu/libplacebo] Memory pool 0:
[vo/gpu/libplacebo]     Compatible types: 0x3
[vo/gpu/libplacebo]     Optimal flags: 0x1
[vo/gpu/libplacebo]     Slab  0: ffffffffffffffff x  4096:     0 used     0 res  256K alloc from heap 0, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Pool summary:     0 used     0 res  256K alloc, efficiency 100.00%, utilization 0.00%
[vo/gpu/libplacebo] Memory pool 1:
[vo/gpu/libplacebo]     Compatible types: 0xffffffff
[vo/gpu/libplacebo]     Required flags: 0x2
[vo/gpu/libplacebo]     Optimal flags: 0x8
[vo/gpu/libplacebo]     Buffer flags: 0x3
[vo/gpu/libplacebo]     Slab  0:        0 x 3153K:   12M used   12M res   12M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Slab  1:        0 x 3153K:   24M used   24M res   24M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Slab  2:     ffc0 x 3153K:   18M used   18M res   49M alloc from heap 1, efficiency 100.00%  [unknown]
[vo/gpu/libplacebo]     Pool summary:   55M used   55M res   86M alloc, efficiency 100.00%, utilization 64.29%
[vo/gpu/libplacebo] Memory summary:   55M used   55M res   86M alloc, efficiency 100.00%, utilization 64.10%, max page:  256M
[vo/gpu/libplacebo]   Backtrace:
[vo/gpu/libplacebo]     #0  0x00007fdf2df9a7f0 in +0x200000001 at /usr/lib/libplacebo.so.351+0xad7f0
[vo/gpu/libplacebo]     #1  0x00007fdf2df9b0e2 in +0x200000001 at /usr/lib/libplacebo.so.351+0xae0e2
[vo/gpu/libplacebo]     #2  0x00007fdf2df9baab in +0x200000001 at /usr/lib/libplacebo.so.351+0xaeaab
[vo/gpu/libplacebo]     #3  0x00005563744606db in +0x200000001 at mpv+0x1276db
[vo/gpu/libplacebo]     #4  0x00005563744419be in +0x200000001 at mpv+0x1089be
[vo/gpu/libplacebo]     #5  0x0000556374444140 in +0x200000001 at mpv+0x10b140
[vo/gpu/libplacebo]     #6  0x00005563744525be in +0x200000001 at mpv+0x1195be
[vo/gpu/libplacebo]     #7  0x000055637445a245 in +0x200000001 at mpv+0x121245
[vo/gpu/libplacebo]     #8  0x00005563743b935b in +0x200000001 at mpv+0x8035b
[vo/gpu/libplacebo]     #9  0x0000556374457d5d in +0x200000001 at mpv+0x11ed5d
[vo/gpu/libplacebo]     #10 0x00007fdf2ba969cb in +0x200000001 at /usr/lib/libc.so.6+0x969cb
[vo/gpu/libplacebo]     #11 0x00007fdf2bb1aa0c in +0x200000001 at /usr/lib/libc.so.6+0x11aa0c
[vo/gpu/libplacebo] No slab to serve request for  600K bytes (with alignment 0x400) in pool 0!
AV: 00:00:04 / 01:18:52 (0%) A-V:  0.000 Dropped: 2
Exiting... (Quit)

No issues with the same command as of the update on 14th. I’m on KDE plasma and have an Intel integrated graphics as well as NVIDIA GeForce RTX 3050 Ti Laptop GPU.

I also saw that the update have a comment about Nvidia settings manager stating something to the tune of “If you run into issues run nvidia-ctk cdi generate --output="/etc/cdi/nvidia.yaml"”. I’ve done that, but the issue persists.

Basic device info:

❯❯ inxi -zv2
System:
Kernel: 6.12.42-1-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.3.6 Distro: Manjaro Linux
Machine:
Type: Laptop System: ASUSTeK product: ASUS TUF Gaming F15 FX507ZE_FX577ZE
v: 1.0 serial: <superuser required>
Mobo: ASUSTeK model: FX507ZE v: 1.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: FX507ZE.315 date: 06/17/2022
Battery:
ID-1: BAT1 charge: 44.3 Wh (72.9%) condition: 60.8/90.2 Wh (67.4%)
CPU:
Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP]
speed (MHz): avg: 676 min/max: 400/4600:4700:3500
Graphics:
Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: i915 v: kernel
Device-2: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] driver: nvidia
v: 580.76.05
Device-3: Sonix USB2.0 HD UVC WebCam driver: uvcvideo type: USB
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
gpu: i915,nvidia,nvidia-nvswitch resolution: 1: 1920x1080~60Hz
2: 1920x1080
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.1.7-arch1.1
renderer: Mesa Intel Iris Xe Graphics (ADL GT2)
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: gputop, intel_gpu_top, lsgpu,
nvidia-settings, nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
Device-2: Intel Ethernet I219-LM driver: e1000e
Device-3: Lite-On Dell Wireless Device driver: hid-generic,usbhid
type: USB
Drives:
Local Storage: total: 5.01 TiB used: 841.24 GiB (16.4%)
Info:
Memory: total: 16 GiB note: est. available: 15.24 GiB used: 5.13 GiB (33.7%)
Processes: 414 Uptime: 9m Shell: fish inxi: 3.3.38

Possible solution:

hwdec=vaapi-copy and auto works. vaapi-copy uses intel iGPU whereas auto uses nvdec (and Nvidia) for decoding. Something has changed between the updates, as vaapi worked before it – not sure what.

2old4gaming · 20 August 2025 20:46

I’m wondering if this issue with the Nvidia 580 drivers might apply.

Yochanan · 20 August 2025 20:52

wpkg · 21 August 2025 12:48

Not directly seems like. Ran the command Yochanan, confirmed replacement worked, rebooted and the issue persists.

Yochanan · 24 August 2025 17:17