Welcome to the new monthly unstable branch thread.
Recent News
Kernel 6.16 is now EOL
6.16.12 is the last maintenance release of the 6.16 kernel series. This kernel is now marked ‘End Of Life’ (EOL). It is recommend to switch to the newer linux617 series:
sudo mhwd-kernel -i linux617
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.
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]:
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
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.
There seems to be a non-functional post-update hook in today’s updates. Probably bound to update on openssh? Not sure what effect this has, since I’m not using SSH for anything at this time.
:: Running post-transaction hooks...
( 1/10) Creating system user accounts...
( 2/10) Reloading system manager configuration...
( 3/10) Reloading user manager configuration...
( 4/10) Restarting marked services...
( 5/10) Creating temporary files...
( 6/10) Arming ConditionNeedsUpdate...
( 7/10) Restart a running sshd.service
Invalid operation 'restart'
error: command failed to execute correctly
( 8/10) Updating fontconfig cache...
( 9/10) Updating 32-bit fontconfig cache...
(10/10) Updating X fontdir indices...
That error message appears even for an enabled sshd service…
Manjaro still has older systemd 257.9 compared to Archs 258 and its /usr/share/libalpm/scripts/systemd-hook is missing the restart action, which was introduced recently:
Updateing core/openssh from 10.0p1-5 to 10.0p1-6 resulted in above error message, with systemd 259.9-1 installed.
Did today’s systemd 259.9-2 update correct this, since now the post-transaction-hook successfully restarts ssh-service?
That brings me to the question if the arch and manjaro systemd packages are comparable at all when looking at the package release numbering?
mbn info systemd -q 99 ✘ 12s
Branch : archlinux
Name : systemd
Version : 258-4
Repository : core
Build Date : Wed 24 Sep 2025 11:18:01
Packager : Christian Hesse <eworm@archlinux.org>
Branch : unstable
Name : systemd
Version : 257.9-2
Repository : core
Build Date : Fri 03 Oct 2025 10:37:37
Packager : Philip Mueller <philm@manjaro.org>
Branch : testing
Name : systemd
Version : 257.9-2
Repository : core
Build Date : Fri 03 Oct 2025 10:37:37
Packager : Philip Mueller <philm@manjaro.org>
Branch : stable
Name : systemd
Version : 257.9-1
Repository : core
Build Date : Thu 04 Sep 2025 16:19:02
Packager : Philip Mueller <philm@manjaro.org>
Sure, why wouldn’t they be? They are almost the same (*), at the moment Arch already made the transition to 258 and Manjaro unstable for some (unknown) reason did not (yet)..
The “problem” observed here is not a difference in systemd (as provided by upstream) but in distro provided alpm helper script - and it’s now (as of 257-9-2) functionally equivalent to Archs 258 version.
edit for (*) : The packages in and of themselves are as long as the version numbers are roughly equal of course. Archs 258 is obviously a newer upstream release than Manjaros 257.
IMO i’m glad manjaro team chose to withhold systemd 258, arch first released 258 in the 3rd week (or so) of September, and there have been countless issues (4 revisions, 15+ commits to fix issues to date; Commits · main · Arch Linux / Packaging / Packages / systemd · GitLab). though on the surface everything seems to be ok on my arch setups now, i’m not sure whether its the last of it.
usually, whenever there is a new systemd release manjaro releases as soon as it’s available. at times, i’ve seen manjaro systemd overlay being released here on the unstable branch, even before arch has it on “arch-unstable”.
You must have some typo when copying that message: 1:0.5.2-1 might have been a previous version (notice the colon to indicate an epoch), the current one does seem to be 0.5.2-2 (notice the missing epoch) and that version technically is lower.
Arch moved that package from AUR to extra just 4 days ago:
Perhaps your currently installed one was built from AUR or was Manjaro provided?
In Qt 6.10 the Qt Wayland client library and platform plugin have moved to qt6-base. The qt6-wayland package contains only the Wayland compositor libraries.
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.