This has popped up twice over the past few days…
No idea why this started. I’ve never used or opened kwallet / KDE Wallet Service.
Any ideas on why this is happening?
So, you don’t use wireless connection in KDE? (it uses the kde wallet)
I think a fair amount of things do use it behind the scenes.
1 Like
Nope. This install of EndeavourOS on my PC is Ethernet. I’ve never even logged in to my WIFI on this install.
Sorry, I don’t actually know details of where kde logs this…though you might check the journal (50% chance it logs to the system log?) and see if you can figure it out.
1 Like
Related to the suggestion by @dbarronoss, perhaps something like htop will reveal ”who owns” the KDE wallet process, and work backwards from there?
1 Like
I found this in a thread on the Arch forums from a few years ago.
❯ journalctl --grep=wallet
Jan 01 21:31:13 eos sddm-helper[31997]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 01 21:31:16 eos systemd[726]: Started Unlock kwallet from pam credentials.
-- Boot 641011ff8eaa4396ab41bd53adeca7bc --
Jan 02 08:28:40 eos sddm-helper[757]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 02 08:28:47 eos systemd[744]: Started Unlock kwallet from pam credentials.
-- Boot 0916eea68981414ba93b825b9a1013e0 --
Jan 05 17:33:09 eos sddm-helper[734]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 05 17:33:13 eos systemd[719]: Started Unlock kwallet from pam credentials.
-- Boot a00e54fa57af4ff99444381721cd53e8 --
Jan 05 17:35:57 eos sddm-helper[759]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 05 17:36:01 eos systemd[744]: Started Unlock kwallet from pam credentials.
-- Boot 91f962aed036400ab98f09da0011b6b7 --
Jan 05 17:50:39 eos sddm-helper[739]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 05 17:50:42 eos systemd[723]: Started Unlock kwallet from pam credentials.
-- Boot bb9961936699491aa1aee345fd3f6b97 --
Jan 05 17:52:03 eos sddm-helper[738]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 05 17:52:07 eos systemd[723]: Started Unlock kwallet from pam credentials.
-- Boot 1d6024093a4d4e829517d8bf34d86158 --
Jan 05 17:54:20 eos sddm-helper[746]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 05 17:54:24 eos systemd[731]: Started Unlock kwallet from pam credentials.
-- Boot 6263da00d3e54cdd8add0a258dd777b4 --
Jan 05 19:38:26 eos sddm-helper[730]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 05 19:38:30 eos systemd[715]: Started Unlock kwallet from pam credentials.
-- Boot 0c5cfa3dacae45faa9460eafbee7b0ee --
Jan 07 08:36:37 eos sddm-helper[752]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 07 08:36:41 eos systemd[737]: Started Unlock kwallet from pam credentials.
-- Boot 792c4877b8914c408698e117d5c581ae --
Jan 08 08:49:04 eos sddm-helper[745]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 08 08:49:07 eos systemd[730]: Started Unlock kwallet from pam credentials.
-- Boot 36f8cd222ba748298ff727094bcec9bb --
Jan 09 13:07:10 eos sddm-helper[742]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 09 13:07:14 eos systemd[727]: Started Unlock kwallet from pam credentials.
Jan 10 08:24:04 eos sddm-helper[28588]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 10 08:24:07 eos systemd[28572]: Started Unlock kwallet from pam credentials.
-- Boot f379ac85532d44a3b8c76033eef5c1d9 --
Jan 10 09:23:47 eos sddm-helper[756]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 10 09:23:51 eos systemd[743]: Started Unlock kwallet from pam credentials.
-- Boot 82ad47ff3c0842839fe14360cca9904b --
Jan 12 04:41:27 eos sddm-helper[728]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Jan 12 04:41:27 eos sddm-helper[728]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jan 12 04:41:27 eos sddm-helper[728]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Jan 12 04:41:27 eos sddm-helper[747]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jan 12 04:41:31 eos systemd[734]: Started Unlock kwallet from pam credentials.
-- Boot f79aee35124346c4b3888afd9570d2d6 --
lines 2-44
Did you change your password before this started happening?
Did you upgrade to the beta testing release?
https://wiki.archlinux.org/title/KDE_Wallet
Nope.
Nope.
If you turn on KWalletManager > Settings > Configure Wallet > Access Control >
Prompt when an application accesses a wallet, you may see what it causing it.
1 Like
Perhaps section 2.1.1 in the above might shed some light on where/when the ”wallet” is getting called, based on your display manager? 
But kwalletmanager is not installed, and if it is it should show up in the system settings.
1 Like
I had to install Kwallet Manager…
KWalletManager > Settings > Configure Wallet > Access Control > Prompt is empty
Does this do the same behavior in your other account?
this picture shows that you have it running.
When that suggestion was posted, I had to go see if I had it installed (yep, though I obviously didn’t ever pay it any attention) 
Now if I can just retain the information.
Enable it and you should see what is accessing the wallet
Yeah, it will show a popup when an application wants to access the wallet.