[Solved] repeated failed attempts to gain access to a wallet

frickelhans · 2021-09-28 01:38:58

When I log out from my system I regularly get the following warning:

There have been repeated failed attempts to gain access to a wallet. An application may be misbehaving.

I am using plasma-desktop Version 5.22-1

So far i was unable to find any log to get any more information. I looked into the xorg log as well an the system journal.
I guess that the message is send by kwallet.
I can tell that the wallet is opened when I am logged in, because some of my programs use information from that wallet.

Where should I look to find more informaiton on what is going wrong? I am Happy to post logs if it helps, but i see no use in posting the full content of /var/log

Last edited by frickelhans (2021-09-28 20:50:41)

seth · 2021-09-28 06:12:13

https://forum.manjaro.org/t/kde-wallet- … llet/40571

frickelhans · 2021-09-28 11:12:46

Thanks for pointing me to this thread. Unfortunately it is not about the Problem I am having and the solution also does not work for me. I would like to clarify this a bit:

I never get asked to open my wallet. This is because it is opened on login with kwallet-pam wich was installed with plasma-desktop. The wallet is not closed until I log out, because I have owncloud-client running all the time wich stores the credentials in the wallet.
When logging in I ususally get my password right the first time, so this should also not be the problem.

seth wrote:

https://forum.manjaro.org/t/kde-wallet- … llet/40571

In kwallet Manager the setting "Promt when an application accesses a wallet" is deactivated, as proposed by an answer in the thread. Because of this I do not have to grant acess to the wallet for every program seperately.

another thing to note: the version of kwallet I have installed is 5.86.0-1

[bs]Edit:[/bs] When I log into my user account and quickly log out again I do not get the message

There have been repeated failed attempts to gain access to a wallet. An application may be misbehaving.

This leads me to the assumption that it is either time-based (probably not, but it is a possibility) or a caused by a program I use on a regular basis. I cannot believe that kwallet has no log. Where can i find it?

seth · 2021-09-28 13:33:49

kwalletd5 logs into the journal - no idea whether access rejects are logged or this is indeed the cause (the shutdown scenario sounds as if kwalletd5 terminates and something™ tries to use the wallet afterwards)
The owncloud client next to PIM/akonadi seem likely contenders, so exit them first and see whether you still get the dialog.

frickelhans · 2021-09-28 20:30:53

Thank you very much for pointing this out. I actually found some logs in the journal. Not sure why i did not find them before. As far as i can tell there is nothing too helpful there but I will still post it here just in case.

# journalctl --grep=wallet
[…]
-- Boot 677ccc78aa554ca38083ca5cef645262 --
Sep 23 10:35:54 SpinBahnKoppler sddm-helper[633]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Sep 23 10:35:54 SpinBahnKoppler sddm-helper[633]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 23 10:35:54 SpinBahnKoppler sddm-helper[633]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Sep 23 10:35:54 SpinBahnKoppler sddm-helper[646]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Sep 23 10:35:54 SpinBahnKoppler audit[633]: USER_START pid=633 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_kwallet5 acct="paul" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Sep 23 10:35:55 SpinBahnKoppler plasma_session[687]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/pam_kwallet_init.desktop" ("/usr/lib/pam_kwallet_init")
Sep 23 17:43:51 SpinBahnKoppler kded5[707]: plasma-nm: bool SecretAgent::processDeleteSecrets(SecretsRequest&) const Waiting for the wallet to open
Sep 23 18:57:01 SpinBahnKoppler dbus-daemon[657]: [session uid=1000 pid=657] Activating service name='org.kde.kwalletd5' requested by ':1.30' (uid=1000 pid=838 comm="/usr/bin/krfb -session 1014c1a51b314c0001621637983")
Sep 23 18:57:01 SpinBahnKoppler kwalletd5[4544]: kf.wallet.kwalletd: Lacking a socket, pipe: 0 env: 0
Sep 23 18:57:01 SpinBahnKoppler dbus-daemon[657]: [session uid=1000 pid=657] Successfully activated service 'org.kde.kwalletd5'
Sep 23 18:57:10 SpinBahnKoppler ksmserver[742]: org.kde.kf5.ksmserver: SmsDie timeout, client  "/usr/bin/kwalletd5" ( 1014c1a51b314c000163241622100000007420016 )
-- Boot 2798dbb7d43642a0a3b114ebd5f44594 --
[…]

This log is from the 23rd of September but they are all identical. Sometimes the message from plasma-nm is missing.

seth wrote:

The owncloud client next to PIM/akonadi seem likely contenders, so exit them first and see whether you still get the dialog.

You were right with your idea about owncloud. The message does not show up if i exit owncloud before shutting down.

Now it would be great if there was a way to automate the process of quitting owncloud before closing the wallet. I am just testing a little script to do that.

frickelhans · 2021-09-28 20:49:40

The script seems to work well. for future reference here is what I did:

I created a script to kill owncloud (see below)
I marked it as executable
Using the system settings I added it as a logout script: System Settings > startup and shutdown > autostart > add > add logout script

#! /bin/bash
killall owncloud

My problem is solved now. Thanks again to seth for helping me with this.

Arch Linux

#1 2021-09-28 01:38:58

[Solved] repeated failed attempts to gain access to a wallet

#2 2021-09-28 06:12:13

Re: [Solved] repeated failed attempts to gain access to a wallet

#3 2021-09-28 11:12:46

Re: [Solved] repeated failed attempts to gain access to a wallet

#4 2021-09-28 13:33:49

Re: [Solved] repeated failed attempts to gain access to a wallet

#5 2021-09-28 20:30:53

Re: [Solved] repeated failed attempts to gain access to a wallet

#6 2021-09-28 20:49:40

Re: [Solved] repeated failed attempts to gain access to a wallet

Board footer