Apparently reinstalling the application is all it takes. Although you may — as suggested elsewhere already — want to switch from keepass (which relies on mono, a Windows technology) to keepassxc (which is a native UNIX implementation).
Okay I did sudo pacman -S keepass and it did it like it has never been installed before. It looked like it was a fresh install, not some kind of a repair.
Yes, that appears to be how to work around the issue. As I understand it — but I have not been following the discussion closely — the change that broke the existing installation was in mono, which — as I said above — is an Open Source attempt at duplicating a proprietary Microsoft technology, not a native UNIX technology.
Not all of them, no, because Manjaro GmbH — which is the commercial wing of the Manjaro distribution — maintains certain promotional deals with proprietary software vendors.
Therefore, we do for instance carry the commercial and proprietary Softmaker Office — three versions: softmaker-office-2021, softmaker-office-2024 and softmaker-office-nx — in our Extra repository. And let’s not forget that we also offer proprietary video and network drivers for those who need them, as most distributions do.
We do however try to stick with (and recommend) Free & Open Source Software where possible, and in that, we largely follow Arch proper.
A little bit off topic, but I will ask here anyway.
When I do yay -Sua I get this:
:: Searching AUR for updates...
-> Packages not in AUR: libsidplay manjaro-documentation-en manjaro-firmware nerd-fonts-noto-sans-mono noto-fonts-compat systemd-fsck-silent
there is nothing to do
should I be concerned about it? I have systemd-fsck-silent in mind particularly
Those are packages which have either been dropped from the repository and never been added to the AUR, or packages that were dropped from the AUR itself. In other words, they are orphans.
I too have a systemd-fsck-silent service installed here — I don’t know where it comes from or what it does, but it’s either way disabled. I don’t see it in the package manager, so perhaps it was never a standalone package, but rather just something that was dropped from systemd during an upgrade.
Edit: Upon closer inspection, I no longer seem to have systemd-fsck-silent on my system, so I’m guessing that the most recent update to systemd removed it. I am certain that it was still on my system before the update.
It’s an orphan. Nothing depends on it, so nothing will break. The same goes for the other packages in that list…
libsidplay # for playing old arcade game ROM images
manjaro-documentation-en # has been repackaged into other packages
manjaro-firmware # has been repackaged into other packages
nerd-fonts-noto-sans-mono # has been repackaged into other packages
noto-fonts-compat # has been repackaged into other packages
It’s because I monitor the Announcements threads. Which every Manjaro user should do.
Sometimes packages are installed as dependencies when they shouldn’t be, and removing certain other packages would then also remove the (fake) dependencies. -Rdd prevents that from happening. See…
