Welcome to the new monthly unstable branch thread.
dovecot >= 2.4 requires manual intervention
2025-10-31 - Thore Bödecker
The dovecot 2.4 release branch has made breaking changes which result in it being incompatible with any <= 2.3 configuration file.
Thus, the dovecot service will no longer be able to start until the configuration file was migrated, requiring manual intervention.
For guidance on the 2.3-to-2.4 migration, please refer to the following upstream documentation: Upgrading Dovecot CE from 2.3 to 2.4
Furthermore, the dovecot 2.4 branch no longer supports their replication feature, it was removed.
For users relying on the replication feature or who are unable to perform the 2.4 migration right now, we provide alternative packages available in [extra]:
dovecot23
pigeonhole23
dovecot23-fts-elastic
dovecot23-fts-xapian
The dovecot 2.3 release branch is going to receive critical security fixes from upstream until stated otherwise.
– Arch Linux - News: dovecot >= 2.4 requires manual intervention
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
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
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
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
Info about AUR packages
Arch User Repository ) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements
For help with AUR packages, please create a new topic in Support > AUR
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:
4 Likes
Updating kernel 6.18-rc4
Building image from preset: /etc/mkinitcpio.d/linux618.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.18-x86_64 -g /boot/initramfs-6.18-x86_64.img
==> Starting build: '6.18.0-rc4-1-MANJARO'
/usr/bin/mkinitcpio: Zeile 791: _addedmodules[${modname//-/_}]: Falscher Feldindex.
3 posts were merged into an existing topic: The Official Manjaro Staff Lounge
philm
4 November 2025 15:11
6
The English error is /usr/bin/mkinitcpio: line 791: _addedmodules[${modname//-/_}]: bad array subscript on linux618 . Full code snippet is:
preload_builtin_modules() {
local modname field value
local -a path
# Prime the _addedmodules list with the builtins for this kernel. We prefer
# the modinfo file if it exists, but this requires a recent enough kernel
# and kmod>=27.
if [[ -r $_d_kmoduledir/modules.builtin.modinfo ]]; then
while IFS=.= read -rd '' modname field value; do
_addedmodules[${modname//-/_}]=2
case "$field" in
alias)
_addedmodules["${value//-/_}"]=2
;;
esac
done <"$_d_kmoduledir/modules.builtin.modinfo"
elif [[ -r "$_d_kmoduledir/modules.builtin" ]]; then
while IFS=/ read -ra path; do
modname="${path[-1]%.ko}"
_addedmodules["${modname//-/_}"]=2
done <"$_d_kmoduledir/modules.builtin"
fi
}
Most likely mkinitcpio needs an update as cat /usr/lib/modules/6.18.0-rc4-1-MANJARO/modules.builtin.modinfo has a different format as /usr/lib/modules/6.17.7-1-MANJARO/modules.builtin.modinfo has. Most likely due to: Merge patch series "Add generated modalias to modules.builtin.modinfo" · torvalds/linux@c7d3dd9 · GitHub
3 Likes
$ uname -r
6.18.0-rc3-1-MANJARO
giving this in the output
==> Starting build: '6.18.0-rc4-1-MANJARO'
/usr/bin/mkinitcpio: line 791: _addedmodules[${modname//-/_}]: bad array subscript
but I didn’t notice this before the mention here
It is not in the pacman.log and for as far as mkinitcpio - the image generation is a success…?
(3/5) Install DKMS modules
==> dkms install --no-depmod vmware-workstation/25H2_24995812 -k 6.18.0-rc4-1-MANJARO
==> depmod 6.18.0-rc4-1-MANJARO
(4/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux618.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.18-x86_64 -U /efi/EFI/Linux/manjaro-6.18-x86_64.efi --splash /usr/share/systemd/bootctl/splash-manjaro.bmp
==> Starting build: '6.18.0-rc4-1-MANJARO'
/usr/bin/mkinitcpio: line 791: _addedmodules[${modname//-/_}]: bad array subscript
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [kms]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Creating unified kernel image: '/efi/EFI/Linux/manjaro-6.18-x86_64.efi'
-> Using ukify to build UKI
-> Using cmdline file: '/etc/kernel/cmdline'
-> Using cmdline file: '/etc/cmdline.d/root.conf'
-> Using cmdline file: '/etc/cmdline.d/security.conf'
Using config file: /etc/kernel/uki.conf
Wrote unsigned /efi/EFI/Linux/manjaro-6.18-x86_64.efi
==> Unified kernel image generation successful
==> Running post hooks
-> Running post hook: [sbctl]
Signing /efi/EFI/Linux/manjaro-6.18-x86_64.efi
✓ Signed /efi/EFI/Linux/manjaro-6.18-x86_64.efi
==> Post processing done
philm
4 November 2025 16:43
11
Before 6.18rc1 generated modaliases were not part of the modinfo file. Mkinitcpio needs to adopt and filter those out @linux-aarhus
2 Likes
something not good for Zen5 and RDSEED ( microcode)
no good soluce for the moment
philm
5 November 2025 01:15
13
@stephane seems people like drama where is no drama …
Upstream Arch has made changes to mkinitcpio.
These will possibly address the issues seen with image generation as the mkinitcpio package in the manjaro repos are from December 18. 2024 @Yochanan
Tested the upstream mkinitcpio 40-1 (core-testing) and it throws the same message with Manjaro kernel (6.18rc4).
No other kernel like 6.12 or 6,17 is affected - for the sake of completeness
mkinitcpio 40-1 (core-testing)
install: “removed lvm2 (2.03.36-1)” - is this good??==> ERROR: file not found: '/usr/lib/systemd/systemd-validatefs' sudo mkinitcpio -P
The issue is mkinitcpio specific and should be reported here:
I agree - I am in the process of verifying on my laptop running Arch Linux - but building a kernel takes time
2 Likes
That requires systemd 258. Both will be updated at the same time sometime after mkinitcpio 40 graduates from Arch Testing. DO NOT report upstream issues unless you’re using Arch.
1 Like
philm
5 November 2025 18:03
20
Using the latest packages is not always the greatest …
1 Like
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.