[Testing Update] 2025-09-29 - Kernel 6.17, Deepin, Yoshimi, Haskell, Python

philm · 29 September 2025 05:58

Hello community, here we have another set of package updates. Welcome to our new development cycle of Manjaro 25.1.0, code-named ‘Anh-Linh’. It is not sure yet if we will focus on Plasma 6.4 series or adopt 6.5 series early on. For sure we will introduce GNOME 49 and maybe Cosmic 1.0 (Beta).

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
Development | Q&A | OrangePi Neo-01
Manjaro 25.0 Zetar released
Manjaro Summit public Alpha now available
As of Linux 6.15.11, the 6.15 series is now EOL (End Of Life). Please install 6.16 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.
https://www.tuxedocomputers.com/en/Arch-Linux-and-Manjaro-on-TUXEDO-computers.tuxedo
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

Some Kernels got updated
- linux617 got now release as a stable release
Updates to Deepin
Yoshimi 2.3.5
Haskell and Python 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 Support > 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.299
linux510 5.10.244
linux515 5.15.193
linux61 6.1.154
linux66 6.6.108
linux612 6.12.49
linux616 6.16.9
linux617 6.17.0
linux61-rt 6.1.151_rt54
linux66-rt 6.6.106_rt61
linux612-rt 6.12.49_rt13
linux615-rt 6.15.0_rt2
linux616-rt 6.16.0_rt3

Package Changes (Mon Sep 29 07:42:36 CEST 2025)

testing core x86_64: 6 new and 6 removed package(s)
testing extra x86_64: 1175 new and 1173 removed package(s)
testing multilib x86_64: 6 new and 6 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 · 29 September 2025 05:59

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-09-28

pacman-mirrors version 5.2
Release Notes: v5.2 · Applications / pacman-mirrors · GitLab

2025-08-24

Graphical issues on older hardware (Black screen, Flickering) due to mesa 25.2.x update

It seems on older hardware the mesa 25.2.x update created some regressions which may result in black screens or flickering. Some older Nvidia cards with nouveau driver seem to be affected.

You can try to use the 25.1.x series of Mesa via this repo. Simply place it on top of [extra] in your /etc/pacman.conf file and use sudo pacman -Syuu to downgrade.

[mesa-251]
SigLevel = PackageRequired
Server = https://download.manjaro.org/pkgs/mesa

If you have no graphical session available you can access the bootloader by pressing ESC key during boot and select the bootloader entry. Press CTRL+E for edit and search for the words quiet and splash. Delete those and add 3 to the line. Then execute CTRL+x to start your session. You will land in a text console TTY. Login with your user.

Edit the /etc/pacman.conf with nano: sudo nano /etc/pacman.conf. Perform the downgrade and reboot.

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

Previous testing threads:

philm · 29 September 2025 14:36

Fresh ISOs including this update can be found here: Release 202509291348 · manjaro/release-review · GitHub

chainofflowers · 29 September 2025 15:59

Hi, I am experiencing this issue with akonadi IMAP agents after the update. It’s an old issue (5 years ago!) but it’s exactly the same.

And - as in that the bug report: on my laptop, with the very same packages installed, everything works fine indeed.

I also tried with ufw disable: no change.

Anyone else experiencing this weird issue?

UPDATE:
Got it.

In /usr/lib/NetworkManager/conf.d/20-connectivity.conf I have:

[connectivity]
uri=http://ping.manjaro.org/check_network_status.txt

but it seems not to be responding to my wget calls, therefore - I assume - NetworkManager thinks I have “limited connectivity” and akonadi (can’t figure out why) stays offline.

I think it is this old bug:

https://www.reddit.com/r/kde/comments/uulpcv/i_get_limited_connectivity_even_though_my/

I solved by creating a NetworkManager config file that disables that check:

/etc/NetworkManager/conf.d/disable-connectivity-check.conf
[connectivity]
enabled=false

and then restarted NetworkManager.

altmuehlmani · 30 September 2025 12:34

I had the same problem.
However, the error disappeared when I used my cell phone hotspot (5G), and my cell phone couldn’t access the page via Wi-Fi either.
Pinging the address worked, but http/https connect timed out.
It’s working again now, though. It seemed to me to be an internet provider or hosting problem. The error is now gone.

Zauberer-Merlin · 30 September 2025 13:52

Lenovo L14, AMD CPU und GPU, Manjaro Gnome, Testing.
Following the 29/09/2025 update, suspend did not work anymore, neither on 6.12 nor on 6.16/6.17.

