I installed manjaro-settings-manager-qt6 today, Xfce Unstable. I removed all of qt5 and replaced my last two pieces of software that required qt5, XnViewMP and KeepassXC, with the appimages directly from the developers and created launchers. I am glad to report all is well. I only use manjaro-settings-manager to check on kernels and add/remove kernels.
2 Likes
I dont know how I ended up here in Dev category… 
(ah yes, a support post was merged in here)
But I’ll keep unnecessary noise out of here onwards!
1 Like
Those plugins are the KCMs. 
1 Like
If so they’re not included in the new (or old) packages and the manjaro-settings-manager-kcm-qt6 package is not listed.
Also @lupine @Yochanan there are 2 packages providing manjaro-settings-manager-notifier, is this expected?
❯ pacman -Si manjaro-settings-manager-notifier-qt6 manjaro-settings-manager-kstatus-notifier
**Repository :** extra
**Name :** manjaro-settings-manager-notifier-qt6
**Version :** 0.6.0-3
**Description :** Manjaro Linux System Settings Tool (Notifier)
**Architecture :** x86_64
**URL :** https://gitlab.manjaro.org/applications/manjaro-settings-manager
**Licenses :** GPL-3.0-or-later
**Groups :** None
**Provides :** manjaro-settings-manager-notifier
**Depends On :** manjaro-settings-manager-qt6
**Optional Deps :** None
**Conflicts With :** manjaro-settings-manager-kde-notifier manjaro-settings-manager-notifier
**Replaces :** None
**Download Size :** 296.81 KiB
**Installed Size :** 536.13 KiB
**Packager :** Mark Wagie <mark@manjaro.org>
**Build Date :** 2026-08-30T00:55:36%:z
**Validated By :** MD5 Sum SHA-256 Sum Signature
**Repository :** extra
**Name :** manjaro-settings-manager-kstatus-notifier
**Version :** 0.6.0-3
**Description :** Manjaro Linux System Settings Tool (Notifier for Plasma 6)
**Architecture :** x86_64
**URL :** https://gitlab.manjaro.org/applications/manjaro-settings-manager
**Licenses :** GPL-3.0-or-later
**Groups :** None
**Provides :** manjaro-settings-manager-notifier
**Depends On :** kstatusnotifieritem manjaro-settings-manager-qt6
**Optional Deps :** None
**Conflicts With :** manjaro-settings-manager-notifier manjaro-settings-manager-knotifier
**Replaces :** manjaro-settings-manager-kde-notifier
**Download Size :** 297.50 KiB
**Installed Size :** 532.21 KiB
**Packager :** Mark Wagie <mark@manjaro.org>
**Build Date :** 2026-08-30T00:55:36%:z
**Validated By :** MD5 Sum SHA-256 Sum Signature
Right, they have been broken in qt5 or qt6 since kde6, I think, and were commented out around then?
I think this is expected, but will defer to people who know manjaro packaging better. Over in debian land we’d call it a virtual dependency - so other packages can depend on a notifier without having to choose between the kde or the qt one?
$ pamac search manjaro-settings-manager | grep -A1 notifier
manjaro-settings-manager-notifier-qt6 0.6.0-3 extra
Manjaro Linux System Settings Tool (Notifier)
manjaro-settings-manager-kstatus-notifier 0.6.0-3 extra
Manjaro Linux System Settings Tool (Notifier for Plasma 6)
manjaro-settings-manager-knotifier 0.5.8-10 extra
Manjaro Linux System Settings Tool (Notifier for Plasma 5)
manjaro-settings-manager-notifier 0.5.8-10 extra
Manjaro Linux System Settings Tool (Notifier)
2 Likes
Of the 2 in version 0.6x what are the differences? Obviously one is qt6 (*-notifier-qt6), but wasn’t the whole thing moved to qt6? Then that leaves *-kstatus-notifier which has a description stating Plasma 6, but wouldn’t the qt6 one work also and if not when would one choose the *-notifier-qt6 package?
I don’t profess to know exactly what, but the “k” is usually a good indicator that something specific has warranted a separate approach for KDE.
Despite KDE being arguably based on Qt6, the separate logic is likely to conform with something Plasma GUI related; at least, that would be my guess.
1 Like
manjaro-settings-manager-kstatus-notifier uses KDE for notifications. I assume it integrates nicely with plasma and I think it provides a KDE systray icon. It depends on Kf6 so pulls a bunch of KDE dependencies.
manjaro-settings-manager-notifier-qt6 is to be installed when you’re not using KDE, i.e., a gnome/xfce desktop, and only relies on Qt. No KDE systray icon.
3 Likes
Things have apparently changed on account of how the KCMs interface with System Settings, and @lupine made an effort at creating a KCM for his new Manjaro Settings Manager with the help of @yochanan, but it proved too difficult for now, especially since he’s not a Plasma user.
1 Like
As do I. So I wrote my own Kernel Manager in Python, and removed MSM completely.
The other MSM modules are taken care of by KDE System Settings.
1 Like
Um, not really — none of the manjaro-settings-manager modules work with the System Settings of Plasma 6.x. But then again, I don’t have manjaro-settings-manager on my system anymore either — nor mhwd — because I’m a more experienced user and I can use the regular tools, and I don’t have any Nvidia hardware in my system, or for that matter, other proprietary stuff.
Everything on my system is FLOSS, and my hardware is bog-standard: Intel CPU, onboard Intel GPU, onboard sound chip, and onboard Ethernet adapter. And my system is installed in US English, so I don’t need any language packs.
2 Likes
Just out of pure curiosity, why? You’re Belgian.
1 Like
I imagine it’s like a gratitude meditation. Every time he boots his PC its a reminder that he isn’t American and things could indeed be worse.
5 Likes
For several reasons.
-
First of all, even though my native tongue is Dutch — or rather, a regional Flemish dialect of Dutch — I am for all intents and purposes an anglophone. I even think in English.
-
Secondly, UNIX systems were developed in the USA, and at the very deepest level, their code falls back onto the (linguistic) language of the C (programming) language, which is US American. As such, sticking to US English as the language for the entire operating system — which in a UNIX context includes application software, because UNIX integrates its applications as mere extra tools in the operating system — does not yield any unexpected translation artifacts.
I don’t reboot very often. 
My computer is up 24/7 — no sleep mode or hibernation — although installing a single package or updating the few fast-tracked packages we have does require me to soft-reboot, because I have /usr as a separate and read-only-mounted btrfs subvolume, and once you remount that as read/write, it becomes part of the writable pool of space in the filesystem, and there is no way to remount it read-only again, save a (soft or hard) reboot.
I’ve just had to do it again tonight, because there was an update to chromium, which is one of the fast-tracked packages, and new versions appear in the repo roughly every week.
A soft reboot is quite handy. It only reboots userspace — the kernel remains fully operational — and it takes only about 3 or 4 seconds before you see the GUI login screen.
systemctl soft-reboot
You don’t even have to use sudo if you’re the person sitting at the local console. logind keeps into account where you are logged in from.
3 Likes
It should be possible to set up Australian English so that it reads exactly as they speak it!
Crikey! Something’s gone pear-shaped, mate. Give it another burl.
Strewth, mate! The bloody thing’s thrown a wobbly. Have another crack.
5 Likes
I’d like to point out not everybody is using KDE Plasma. XFCE for example is a lot simpler and beleive it or not has no native GUI setting for setting the clock or timezone for example, i can also imagine a lot of the spins that only rely on WMs and are not with full blown DEs have also not that much in the GUI settings department.
MSM fills exactly the lacking settings GUI modules in XFCE, which is officially supported by manjaro, so it is super important.
7 Likes
Stone the crows, don’t scare him 
1 Like
@lupine Everything is now moved to the new Manjaro Forgejo instance:
Feel free to register an account and setup the fork there.