[Unstable Update] October 2026

Yochanan · 1 October 2026 13:43

Welcome to the monthly unstable branch thread.

Recent News

Notable Package Changes

Mesa 26.2.4
Firefox 157.0.1
GRUB 2.16
GNOME 51
Libadwaita 1.10
WebKitGTK 2.54.1
Phosh 0.58.0
NVIDIA 615.78.08
Qt 6.12
Thunderbird 156.0.1 / 157.0.1
KDE Gear 26.08.2
LibreOffice 26.8.1
GStreamer 1.28.8

Known Issues

Additional Info

Python 3.14 info

You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.13.so.

Print a list of of packages that have files in /usr/lib/python3.13/ :

pacman -Qoq /usr/lib/python3.13/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.13)

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.

Check if your mirror has already synced:

Mirror-Check Service

Ben · 1 October 2026 13:16

There’s a problem with qbittorrent - it got a couple of times due to a memory leak…

qBittorrent 5.2.4 is not fully compatible with libtorrent-rasterbar 2.1.x

github.com/qbittorrent/qBittorrent

Memory leak qBittorrent 5.2.1

opened 05:08PM - 02 Jul 26 UTC

closed 06:06AM - 15 Jul 26 UTC

ngosang

Performance

### qBittorrent & operating system versions Docker: linuxserver/qbittorrent:5.2….2 Host: Ubuntu 26.04 Headless (qbittorrent-nox) ### What is the problem? I have been running qBittorrent for years without problems. Same hardware, same Docker container, etc... This is the qBittorrent memory usage for the last 90 days (version <= 5.2.0). It's really good, I'm sharing 400 torrents 24/7. <img width="974" height="390" alt="Image" src="https://github.com/user-attachments/assets/892ad21a-d9ce-4284-95c1-0c1e40f1e609" /> Yesterday I updated from qbittorrent:5.2.0 => qbittorrent:5.2.2 and there is a HUGE memory leak. It leaked 10 GB of memory in 1 day. At some point my server doesn't have more memory to use. The last 5 days. <img width="975" height="1181" alt="Image" src="https://github.com/user-attachments/assets/e6437a1b-6c47-4b44-9200-f070156be36c" /> I tried to rollback to version 5.2.0 and it seems it's not possible. qBittorrent restarts forever. I tried to rollback to version 5.2.1 and I see the same memory leak. ### Steps to reproduce _No response_ ### Additional context _No response_ ### Log(s) & preferences file(s) .

After the OOM message, I restarted qBittorrent and had 11.7G out of 16G free RAM… it’s leaking heap memory (10GB of anonymous RSS).

Trying this first - change the advanced setting for Disk IO to POSIX-compliant.

I already have a command to refresh qBittorrent if anyone’s interested, sometimes refreshes connections for me:

Summary

#!/bin/bash
# qbittorrent-session-reset.sh

# Gracefully stop qBittorrent
pkill -SIGTERM qbittorrent

# Wait until process exits
while pgrep qbittorrent >/dev/null; do
  sleep 1
done

# Optional: clear stats file (not strictly needed, but ensures reset)
CONFIG_DIR="$HOME/.config/qBittorrent"
rm -f "$CONFIG_DIR/qBittorrent-data.ini"

# Relaunch qBittorrent
qbittorrent &
sleep 4
qbittorrent &
notify-send --expire-time=3000 "Qbittorrent is refreshed and ready to serve!"

# Gracefully stop qBittorrent
pkill -SIGTERM qbittorrent

# Wait until process exits
while pgrep qbittorrent >/dev/null; do
  sleep 1
done

# Optional: clear stats file (not strictly needed, but ensures reset)
CONFIG_DIR="$HOME/.config/qBittorrent"
rm -f "$CONFIG_DIR/qBittorrent-data.ini"

# Relaunch qBittorrent
qbittorrent &
sleep 4
qbittorrent &
notify-send --expire-time=3000 "Qbittorrent is refreshed and ready to serve!"

stephane · 2 October 2026 16:29

i have this error for manjaro-settings-manager

:: Début de la mise à jour complète du système…
résolution des dépendances…
recherche des conflits entre paquets…
erreur : la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: l’installation de hwinfo (26.0-1) casse la dépendance « hwinfo<=26 » requise par manjaro-settings-manager

Teo · 2 October 2026 17:40

I think @Yochanan is the packager of msm.

GaVenga · 3 October 2026 10:05

I just noticed that GNOME 51 has landed in testing Arch-repos
– every man for himself!

AwwsmGaurav · 6 October 2026 13:57

I see there is an update to plymouth-theme-manjaro 2.2-6 -> 2.2-7 extra

Can I please know what’s the change, I couldn’t find the git repo…
I have a copy of that theme with a custom Image injected, just wanna know whats changed.

Updating it wont affect my copy theme, but last time there were some important changes like font and stuff for disk encryption or something, so I updated my theme to be based on new version.

Aragorn · 6 October 2026 13:59

Manjaro Theme in Plymouth shows wrong keyboard layout

Yochanan · 6 October 2026 20:30

Now that 2.16 is in the Manjaro repos, maybe you can test that instead of Arch’s package.

jrichard326 · 6 October 2026 23:19

I am running Xfce Unstable formatted ext4. I am able to boot successfully with GRUB 2.16, however, I don’t have an entry for UEFI firmware settings. All I see on cold boot are:

Manjaro Linux
Advanced options for Manjaro Linux.

I have added the parameters as noted by Stephane. With those suggested parameters I see UEFI firmware settings in EOS and Arch Virtual Machines. My entries are as follows:

