I guess it wasn’t firmware then 
I don’t see anything in my pacman log that would affect this either, except perhaps the kernel.
I’m reviewing my .pacnew files, and after this update there’s a /etc/pam.d/sudo.pacnew with the following content:
#%PAM-1.0
auth include system-auth
account include system-auth
session include system-auth
session optional pam_systemd.so class=none
which would replace my current /etc/pam.d/sudo:
#%PAM-1.0
auth required pam_env.so
auth sufficient pam_fprintd.so
auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
auth include system-auth
account include system-auth
session include system-auth
(though I don’t remember editing that file previously…)
I’m definitely not an expert, so when it comes to authentication and security I prefer to double-check.
Should I use the content of the .pacnew file? Bonus if someone knows why this change happened 
All you need to do is merge that in at the bottom.
2 Likes
Everything appears to have updated fine on both my XFCE and KDE machines thanks.
One little odd thing I noticed was that the Firefox VPN was available to use in the KDE build but not the XFCE build. The button and option to use it showed in one but not the other 
Fixed the issue by running:
localectl --no-convert set-x11-keymap de
Edit: Helpful ArchWiki article.
1 Like
Thanks! Can confirm 
Added Plasma 6.6.6: KDE Plasma 6.6.6, Bugfix Release for July - KDE Community
ISOs including this update: Release 202607081251 · manjaro/release-review · GitHub
2 Likes