Root cause was that systemd-rfkill service was enabled. By whom and why? I have no clue.
TLP and suspend did work before the update, but not after the install anymore. So during this updated something changed with regards to this service.

Why is this an issue? As this blocks TLP to work, leading in suspend issues.

Solved by

sudo systemctl mask systemd-rfkill.service
sudo systemctl mask systemd-rfkill.socket
reboot

and suspend works again.
But why / what did change during the update?

rousseau · 1 October 2025 00:59

@Zauberer-Merlin Is it possible that the issue is specific to your hardware and config ?

I have a Manjaro KDE Lenovo ThinkPad X1 Carbon Gen 8 (Intel CPU) and a Manjaro Gnome HP X360 13 (AMD CPU). Both machines have integrated graphics and suspend works on both.

That said, I do not have tlp installed : tlp does not appear to be a default package on new installations of Zetar 25.0. Also, default power management seems fine without it on 6.16.

gothicVI · 1 October 2025 12:01

Is anyone running docker and having issues with kernel 6.17?
I’m getting

$ systemctl status docker.s*
× docker.socket - Docker Socket for the API
     Loaded: loaded (/usr/lib/systemd/system/docker.socket; disabled; preset: disabled)
     Active: failed (Result: service-start-limit-hit) since Wed 2025-10-01 13:44:14 CEST; 2s ago
   Duration: 8.506s
 Invocation: b4cab8acdc6e44e791e9704dff26ad7a
   Triggers: ● docker.service
     Listen: /run/docker.sock (Stream)
   Mem peak: 512K
        CPU: 1ms

Okt 01 13:44:06 einstein systemd[1]: Starting Docker Socket for the API...
Okt 01 13:44:06 einstein systemd[1]: Listening on Docker Socket for the API.
Okt 01 13:44:14 einstein systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.

× docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Wed 2025-10-01 13:43:37 CEST; 39s ago
 Invocation: bade8d6dbb844b9496a558f1cf5203dd
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
    Process: 11627 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 11627 (code=exited, status=1/FAILURE)

Okt 01 13:43:37 einstein systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Okt 01 13:43:37 einstein systemd[1]: docker.service: Start request repeated too quickly.
Okt 01 13:43:37 einstein systemd[1]: docker.service: Failed with result 'exit-code'.
Okt 01 13:43:37 einstein systemd[1]: Failed to start Docker Application Container Engine.
Okt 01 13:44:14 einstein systemd[1]: docker.service: Start request repeated too quickly.
Okt 01 13:44:14 einstein systemd[1]: docker.service: Failed with result 'exit-code'.
Okt 01 13:44:14 einstein systemd[1]: Failed to start Docker Application Container Engine.

and

