[Unstable Update] September 2025

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

Notable Package Changes

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:

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

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

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

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

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

Check if your mirror has already synced:

A post was split to a new topic: Update failing due to a ‘corrupt PGP signature’

more a fix for nvidia & wayland

Another notable package change:

rofi-wayland replaced with extra/rofi

See: lbonn/rofi-wayland Announcement here

Wayland is now an officially supported backend for rofi.

During pacman upgrade, users will see:

:: Replace rofi-wayland with extra/rofi? [Y/n] y

Other than that, the upgrade should be a smooth drop-in replacement.

1 Like

A post was split to a new topic: An error occurred in the library libQt6QmlModels.so.6

upgraded update-grub (2:2.12.r359.g19c698d1-1 → 2:2.12.r359.g19c698d1-2)
==> ignores “quiet” parameter ==> unwanted boot-messages.

indeed, “quiet” the kernel parameter has nothing to do with it, this is printed by grub.

open file /etc/grub.d/10_linux (with root privileges)

find and change line from;

quiet_boot="0"

to

quiet_boot="1"

regenerate grub.cfg using;

sudo update-grub
1 Like

Will this “sir wife” updates?

i’ve had other modifications in other files in /etc/grub.d/ that has survived updates

1 Like

My GRUB menu stops at “0” while booting.
Do You know any setting to get rid of?
Normally /etc/xxxx.d is custom, but I like to be sure, thank You.

This is just a post for later referral - when / if I find a solution…

It seems there is an issue with libvirt’s virtual networking configuration when using Linux 6.16.6.

 $ uname -r
6.16.6-1-MANJARO

As I have been running Linux 6.16 for a while, without issues - I believe it is a regression and with the popularity of libvirt - I thought I would find similar issues online; I did not :slight_smile: :thinking:

The default NAT network does start and is running but the machine connected using the network never get any address assigned.

Removing the default network and creating a new nat-network with the same parameters also work - as in starting and running - but the virtual machine never get an address assigned.

Restarting the system, using Linux 6.12 - the same virtual network will happily assign an IP address to the vm.

 $ uname -r
6.12.46-1-MANJARO

2025-09-12T13:37:00Z

I couldn’t figure out the reason - now I am back a Linux 6.16 - with a working setup and no clue on what fixed it. quite annoying but :man_shrugging:

What I did do was to remove all relevant packages - cleanup remnants in /etc.

Install libvirt, virt-manager, qemu-desktop, dnsmasq - and now the network is as expected.

1 Like

I cannot reproduce this,
Using 6.16.6.1 as well, and using Gnome Boxes more or less every day.
But I am on testing currently …
Libvirt is the same in testing and unstable, so probably a different package is the reason?

I decided to bring back NVIDIA 570 and NVIDIA 575 driver series. For now you will find the dkms packages for proprietary and open drivers. Pre-compiled kernel modules may follow later:

Looks like this haven’t been done yet?

One of my friend encountered the grub shim lock issue recently when updating from an older system.

I agree that the install-grub command should be run automatically for a system update like that. So that average users don’t have to deal with live ISO.

(We should read the Known Issues section more carefully though.)

Hi @Yochanan, with [prepare] rework PKGBUILD (21b776fb) · Commits · Packages / core / grub · GitLab

--enable-quiet-boot
--enable-quick-boot

were removed. The first one resulting in quiet_boot="0"
in /etc/grub.d/10_linux. Was this intended? I would assume a lot of users to be suprised by seeing messages about loaded kernel and so on during booting when this reaches stable branch.

The issue mentioned there has been taken care of. I cannot say if the change has been propagated to all branches.

2 Likes

Fixed with grub 2:2.12.r359.g19c698d1-3.

2 Likes

Now also the pre-compiled modules are available. Next step is to add support for mhwd-db

1 Like

Now mhwd should offer these “new” drivers as well:

> 0000:01:00.0 (0300:10de:2820) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-amd-nvidia-prime     2026.09.18               false            PCI
          video-nvidia            2026.09.18               false            PCI
    video-nvidia-575xx            2026.09.18               false            PCI
    video-nvidia-570xx            2026.09.18               false            PCI
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI
2 Likes

Futuristic design?

3 Likes