Had an issue with kwallet, followed instructions here to fix it. Bummer it logged me out of all my accounts on Brave though. Oh well
Actually, even though I voted “no issues”, I’ve just noticed a regression in klipper, or at least, running on Wayland — I’m not going to be trying X11.
It’s an issue that got remedied in the previous Plasma update, but which has now returned, namely that if one selects text with the mouse, then the entire clipboard — or at least, for as many characters as you’ve selected/copied in relation to the number of entries your clipboard history can store — will be filled with partial copies gradually increasing in length until the final length of the selected string is reached.
Hopefully the screenshot below will adequately illustrate what I mean… 
This is with the setting “Keep the selection and the clipboard the same”, which is the default modus operandi of a UNIX clipboard.
Has the pamac issue been resolved with this update? i.e is it still required to run the gtk3 version (Wayland)?
I didn’t realise that was an issue. Your user profile says you are using Plasma, so you should be using pamac-gtk3.
2 Likes
Sorry, I’ve updated my profile now. I’m on X11 but I tried switching to Wayland and experienced the same problem.
Upgrading to kernel 6.12 seems to have helped a lot. I was on 6.6 and for some reason it wasn’t automatically switching to 6.12 after I installed it in Manjaro Settings Manager, so I selected it manually from the grub menu. I think it’s back to normal performance now.
CC @TheDubster
1 Like
This is all a bit weird. Things seem to have improved overnight without me doing anything. No reboot, nothing. I’m using Plasma Wayland and the 6.12 Kernel. My other machine is using X11 and didn’t experience any of those problems. Fingers crossed it stays like that.
Interestingly mine has a few extra lines that I have no idea how they got there. Mind you, I did merge the last passwd.pacnew
# Pathnames of valid login shells.
# See shells(5) for details.
/bin/sh
/bin/bash
/bin/rbash
/bin/zsh
/usr/bin/sh
/usr/bin/bash
/usr/bin/rbash
/usr/bin/zsh
/usr/bin/git-shell
/usr/bin/systemd-home-fallback-shell
If I understand this correctly, this file is a sort of whitelist for shells allowed, in which case would it be best to leave those in?
1 Like
Not sure how that got there, but it was in mine as well. I’m guessing it may have come as part of the zsh-theme-powerlevel10k package, but I can’t be sure about that.
I either way don’t use git, so I had deleted that line. But I’ve restored it now. 
This is part of systemd-homed, which I don’t use, and of which I think there won’t be too many who do.
systemd-homed is one of those solutions to a problem that doesn’t actually exist in this universe.
1 Like
The update (ignoring the pacnews) went ok, thanks!
I have the now, for me, weekly fight with the Palo Alto Global Protect, of which I have just the binary. Now is failing because it misses
libxml2.so.2 => not found
…is there some good samaritan here that can help me to find a version of that file so I can put it in the frigging global protect directory? And yes, people that distribute things binary-only should have the good taste of statically linking them…
I don’t use it myself, but it looks like you might find it in the libxml2-legacy package which is in the extra repoo:
~ > pkgfile libxml2.so.2 4s
extra/libxml2-legacy
~ >
2 Likes
Yes, thanks a lot! Yo usaved my day
1 Like
No It shut down again for me when doing the full system update
@gnoumph @tracyanne I think I found out why:
- Kwallet implements Secret Service Desktop Portal
- XDG desktop portal is broken on this release, see Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory · Issue #1653 · flatpak/xdg-desktop-portal · GitHub
- This also breaks OBS/Discord screen sharing (via PipeWire)
- I also have issues with theme being out of sync with KDE on GTK4 apps, but not sure if that’s related to the portal
- There is a proposed patch in mentioned issue for kernel 6.11+
- If multiple people would confirm the fix could the patch please be included in the manjaro package (
xdg-desktop-portal)?
To verify, try systemctl --user status xdg-desktop-portal, mine fails with:
Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
2 Likes
Thanks, I actually rolled back kwallet, so I don’t get that failure.
It’s interesting just how many subsystems can be affected by even a small issue like this, and why partial updates can be such a huge problem.
2 Likes
No, that’s just gtk4. The gtk developers have a rather… solipsistic view on the universe. 
3 Likes
A couple of people (self professed noobs?) in this thread said they just ignored the 2 pacnew file warnings (and did nothing) and everything was (seemed?) OK. If you’ve never manually made any changes to your files, can that be done? I’m on XFCE, terrified of getting locked out of my system (work cannot stop).
I never actually log out, the only time I have to use my password is when the darn laptop lid closes by mistake and does not follow my choice in the settings: “do nothing”. Instead it requires me to use my password.
There is action implied in the pacnew files warning that I don’t have my head around. I don’t have a backup system in place because I have too many files on my desktop, seems unmanageable to backup everything. What I’ve been doing is update 2 other adjunct XFCE systems first and if those go ok then update my main machine.
In theory, if you’ve never made any changes to your configuration files, then they would be overwritten with the new defaults, and any .pacnew files will only be created if you have modified your configuration files.
In practice however, changing settings by way of GUI tools such as System Settings may modify such configuration files in the background without that you realize it. Likewise for the installation of certain packages.
So it is always best to compare the .pacnew files with the originals and to merge the changes, thereby utilizing common sense. One of our developers has created a gtk-based GUI tool for doing that, called manjaro-pacnew-checker. Personally, I prefer the qt-based pacnew-chaser from the AUR, which I’ve already been using from before manjaro-pacnew-checker was developed.
Buy yourself an external drive that connects to your laptop via USB, create a big ext4 partition on it, and — as root — make a full copy of your home directory on it every day.
The operating system can always be reinstalled, and if you’ve customized certain system-wide settings and/or added packages, then it’ll be quite a bit of work to get everything back, but in the end, it’s perfectly doable. Your personal files however are priceless, and you don’t want to lose those. So back them up before it’s too late.
3 Likes
Unless, of course, you also use something like this:
https://github.com/hectorm/hblock
So, like it is said, do not blindly copy over your existing file/-s!
Plus I have additional edits of my own to rid myself of other nasty things.
1 Like
Terrible update for nvidia/X11 users (as usual this year). Plasma 6.3.5 now gives black screen when connecting any external screen on the up-to-date driver. The up-to-date nvidia driver still has kernel hang issues, but now also the 535 driver from AUR, which used to work perfectly in my system, no longer works after this update.
You should find it in the backup you took before upgrading. Er, you did take a backup?
Now there’s a user sleepwalking into disaster.
1 Like