$ sudo dockerd --debug
INFO[2025-10-01T13:47:22.777878753+02:00] Starting up                                  
DEBU[2025-10-01T13:47:22.778272689+02:00] Listener created for HTTP on unix (/var/run/docker.sock) 
INFO[2025-10-01T13:47:22.778368727+02:00] OTEL tracing is not configured, using no-op tracer provider 
INFO[2025-10-01T13:47:22.778426222+02:00] CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory  dir=/etc/cdi
INFO[2025-10-01T13:47:22.778435962+02:00] CDI directory does not exist, skipping: failed to monitor for changes: no such file or directory  dir=/var/run/cdi
DEBU[2025-10-01T13:47:22.784805013+02:00] Golang's threads limit set to 112500         
INFO[2025-10-01T13:47:22.785131368+02:00] Creating a containerd client                  address=/run/containerd/containerd.sock timeout=1m0s
DEBU[2025-10-01T13:47:22.785220316+02:00] metrics API listening on /var/run/docker/metrics.sock 
DEBU[2025-10-01T13:47:22.785582841+02:00] Using default logging driver json-file       
DEBU[2025-10-01T13:47:22.785673169+02:00] No quota support for local volumes in /var/lib/docker/volumes: Filesystem does not support, or has not enabled quotas 
DEBU[2025-10-01T13:47:22.786015003+02:00] processing event stream                       module=libcontainerd namespace=plugins.moby
DEBU[2025-10-01T13:47:22.794689606+02:00] [graphdriver] priority list: [overlay2 fuse-overlayfs btrfs zfs vfs] 
DEBU[2025-10-01T13:47:22.807186090+02:00] successfully detected metacopy status         storage-driver=overlay2 usingMetacopy=true
DEBU[2025-10-01T13:47:22.812350442+02:00] backingFs=extfs, projectQuotaSupported=false, usingMetacopy=true, indexOff="index=off,", userxattr=""  storage-driver=overlay2
INFO[2025-10-01T13:47:22.812370515+02:00] [graphdriver] using prior storage driver: overlay2 
DEBU[2025-10-01T13:47:22.812380190+02:00] Initialized graph driver overlay2            
DEBU[2025-10-01T13:47:22.822713461+02:00] Max Concurrent Downloads: 3                  
DEBU[2025-10-01T13:47:22.822738755+02:00] Max Concurrent Uploads: 5                    
DEBU[2025-10-01T13:47:22.822744423+02:00] Max Download Attempts: 5                     
INFO[2025-10-01T13:47:22.822762225+02:00] Loading containers: start.                   
DEBU[2025-10-01T13:47:22.824713483+02:00] processing event stream                       module=libcontainerd namespace=moby
DEBU[2025-10-01T13:47:22.825243819+02:00] loaded container                              container=01eea8bf83895f1eef7b12e7f00e3c88060e53274b56731d4571a5b17a5662f2 paused=false running=false
DEBU[2025-10-01T13:47:22.825244550+02:00] loaded container                              container=d0e3c4d35712e13d25c4bc57c9f23f3f20343f70428956cae6e7b119dc1872be paused=false running=false
DEBU[2025-10-01T13:47:22.825246942+02:00] loaded container                              container=d0fa11f412a8adc0c192acf28ba36574e1e4e748c93a6625eefd79ac0803c487 paused=false running=false
DEBU[2025-10-01T13:47:22.853149271+02:00] restoring container                           container=01eea8bf83895f1eef7b12e7f00e3c88060e53274b56731d4571a5b17a5662f2 paused=false restarting=false running=false
DEBU[2025-10-01T13:47:22.853180751+02:00] restoring container                           container=d0fa11f412a8adc0c192acf28ba36574e1e4e748c93a6625eefd79ac0803c487 paused=false restarting=false running=false
DEBU[2025-10-01T13:47:22.853266795+02:00] restoring container                           container=d0e3c4d35712e13d25c4bc57c9f23f3f20343f70428956cae6e7b119dc1872be paused=false restarting=false running=false
DEBU[2025-10-01T13:47:22.853790014+02:00] done restoring container                      container=d0fa11f412a8adc0c192acf28ba36574e1e4e748c93a6625eefd79ac0803c487 paused=false restarting=false running=false
DEBU[2025-10-01T13:47:22.853846687+02:00] done restoring container                      container=d0e3c4d35712e13d25c4bc57c9f23f3f20343f70428956cae6e7b119dc1872be paused=false restarting=false running=false
DEBU[2025-10-01T13:47:22.853919170+02:00] done restoring container                      container=01eea8bf83895f1eef7b12e7f00e3c88060e53274b56731d4571a5b17a5662f2 paused=false restarting=false running=false
DEBU[2025-10-01T13:47:22.854009820+02:00] Option DefaultDriver: bridge                 
DEBU[2025-10-01T13:47:22.854026473+02:00] Option DefaultNetwork: bridge                
DEBU[2025-10-01T13:47:22.854032845+02:00] Network Control Plane MTU: 1500              
DEBU[2025-10-01T13:47:22.854284450+02:00] Modules already loaded                        modules="[nf_conntrack nf_conntrack_netlink]"
DEBU[2025-10-01T13:47:22.856105575+02:00] /usr/bin/iptables, [--wait -t filter -C FORWARD -j DOCKER-ISOLATION] 
DEBU[2025-10-01T13:47:22.857591550+02:00] /usr/bin/iptables, [--wait -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER] 
DEBU[2025-10-01T13:47:22.863868812+02:00] /usr/bin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER] 
DEBU[2025-10-01T13:47:22.871315446+02:00] /usr/bin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER] 
DEBU[2025-10-01T13:47:22.881407585+02:00] /usr/bin/iptables, [--wait -t nat -D PREROUTING] 
DEBU[2025-10-01T13:47:22.894076689+02:00] /usr/bin/iptables, [--wait -t nat -D OUTPUT] 
DEBU[2025-10-01T13:47:22.908067088+02:00] /usr/bin/iptables, [--wait -t nat -F DOCKER] 
DEBU[2025-10-01T13:47:22.921376446+02:00] /usr/bin/iptables, [--wait -t nat -X DOCKER] 
DEBU[2025-10-01T13:47:22.934914564+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER] 
DEBU[2025-10-01T13:47:22.938129957+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER] 
DEBU[2025-10-01T13:47:22.941256102+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER-FORWARD] 
DEBU[2025-10-01T13:47:22.944325139+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER-FORWARD] 
DEBU[2025-10-01T13:47:22.947254630+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER-BRIDGE] 
DEBU[2025-10-01T13:47:22.950193877+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER-BRIDGE] 
DEBU[2025-10-01T13:47:22.953452494+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER-CT] 
DEBU[2025-10-01T13:47:22.956605203+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER-CT] 
DEBU[2025-10-01T13:47:22.959748494+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER-ISOLATION-STAGE-1] 
DEBU[2025-10-01T13:47:22.962706834+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER-ISOLATION-STAGE-1] 
DEBU[2025-10-01T13:47:22.965870659+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER-ISOLATION-STAGE-2] 
DEBU[2025-10-01T13:47:22.968916592+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER-ISOLATION-STAGE-2] 
DEBU[2025-10-01T13:47:22.972180213+02:00] /usr/bin/iptables, [--wait -t filter -F DOCKER-ISOLATION] 
DEBU[2025-10-01T13:47:22.975335761+02:00] /usr/bin/iptables, [--wait -t filter -X DOCKER-ISOLATION] 
DEBU[2025-10-01T13:47:22.978694587+02:00] /usr/bin/iptables, [--wait -t nat -n -L DOCKER] 
DEBU[2025-10-01T13:47:22.992025980+02:00] /usr/bin/iptables, [--wait -t nat -N DOCKER] 
DEBU[2025-10-01T13:47:23.005499053+02:00] daemon configured with a 15 seconds minimum shutdown timeout 
DEBU[2025-10-01T13:47:23.005553124+02:00] start clean shutdown of all containers with a 15 seconds timeout... 
INFO[2025-10-01T13:47:23.008179075+02:00] stopping event stream following graceful shutdown  error="<nil>" module=libcontainerd namespace=moby
DEBU[2025-10-01T13:47:23.008221171+02:00] Cleaning up old mountid : start.             
DEBU[2025-10-01T13:47:23.008726548+02:00] Cleaning up old mountid : done.              
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.11 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
 (exit status 3)
