[Unstable Update] August 2025

[Yochanan]

Welcome to the new monthly unstable branch thread.

Recent News

Kernel 6.15 is now EOL

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).

zabbix >= 7.4.1-2 may require manual intervention

2025-08-04 - Robin Candau

Starting with 7.4.1-2, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared zabbix user account (as originally intended by upstream and done by other distributions):

• zabbix-server
• zabbix-proxy
• zabbix-agent (also used by the zabbix-agent2 package)
• zabbix-web-service

This shared zabbix user account is provided by the newly introduced zabbix-common split package, which is now a dependency for all relevant zabbix-* packages.

The switch to the new user account is handled automatically for the corresponding main configuration files and systemd service units.

However, manual intervention may be required if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example:

• PSK files used for encrypted communication
• Custom scripts for metrics collections or report generations
• sudoers rules for metrics requiring elevated privileges to be collected
• …

Those should therefore be updated to refer to and / or be owned by the new zabbix user account, otherwise some services or user parameters may fail to work properly, or not at all.

Once migrated, you may remove the obsolete user accounts from your system.

– Arch Linux - News: zabbix >= 7.4.1-2 may require manual intervention

Notable Package Changes

• WebKitGTK 2.48.5
• KDE Plasma 6.4.4
• NetworkManager 1.54
• GStreamer 1.26.5
• KDE Frameworks 6.17.0
• GNOME 48.4
• NVIDIA 580.76.05
  • NOTE: The 580 series will be the last to support GPUs based on the Maxwell, Pascal, and Volta architectures. See Unix graphics feature deprecation schedule - Linux - NVIDIA Developer Forums
• VirtualBox 7.2.0
• KDE Gear 25.08
• Mesa 25.2.1
• Firefox 142.0.1
• LibreOffice 25.8.1
• Qt 6.9.2

Known Issues

2025-07-20 - grub update 2:2.12.r292 -> r350

Before reboot be sure to sync the grub efi-stubs in EFI/Manjaro and EFI/boot and recreate grub.cfg by using the install-grub script.

See → [Unstable Update] July 2025 - #31 by linux-aarhus

2025-06-22 - linux-firmware-amdgpu-20250613.12fe085f may create an unbootable system for RDNA4 GPUs or graphical glitches with RDNA3 GPUs

Currently AMD and the Linux community is working on fixing possible issues with the latest firmware changes for RDNA3 and RDNA4 GPUs. If you land on a black screen you may need to use a recovery image to downgrade the installed firmware. More information here:

