Sorry to bother but I trying to understand what is going on with kwalletmanager in my system. I am using Plasma for some time now and since version 6.x I lost access to the kwallet manager. I sit on this for a while since I thought that was something to be fix globally, but now I am starting to think that is something particular on my system that isn’t working as should be. I mean, the service seems to be working, but I cannot run kwallet manager to manage stored passwords and such.
The shortcut I have in plasma menu (6.2.4 at this moment) is pointing to kwalletmanager5 but when I tried to run it, nothing happens (the first time after a boot, the app icon appear for a moment in the task bar and then disappears).
This are the packages I have installed:
pacman -Qs kwallet
local/ksshaskpass 6.2.4-1 (plasma)
ssh-add helper that uses kwallet and kpassworddialog
local/kwallet 6.8.0-1 (kf6)
Secure and unified container for user passwords
local/kwallet-pam 6.2.4-1 (plasma)
KWallet PAM integration
local/kwallet5 5.116.0-1 (kf5)
Secure and unified container for user passwords
local/kwalletmanager 24.08.3-1 (kde-applications kde-utilities)
Wallet management tool
local/signon-kwallet-extension 24.08.3-1 (kde-applications kde-network)
KWallet integration for signon framework
I thought I had some old installation shortcut and I was missing something like kwalletmanager6 but not seems to be the case since kwalletmanager package only has kwalletmanager5 in it:
checking dependencies…
warning: removing frameworkintegration5 from target list
warning: removing kconfig5 from target list
warning: removing kconfigwidgets5 from target list
warning: removing kguiaddons5 from target list
warning: removing kiconthemes5 from target list
warning: removing kirigami2 from target list
warning: removing kwindowsystem5 from target list
warning: removing kcompletion5 from target list
warning: removing kcoreaddons5 from target list
warning: removing kcrash5 from target list
warning: removing ki18n5 from target list
warning: removing kitemviews5 from target list
warning: removing kio5 from target list
warning: removing kjobwidgets5 from target list
warning: removing kwidgetsaddons5 from target list
warning: removing kxmlgui5 from target list
warning: removing kwayland5 from target list
warning: removing ktextwidgets5 from target list
warning: removing kwallet5 from target list
warning: removing kauth5 from target list
warning: removing kitemmodels5 from target list
warning: removing knotifications5 from target list
warning: removing knewstuff5 from target list
warning: removing kcodecs5 from target list
warning: removing karchive5 from target list
warning: removing solid5 from target list
warning: removing kbookmarks5 from target list
warning: removing kded5 from target list
warning: removing sonnet5 from target list
warning: removing kservice5 from target list
warning: removing kglobalaccel5 from target list
warning: removing kpackage5 from target list
warning: removing attica5 from target list
warning: removing syndication5 from target list
warning: removing kdbusaddons5 from target list
You know I just went back through my pacman log … and it appears kwallet5 was removed along with plasma5-integration.
I am not suggesting this as your path forward (though users may consider removing the package if they wish), just recognizing the chain of events.
This also tells me that I was not having problems associated with the wallet even when kwallet5 was present.
You likely have so many being retained because of some various other packages, but plasma5-integration especially.
The command shared was chosen because it can be pointed at the group and only remove the unneeded packages … even if most were left.
These should all be ok to remove so long as you dont personally want any.
If you do … then they should be marked as explicitly installed - thus removing them from the orphans list. Example:
sudo pacman -D --asexplicit $package
A handful like v86d should definitely not be installed.
If/when you are comfortable with removing all orphans then you can run
sudo pacman -Rns $(pacman -Qdtq)
Back to the wallet … in the case its not some wonky interference by one of these orphans or similar … then we may want to go looking in HOME config/cache files. Or a quick check may be just creating a new account and signing in to that and checking kwalletmanager5 there.
I think I don’t remember explicitly installing any of this but some (like electron) seems dependencies of some AUR packages like MS TEAMS () I have to use for work.
I am going to look at them a little closer but so far I think I am going to remove them all (thanks for the commands btw! Very helpful and they are going directly to my .txt with useful commands).
Rebooted and still the same, so I am going to try this and I’ll update this post with the findings. The service is definitely working because change my pass and now is asking my old pass to decrypt the wallet on each reboot. Thanks for your time!
The orphans should, by definition, be packages that were installed as a dependency, but are not currently required by anything else.
In the case of electron … those appear to be older versions, probably as needed some time in the past, and you likely have some other electron that teams is actually depending on right now.
(You can double check with something like pacman -Qi teams or whatever is the package, and see the Depends On line.)
This definitively work. I remove all the orphans listed above (except links and cmake, which I marked as “explicitly installed”) and remove this files from .config:
Then after reboot it worked like a charm. I never imagine that this could cause this problem. Thanks @cscs for your time and your detailed response! I couldn’t have done it without you.
) I have to use for work.