INFO[2025-10-01T13:47:23.009220657+02:00] stopping event stream following graceful shutdown  error="context canceled" module=libcontainerd namespace=plugins.moby

with

$ modinfo ip_tables 
filename:       /lib/modules/6.17.0-0-MANJARO/kernel/net/ipv4/netfilter/ip_tables.ko.zst
description:    IPv4 packet filter
author:         Netfilter Core Team <coreteam@netfilter.org>
license:        GPL
srcversion:     E76A147B434207E5FEF1739
depends:        x_tables
intree:         Y
name:           ip_tables
retpoline:      Y
vermagic:       6.17.0-0-MANJARO SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        69:51:BF:7E:9D:06:07:EA:22:2F:EC:21:52:17:75:92:BF:73:EE:FA
sig_hashalgo:   sha512
signature:      30:66:02:31:00:C8:9A:26:7B:02:49:48:FC:4F:65:5F:6E:2F:08:D1:
		8E:C6:C6:0A:2F:60:54:16:2F:9B:86:4C:C7:78:F8:5D:8F:68:C1:F2:
		89:8D:2E:49:F4:6D:9C:70:6B:C2:C5:A2:DE:02:31:00:98:1B:9B:56:
		31:88:38:BE:80:90:F8:3B:81:05:6A:7A:59:89:A9:B2:9A:D6:B7:60:
		EC:75:13:EB:6F:02:D0:2F:1C:F8:FA:0F:C3:DD:FF:EB:19:0E:C2:43:
		97:24:FB:7D

EDIT: This seems to be fixed by GitHub · Where software is built
Maybe this should be addressed somehow.
EDIT: Though it might just be a workaround.
EDIT: Doesn’t fix it

philm · 1 October 2025 12:11

Our build should normally support IPTABLES_LEGACY in 6.17: legacy iptables broken [LWN.net]

gothicVI · 1 October 2025 12:15

Somehow seems to not be the case. Any idea how to debug/fix that?

philm · 1 October 2025 12:24

Maybe I missed some. Try to rebuild the kernel with these config updates: [prepare] try to enable ip-tables legacy support for docker (7a4b29ad) · Commits · Packages / core / linux617 · GitLab and let me know if they change anything …

gothicVI · 1 October 2025 12:38

What solved it was replacing iptables with iptables-nft. Was there ever an announcement for this transition? I can not recall seeing one in any announcement.
I have this system running since 2020-07-26 and never touched iptables myself.

philm · 1 October 2025 13:53

it was changed during the 6.17-rc development cycle: netfilter: Exclude LEGACY TABLES on PREEMPT_RT.