#GRUB_DISABLE_OS_PROBER=false
GRUB_DISABLE_UEFI_FIRMWARE=true
GRUB_DISABLE_BOOTNEXT=true

GRUB_DISABLE_UEFI_FIRMWARE=false does not make any difference.

efibootmgr -v                                                            
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,0004
Boot0000* Manjaro	HD(1,GPT,579cf5cb-30eb-0b4f-82e0-bb597b4c711e,0x22,0x1007de)/\EFI\MANJARO\GRUBX64.EFI
      dp: 04 01 2a 00 01 00 00 00 22 00 00 00 00 00 00 00 de 07 10 00 00 00 00 00 cb f5 9c 57 eb 30 4f 0b 82 e0 bb 59 7b 4c 71 1e 02 02 / 04 04 36 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 41 00 4e 00 4a 00 41 00 52 00 4f 00 5c 00 47 00 52 00 55 00 42 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0001  UEFI: Built-in EFI Shell	VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
      dp: 04 03 14 00 5c b9 23 50 26 db 9b 42 a6 48 bd 47 66 4c 80 12 / 7f ff 04 00
    data: 00 00 42 4f
Boot0004  UEFI OS	HD(1,GPT,579cf5cb-30eb-0b4f-82e0-bb597b4c711e,0x22,0x1007de)/\EFI\BOOT\BOOTX64.EFI0000424f
      dp: 04 01 2a 00 01 00 00 00 22 00 00 00 00 00 00 00 de 07 10 00 00 00 00 00 cb f5 9c 57 eb 30 4f 0b 82 e0 bb 59 7b 4c 71 1e 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f

sudo update-grub                                                         
[sudo] password for jrichard: 
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-7.2-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-7.2-x86_64.img
Found linux image: /boot/vmlinuz-6.18-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.18-x86_64.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

Update:
The following was missing from the end of the 30_uefi-firmware file in /etc/grub.d

if [ "\$?" = 0 ]; then
		menuentry '$LABEL' \$menuentry_id_option 'uefi-firmware' ${allowed_user_list}{
			fwsetup
		}
	fi

I added the above, sudo update-grub and reboot fixed the issue.

Yochanan · 7 October 2026 13:29

Ah, oops. Fixed with 2:2.16-2 coming along shortly.

Yochanan · 7 October 2026 15:08

EDIT: Packaging is finished.

medmedin · 7 October 2026 20:27

The update wants to change:
from:
GRUB_CMDLINE_LINUX_DEFAULT="udev.log_priority=3 acpi_backlight=native resume=UUID=9f921366-4ebb-4b6b-aa6e-1fa19d252abc"

to:
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet rd.udev.log_level=3"

The final sould be:
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet rd.udev.log_level=3 acpi_backlight=native resume=UUID=9f921366-4ebb-4b6b-aa6e-1fa19d252abc"

or

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 rd.udev.log_level=3 acpi_backlight=native resume=UUID=9f921366-4ebb-4b6b-aa6e-1fa19d252abc"

https://wiki.archlinux.org/title/Silent_boot#Kernel_parameters

Note that this only seems to work if both quiet and loglevel=level are used, and they must be in that order (quiet first). The loglevel parameter will only change that which is printed to the console, the levels of dmesg itself will not be affected and will still be available through the journal as well as dmesg. For more information, see kernel parameters.

Yochanan · 7 October 2026 20:30

Pacnews don’t “want to change” anything. They are the defaults before Calamares makes changes to it. ~~You can ignore the pacnew and remove it~~.

EDIT: I suppose udev.log_priority=3 should be changed to rd.udev.log_level=3, I already made that change myself quite a while ago.

EDIT 2: Oh, turns out we need to change loglevel=3 quiet to quiet loglevel=3 for it to actually work. I’ll fix that here shortly.

medmedin · 7 October 2026 20:37

Thanks, it’s just this installation was installed since 2020 and I might missed merging some pacnew files, thanks I will only keep

GRUB_CMDLINE_LINUX_DEFAULT="rd.udev.log_level=3 acpi_backlight=native resume=UUID=9f921366-4ebb-4b6b-aa6e-1fa19d252abc"

fraz0815 · 8 October 2026 12:25

hello,
can anyone point me to the changes from gnome-shell 51.0-1 to 51.0-2.
51.0-1 crashed a lot when playing/decoding video files and mouse-over the player (eg chrome, mpv …).
51.0-2 fixed everything and arch still only lists 51.0-1, just wondering what caused the problems.

Thanks,

Aragorn · 8 October 2026 12:37

Normally, a change from -1 to -2 does not signify any change to the code, but rather a repackaging and/or a rebuild, e.g. due to a change in one or several dependencies.

GaVenga · 8 October 2026 13:33

Pamac Updates Indicator is “outdated”.

medmedin · 8 October 2026 13:36

For anyone who uses sleep then hibernate with kernel 7.2.x, and suffers from total black screen with frozen and unresponsive system, this helped me fixing the problem:

System does not power off when hibernating

Yochanan · 8 October 2026 15:30

Right here. I updated the patch borrowed from Ubuntu that restores XCursor compatibility. GNOME 51 only supports the SVG+JSON cursor format.

Initial GNOME 51 compatibility is now added with pamac-gtk 11.7.5-3.

GaVenga · 8 October 2026 15:59

Icons are missing in front of description…

[Unstable Update] October 2026

Recent News

Notable Package Changes

Known Issues

Additional Info

Manjaro Theme in Plymouth shows wrong keyboard layout