I have a partner that’s 73 and experiencing cognitive decline. Enough so that he keeps managing to mess up his browser. He or I have to reboot his system to get the browser to behave again, but before getting the browser to launch we have to enter his wallet password cause somehow he’s managed to cause the system to bring it up everytime the system is logged out or rebooted. I am well beyond tired of fixing it every time for him cause he can’t read a simple piece of paper with his password on it. I simply want wallet completely gone on his system so he can’t accidentally create this issue.
First, welcome to the KDE Discuss Forums.
A comprehensive help for the KDE Wallet is on the ArchWiki – here: <KDE Wallet>
The KDE documentation is OK but, the ArchWiki is more complete – <The KWallet Handbook>
The most important point is, the ArchWiki comment that, the Wallet has to be Blowfish encrypted and, that the Wallet password has to be the same as the user’s login password –
- then, and only then, the Wallet will open auto-magically when the user logs in.
Removing the KWallet package can be a bit of a pain due to dependencies –
- disabling KWallet is documented here: <Disable KWallet>
1 Like
Thank you for your reply. It’s very much appreciated, but I do have what’s most likely a niche situation.
My computer and my roommates are very close in specs cause I built both. Like me he should be able to just turn on his monitor, launch his browser and have no issue. However somehow he manages to break the browser so it’s just a white browser window making him or me have to do a restart to fix it. When the browser is launch in the fresh desktop session the Wallet password dialog box pops up. I have tried to figure out what he keeps doing since beside the specs the OS and desktop and software are almost identical. I’ll try the disabling link you included and see what milage I get. Thanks again.
You might also consider setting Kwallet to have a blank password.
Please keep up with what’s going on with Wallet cause for weeks now that’s no longer is the solution in many cases. I wasn’t even close to the first one to get forced to have to give Wallet a real password on setup instead of just leaving blank.
I’m on Fedora 42 KDE and one of the first things I do post-install is uninstall Fedora’s pre-bundled KDE/QT/GTK software that I don’t like / use. That includes kwalletmanager5 / KDE Wallet. I don’t use it because in my opinion it does nothing but get in the way and makes a nuisance of itself.
Having said that, if you need your passwords stored in encrypted wallets then you’ll want kwalletmanager.
Under Fedora you can uninstall it with sudo dnf remove kwalletmanager5. From memory I don’t think anything relies on it with my limited install. @firefox and @libreoffice being the only software groups I add. It’s possible if I installed other KDE* software groups during install and used those apps post-install, particularly @kde-pim apps (kmail, kontact, kaddressbook, et cetera), I might need kwallet or find it useful. But since I use Thunderbird and don’t install @kde-apps or @kde-pim it’s not an issue.
Unfortunately with most distros there are just enough included apps that need wallet even if one doesn’t use it so it can’t be removed. Hence why I hate meta packages. They may save the distro builder some time but end up scr_wing the end user.
I guess it boils down to whatever distro you’re using and how they packaged it. Under Fedora this is my output for the kwalletmanager5 package.
[brian@thinkpad ~]: sudo dnf repoquery --whatdepends=kwalletmanager5
Updating and loading repositories:
Repositories loaded.
[brian@thinkpad ~]: sudo dnf repoquery --whatrequires=kwalletmanager5
Updating and loading repositories:
Repositories loaded.
[brian@thinkpad ~]:
As you can see, nothing depends on it and nothing requires it.
You could of course try uninstalling it straight from the command line on your own distro and seeing what it’s threatening to pull with it. You don’t have to confirm the action if it’s pulling the table cloth out from under the rest of the DE and threatening to bring it all crashing down.
I said depending on which distro. Some have each package installed independent of other packages and some use the meta packages that were created. Meta packages that were created by at least one of the KDE devs.
BTW: I’m more than 3/4 of a century old … 
I’ve now upgraded from openSUSE Leap 15.6 to Leap 16.0 – Plasma 5 to Plasma 6 …
With respect to KWallet, the following happened during the upgrade:
- The “kf6-kwallet” and “kwalletd6” packages were installed.
- the “pam_kwallet” package was removed.
- the “pam_kwallet6-common” package was installed.
After the upgrade, I additionally installed the “pam_kwallet6” package.
The “libkwalletbackend5-5” package has remained installed on the upgraded system.
The upgrade has removed the /etc/pam.d/sddm configuration file.
At login, the KWallet “kdewallet” opens automagically – it only needs to be setup to never, ever, close again –
- until the user logs out …
I’m 61 so that holds no water with me.
Since when is ‘65 .gt. 75+’ true? 