The issue you had to fix, was caused by using the illegal command.
sudo pamac update
Do not use sudo with pamac.
4 Likes
Downgrading the package did indeed restore functionality to normal. However, this does of course trigger the octopi-notifier â or its pamac equivalent â to prompt one that an update for plasma-applet-window-buttons is waiting, so one has to add the package to the IgnorePkg stanza in /etc/pacman.conf for the time being.
I will edit the wiki post and add this information to it. Still, ignoring packages is never a good idea, so hereâs hoping that the next update will fix things.
Please keep us informed as to when it is safe to remove the IgnorePkg entry. 
Edit: Philip has pulled the faulty plasma-applet-window-buttons version 0.14.0-3 and replaced it in the repo by 0.14.0-2 again.
Therefore, I will edit my addition to the wiki post, for those who had updated their systems but did not downgrade the package yet â provided you have it on your system, of course. If you are one of those people, run⊠
sudo pacman -Syuu
⊠just once for now. This will pull in the correct version.
1 Like
From my understanding, KDE supports X11. Till at least early 2027
More precisely, Plasma 6.8 will completely be dropping all X11 support, so itâll still be supported in 6.6.x and 6.7.x, but after that itâs game over, unless somebody were to fork Plasma and continue offering X11 support.
2 Likes
KDE Plasma users with SDDM can now migrate to Plasma Login Manager
After ensuring
plasma-login-manager6.5.90-1 (or newer) is installed, run the following:sudo pacman -Syu plasma-login-manager systemctl disable sddm systemctl enable plasmalogin sudo pacman -R sddm-kcm sddm
Well, that failed miserably for me. After reboot, screen went black. Keyboard was still responsive, but I wasnât able to CTRL+ALT+Fx into any of the ttys to switch the systemd units back (I didnât uninstall sddm as precaution).
Had to connect via SSH into my machine to revert that back (I did boot a previous btrfs snapshot from minutes before the update, but that one had no network for some strange reason).
EDIT: Below relevant log entries. Seems like folder /var/lib/plasmalogin is missing.
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Initializing...
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Starting...
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Logind interface found
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Adding new display...
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Using VT 1
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Display server started.
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Socket server starting...
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Socket server started.
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Greeter starting...
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: [PAM] Starting...
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: [PAM] Authenticating...
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: [PAM] returning.
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: pam_unix(plasmalogin-greeter:session): session opened for user plasmalogin(uid=952) by (uid=0)
MĂ€r 25 09:25:13 freedom systemd-logind[2495]: New session 'c1' of user 'plasmalogin' with class 'greeter' and type 'wayland'.
MĂ€r 25 09:25:13 freedom (systemd)[2641]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[plasmalogin] ruser=[<unknown>] rhost=[<unknown>]
MĂ€r 25 09:25:13 freedom (systemd)[2641]: pam_unix(systemd-user:session): session opened for user plasmalogin(uid=952) by plasmalogin(uid=0)
MĂ€r 25 09:25:13 freedom systemd-logind[2495]: New session '1' of user 'plasmalogin' with class 'manager-early' and type 'unspecified'.
MĂ€r 25 09:25:13 freedom systemd[1]: Started Session c1 of User plasmalogin.
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: Starting Wayland user session: "/usr/share/plasmalogin/scripts/wayland-session" "/usr/bin/startplasma-login-wayland"
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2719]: Jumping to VT 1
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2719]: VT mode fixed
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2719]: chdir( /var/lib/plasmalogin ) failed for user: "plasmalogin"
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2719]: verify directory exist and has sufficient permissions
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Greeter session started successfully
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: pam_unix(plasmalogin-greeter:session): session closed for user plasmalogin
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: [PAM] Closing session
MĂ€r 25 09:25:13 freedom plasmalogin-helper[2638]: [PAM] Ended.
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Auth: plasmalogin-helper exited with 3
MĂ€r 25 09:25:13 freedom plasmalogin[2636]: Greeter stopped. PLASMALOGIN::Auth::HELPER_OTHER_ERROR
MĂ€r 25 09:25:23 freedom (sd-pam)[2695]: pam_unix(systemd-user:session): session closed for user plasmalogin
EDIT 2: Something is not creating the home folder /var/lib/plasmalogin for the plasmalogin user as instructed in the post installation steps.
Post-installation steps
By default, PLASMALOGIN runs as its own user. An
plasmaloginuser needs to be created, with its home set to/var/lib/plasmaloginby default.
We should probably NOT recommend switching to plasma-login-manager until this is fixed upstream.
EDIT 3: Official repo creates a file in /usr/lib/sysusers.d/plasmalogin.conf, and mentions to run following command to create the user:
sudo systemd-sysusers
This seems to happen, and user plasmalogin exists in the system, but this command does not automatically create the necessary home folder. Maybe a bug in systemd-sysuser itself?
EDIT 4: From systemd-susysers
systemd-sysusers only sets the home directory record in the user database. To actually create the directory, consider adding a corresponding tmpfiles.d(5) fragment.
EDIT 5: Following file exists! /usr/lib/tmpfiles.d/plasmalogin.conf with following content:
# Home dir of the plasmalogin user, also contains state.conf
d /var/lib/plasmalogin 0750 plasmalogin plasmalogin
# This contains X11 auth files passed to Xorg and the greeter
d /run/plasmalogin 0711 root root
# Sockets for IPC
r! /tmp/plasmalogin-auth*
# xauth files passed to user sessions
r! /tmp/xauth_*
# "r!" above means to remove the files if existent (r), but only at boot (!).
# tmpfiles.d/tmp.conf declares a periodic cleanup of old /tmp/ files, which
# would ordinarily result in the deletion of our xauth files. To prevent that
# from happening, explicitly tag these as X (ignore).
X /tmp/plasmalogin-auth*
X /tmp/xauth_*
So, what failed?
EDIT 6: Found the issue. systemd-tmpfiles was failing due to a folder ownership mismatch between / and /var.
TL;DR: Package is fine. Issue was due to local system specific issue (arch comment).
3 Likes
I canât confirm this. I checked on stable and unstable but the versions of dolphin and krusader and kdeframeworks as well as Qt are all the same (on stable and unstable branch) and WebDAV and Samba works fine with dolphin and krusader.
This may have different causes - hard to tell from here without further information. Maybe open a new topic for help.
3 Likes
In my case, plasma-login-manager starts with session X11 even if I have set the login session to wayland session. Sddm starts into Wayland without problems.
My updates went fine with two machines. This time Pamac did not even close the GUI when doing the updates.
Yeah I noticed it relatively late. Thanks for the solution to get it starting again 
Thanks for your feedback! good to know it should work. I might delete the settings and cache files and continue investigating the issue. If I find anything, Iâll let you know.
Update 2026-03-25 5pm: Todayâs update to extra/plasma-workspace 6.5.6-2 has fixed the problem. Thanks!
Hello, I donât know what to answer at that question:
:: Remplacer kdsoap-qt6 par extra/kdsoap ? [O/n] o
rĂ©solution des dĂ©pendancesâŠ
recherche des conflits entre paquetsâŠ
:: kdsoap - 2.3.0-1 et kdsoap-qt5 - 2.2.0-1 sont en conflit. Supprimer kdsoap-qt5 ? [o/N]
I answered Yes for the replacement of kdsoap-qt6 by extra/kdsoap, but it seems that the recommended answer for deleting kdsoap-qt5 is NoâŠ
Someone already has, or at least parts of it:
2 Likes
Having issues with Mesa I think; black screen with Picom, Crimson Desert suddenly doesnât launch with raytracing anymore and has a weird graphical issue where lighting or some shader is only in the top left corner.
Is there a way to downgrade Mesa without breaking future updates (if thats the source of the issue)?
Edit: Switched to CachyOS, it doesnât have this issue
Iâm just confirming that this update fixes an issue where gvim would always consume 100% CPU in Wayland. Thanks.
1 Like
Hey there. The update went smoothly on two out of three machines.
On my last machine, Iâm struggling with the following problem, which I havenât been able to fix yet:
error: highway: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/highway-1.3.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: libjxl: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/libjxl-0.11.1-5-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: libvpl: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/libvpl-2.16.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: libmfx: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/libmfx-23.2.2-5-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: gsfonts: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/gsfonts-20200910-6-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: mujs: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/mujs-1.3.8-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: pkgfile: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/pkgfile-25-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
Itâs exactly the same problem as described in the following forum post: Marginal Trust invalid or corrupt package Error while updating manjaro
Does anyone have any idea how to fix this error? Thanks in advance.
2026-02-23
Possible signature validity issues with packages taken over from Arch
Right at the top of the topicâŠ
1 Like
Thanks! Those who can read have a clear advantage - and sometimes youâre blind .-)
2 Likes
You should remove kdsoap-qt5 as it is a package that is no longer in the repositories:
pamac search kdsoap
mingw-w64-kdsoap 2.1.1-1 AUR
Qt-based client-side and server-side SOAP component (mingw-w64)
kdsoap-qt6-git 2.2.1_r1966.gd56e5ce3-1 AUR
Qt-based client-side and server-side SOAP component
kdsoap-qt5-git 2.2.1_r1966.gd56e5ce3-1 AUR
Qt-based client-side and server-side SOAP component
kdsoap-ws-discovery-client 0.4.0-3 [Installed] extra
WS-Discovery client library based on KDSoap
kdsoap 2.3.0-1 [Installed] extra
Qt-based client-side and server-side SOAP component
The kdsoap package now provides kdsoap-qt6:
pamac info kdsoap | grep -Ei "name|version|provides|replaces"
Name : kdsoap
Version : 2.3.0-1
Provides : kdsoap-qt6
Replaces : kdsoap-qt6
2 Likes
No issues for me.
Thanks for the update guys!
2 Likes
Thunderbird cannot be started after the upgrade and crashes with:
Illegal instruction (core dumped) thunderbird
CPU AMD Athlon II X2 250e
Downgrading from 148.0.1-2 to 148.0-2 makes it work again.
EDIT: The same problem with KeePassXC 2.7.12-2.
EDIT2: Reported to be related to Botan update, used by both the programs.
EDIT3: Fixed in botan 3.11.0-1.0. 