• Making sure you're not a bot!
• Making sure you're not a bot!
• 20250613.12fe085f causes cursor duplication and gray flickering (#16) · Issues · Arch Linux / Packaging / Packages / linux-firmware · GitLab
• linux-firmware-amdgpu 20250613.12fe085f-6 prevents System from booting with RX 9000 Series (#17) · Issues · Arch Linux / Packaging / Packages / linux-firmware · GitLab
• https://www.reddit.com/r/archlinux/comments/1lhn3ti/slow_firmware_as_of_june_22_2025_update/

Also monitor the AMD DRM issue tracker

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

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

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

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

sudo chmod g+w /usr/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

Chrome/Chromium-based browsers and GNOME 48 - Global Shortcuts

If you have extensions who use shortcuts installed on these browsers, you’ll face an issue of many dialogs opening when the browser starts, it’s quite annoying. The bug has been reported and fixed, but the commit is not yet on a stable release.

The workaround for now, is to disable the feature via --disable-features=GlobalShortcutsPortal

• Bug report: Chromium

– https://www.reddit.com/r/gnome/comments/1jfejor/psa_chromechromiumbased_browsers_and_gnome_48/

python-gobject 3.52 breaks multiple apps (libpeas related)

Python plugins for programs like Gedit and Rhythmbox currently will not be loaded in the current state.

python-gobject 3.52 breaks multiple apps (libpeas related) (#3) · Issues · Arch Linux / Packaging / Packages / pygobject · GitLab

For Gedit, use the Flatpak for now. See Some problems currently with Python and gedit plugins | Gedit Technology blog

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.

Plasma 6.4.0 will need manual intervention if you are on X11

2025-06-20 - Tomaz Canabrava

On Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11.

With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn’t be ok to install plasma-x11-session and kwin-x11 for every one using Plasma.

tldr: Install plasma-x11-session if you are still using x11

– Arch Linux - News: Plasma 6.4.0 will need manual intervention if you are on X11

Additional Info

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.

Check if your mirror has already synced:

• Mirror-Check Service

[ydar]

Just ran into a problem updating:

error: failed to commit transaction (conflicting files)
dracut: /usr/share/libalpm/hooks/60-dracut-remove.hook exists in filesystem (owned by dracut-hook)
dracut: /usr/share/libalpm/hooks/90-dracut-install.hook exists in filesystem (owned by dracut-hook)
dracut: /usr/share/libalpm/scripts/dracut-install exists in filesystem (owned by dracut-hook)
dracut: /usr/share/libalpm/scripts/dracut-remove exists in filesystem (owned by dracut-hook)
Errors occurred, no packages were upgraded.

I guess dracut-hook needs an update to go with the dracut update today?

[Yochanan]

@ydar

I guess dracut-hook needs an update to go with the dracut update today?

Investigation pending… please wait.

[ben75]

I see we now have linux 6.16.0-4 with literally no differences from 6.16.0-3.

[freggel.doe]

I don’t like the many (public) kernel revisions either, but it seems to me that the 2 commits prior the pkrel adjustment would be the changes between revision 3 and 4:

[prepare] update patch-set (d9693f96) · Commits · Packages / core / linux616...

[prepare] update config (2cc6c874) · Commits · Packages / core / linux616 ·...

[ben75]

Ok. I missed that part. I just saw the [pkg-upd] pkgrel 4 which had no changes other than bumping pkgrel from 3 to 4.

[Zauberer-Merlin]

With today’s systemd update the suspend issues (since 1 or 1,5weeks or so) on my NVIDIA system are all gone and everything works again as it should .
I am stating this as this update migth be an important one that should be delivered to testing soon.

[stephane]

for patch btrfs

Btrfs Sees Urgent Fix Following Recent Reports Of Log Tree Corruption

about futex (6.17 )

Linux 6.17 Fixes A Performance Bottleneck In The Futex Code

and driver Xe & 6.17 for 4K is broken
( required Single Root I/O Virtualization (SR-IOV) in your Uefi on or auto )

Intel Xe Enabling SR-IOV PF By Default, Marking Driver As "Broken" For Non-4K...

[weingeist]

Thats new

Aug 08 22:03:40 (udev-worker)[630]: event5: Failed to call EVIOCSKEYCODE with scan code 0x10081, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[630]: event5: Failed to call EVIOCSKEYCODE with scan code 0x10082, and key code 0: Invalid argument

and

Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x10081, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x10082, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70070, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70071, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70072, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70073, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70074, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70075, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70076, and key code 0: Invalid argument
Aug 08 22:03:40 (udev-worker)[660]: event10: Failed to call EVIOCSKEYCODE with scan code 0x70077, and key code 0: Invalid argument

i check the events

sudo udevadm info /dev/input/event5                                                                                                                                        ✔ 
[sudo] Passwort für weingeist: 
P: /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/0003:0B05:184D.0005/input/input5/event5
M: event5
R: 5
J: c13:69
U: input
D: c 13:69
N: input/event5
L: 0
S: input/by-path/pci-0000:00:14.0-usbv2-0:7.3:1.0-event-kbd
S: input/by-path/pci-0000:00:14.0-usb-0:7.3:1.0-event-kbd
S: input/by-id/usb-ASUS_ROG_Claymore_Gaming_Keyboard-event-kbd
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.3/1-7.3:1.0/0003:0B05:184D.0005/input/input5/event5
E: DEVNAME=/dev/input/event5
E: MAJOR=13
E: MINOR=69
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4807259
E: KEYBOARD_KEY_10081=reserved
E: KEYBOARD_KEY_10082=reserved
E: KEYBOARD_KEY_70070=reserved
E: KEYBOARD_KEY_70071=reserved
E: KEYBOARD_KEY_70072=reserved
E: KEYBOARD_KEY_70073=reserved
E: KEYBOARD_KEY_70074=reserved
E: KEYBOARD_KEY_70075=reserved
E: KEYBOARD_KEY_70076=reserved
E: KEYBOARD_KEY_70077=reserved
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_BUS=usb
E: ID_MODEL=ROG_Claymore_Gaming_Keyboard
E: ID_MODEL_ENC=ROG\x20Claymore\x20Gaming\x20Keyboard
E: ID_MODEL_ID=184d
E: ID_SERIAL=ASUS_ROG_Claymore_Gaming_Keyboard
E: ID_VENDOR=ASUS
E: ID_VENDOR_ENC=ASUS
E: ID_VENDOR_ID=0b05
E: ID_REVISION=2109
E: ID_TYPE=hid
E: ID_USB_MODEL=ROG_Claymore_Gaming_Keyboard
E: ID_USB_MODEL_ENC=ROG\x20Claymore\x20Gaming\x20Keyboard
E: ID_USB_MODEL_ID=184d
E: ID_USB_SERIAL=ASUS_ROG_Claymore_Gaming_Keyboard
E: ID_USB_VENDOR=ASUS
E: ID_USB_VENDOR_ENC=ASUS
E: ID_USB_VENDOR_ID=0b05
E: ID_USB_REVISION=2109
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030101:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH_WITH_USB_REVISION=pci-0000:00:14.0-usbv2-0:7.3:1.0
E: ID_PATH=pci-0000:00:14.0-usb-0:7.3:1.0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_7_3_1_0
E: LIBINPUT_DEVICE_GROUP=3/b05/184d:usb-0000:00:14.0-7
E: DEVLINKS=/dev/input/by-path/pci-0000:00:14.0-usbv2-0:7.3:1.0-event-kbd /dev/input/by-path/pci-0000:00:14.0-usb-0:7.3:1.0-event-kbd /dev/input/by-id/usb-ASUS_ROG_Claymore_Gaming_Keybo>
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

and

sudo udevadm info /dev/input/event10                                                                                                                               ✔  30s  
P: /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.4/1-7.4:1.1/0003:0B05:197B.0009/input/input10/event10
M: event10
R: 10
J: c13:74
U: input
D: c 13:74
N: input/event10
L: 0
S: input/by-path/pci-0000:00:14.0-usbv2-0:7.4:1.1-event-mouse
S: input/by-path/pci-0000:00:14.0-usb-0:7.4:1.1-event-mouse
S: input/by-id/usb-ASUSTeK_ROG_GLADIUS_III-if01-event-mouse
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.4/1-7.4:1.1/0003:0B05:197B.0009/input/input10/event10
E: DEVNAME=/dev/input/event10
E: MAJOR=13
E: MINOR=74
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4807622
E: KEYBOARD_KEY_10081=reserved
E: KEYBOARD_KEY_10082=reserved
E: KEYBOARD_KEY_70070=reserved
E: KEYBOARD_KEY_70071=reserved
E: KEYBOARD_KEY_70072=reserved
E: KEYBOARD_KEY_70073=reserved
E: KEYBOARD_KEY_70074=reserved
E: KEYBOARD_KEY_70075=reserved
E: KEYBOARD_KEY_70076=reserved
E: KEYBOARD_KEY_70077=reserved
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_BUS=usb
E: ID_MODEL=ROG_GLADIUS_III
E: ID_MODEL_ENC=ROG\x20GLADIUS\x20III
E: ID_MODEL_ID=197b
E: ID_SERIAL=ASUSTeK_ROG_GLADIUS_III
E: ID_VENDOR=ASUSTeK
E: ID_VENDOR_ENC=ASUSTeK
E: ID_VENDOR_ID=0b05
E: ID_REVISION=0207
E: ID_TYPE=hid
E: ID_USB_MODEL=ROG_GLADIUS_III
E: ID_USB_MODEL_ENC=ROG\x20GLADIUS\x20III
E: ID_USB_MODEL_ID=197b
E: ID_USB_SERIAL=ASUSTeK_ROG_GLADIUS_III
E: ID_USB_VENDOR=ASUSTeK
E: ID_USB_VENDOR_ENC=ASUSTeK
E: ID_USB_VENDOR_ID=0b05
E: ID_USB_REVISION=0207
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030000:030102:
E: ID_USB_INTERFACE_NUM=01
E: ID_USB_DRIVER=usbhid
E: ID_PATH_WITH_USB_REVISION=pci-0000:00:14.0-usbv2-0:7.4:1.1
E: ID_PATH=pci-0000:00:14.0-usb-0:7.4:1.1
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_7_4_1_1
E: LIBINPUT_DEVICE_GROUP=3/b05/197b:usb-0000:00:14.0-7
E: DEVLINKS=/dev/input/by-path/pci-0000:00:14.0-usbv2-0:7.4:1.1-event-mouse /dev/input/by-path/pci-0000:00:14.0-usb-0:7.4:1.1-event-mouse /dev/input/by-id/usb-ASUSTeK_ROG_GLADIUS_III-if>

i have no idea

PS: i found this

Commit 6428c0f applied too broad a rule and is causing unintended issues

PS: It is fixed with systemd 257.8-3

[Yochanan]

@ydar

I guess dracut-hook needs an update to go with the dracut update today?

[Stable Update] 2025-08-11 - Kernels, Mesa, KDE Frameworks, Systemd

I’ve removed dracut-hook from the repos as it’s now obosolete: The dracut and dracut-gitAUR packages include hooks for pacman to automatically generate new initramfs images upon each kernel upgrade. – dracut - ArchWiki

[Kjplay]

New NVIDIA production branch drivers are released 580.76.05, but seem to have an important bug which has not been fixed since the beta release: 580 release feedback & discussion - #13 by Tekstryder - Linux - NVIDIA Developer Forums

[Yochanan]

It’s possible using the GSK_RENDERER=ngl environment variable may help with that issue.

Either way, the drivers cannot be packaged until NVIDIA tags egl-x11 1.0.3.

[philm]

It is tagged now. Release v1.0.3 · NVIDIA/egl-x11 · GitHub

[weingeist]

Did you forget to update the package linux616-nvidia-open ?

[Yochanan]

Yesh. Whoops.

Build script fixed and package pushed.

[weingeist]

the new nvidia driver is not good

Aug 13 22:26:21 kernel: NVRM: GPU at PCI:0000:01:00: GPU-3ced0ba2-d393-9cab-f4ee-12324490d93b
Aug 13 22:26:21 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=2347, name=GameThread, Graphics Exception: channel 0x00000041, Class 0000c9c0, Offset 00000000, Data 00000000
Aug 13 22:46:10 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=4448, name=GameThread, Graphics Exception: channel 0x00000047, Class 0000c9c0, Offset 00000000, Data 00000000
Aug 13 22:53:25 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=5638, name=GameThread, Graphics Exception: channel 0x00000047, Class 0000c9c0, Offset 00000000, Data 00000000
Aug 13 22:57:27 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=6543, name=GameThread, Graphics Exception: channel 0x00000047, Class 0000c9c0, Offset 00000000, Data 00000000
Aug 13 23:20:47 kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=9587, name=FORSPOKENDemo.e, channel 0x00000041, errorString CTX SWITCH TIMEOUT, Info 0x9c04a

Forspoken Demo and Cyberpunk

[Yochanan]

You know the routine. Please create a new Graphics & Display thread for further troubleshooting.

[philm]

Unstable branch might be broken due to updates to the toolchain

• [manjaro-packages] [BoxIt] Memo (x64)
• [manjaro-packages] [BoxIt] Memo (x64)

[ben75]

I just updated my kernel to 6.16.1-1.

When building the initramfs, mkinitcpio reported:

Starting build: '6.16.0-1-MANJARO'

Why does it identify as 6.16.0?