Hello,

My understanding was that GPG backed KWallet would ask you password once at login and then password will be stored in GPG's keychain even if KWallet gets locked making it never to ask password again. I am not sure what triggers for password. It seems it is often asked by Network Manager, Chrome, etc.

IMPORTANT NOTE: the passphrase dialog only shows once. Even if the wallet is closed after initial open, subsequent opening will occur silently during the same KDE session! That’s great news for those annoyed by the kwallet password prompt in the middle of the KDE session.

http://www.rusu.info/wp/?p=248

Thanks.

Hmm. What are your settings for wallet opening/closing in System Settings > Account Details > KDE Wallet?

bcooksley wrote:Hmm. What are your settings for wallet opening/closing in System Settings > Account Details > KDE Wallet?

Default as came from Fedora group. Seems like okay because even if KWallet closes GPG Key remains open which will make KWallet open without problem.

Went ahead and created a bug report. https://bugs.kde.org/show_bug.cgi?id=336955

Try unchecking "Close when unused for" and see if that has an effect on the behaviour you are seeing.

bcooksley wrote:Try unchecking "Close when unused for" and see if that has an effect on the behaviour you are seeing.

I will do that. I am thinking that culprit might be Kgpg. Kgpg has a setting use GnuPG-agent. I thought gpg-agent was the one keeping the gpg key password cached for the session. It might be possible that kgpg closes gpg-agent session triggering pinentry-qt.

To my knowledge KGpg doesn't close the GPG agent or ask it to unload keys it has loaded. It may therefore be worthwhile to ensure that kwalletd is able to communicate with gpg-agent.

bcooksley wrote:To my knowledge KGpg doesn't close the GPG agent or ask it to unload keys it has loaded. It may therefore be worthwhile to ensure that kwalletd is able to communicate with gpg-agent.

Presence of enable gpg-agent makes me think that Kgpg is managing the keys. Does it?

The extent of KGpg's management of keys is the management you do through it's user interface. It doesn't automatically disable keys, etc. That functionality is part of gpg-agent itself if it is enabled.

bcooksley wrote:The extent of KGpg's management of keys is the management you do through it's user interface. It doesn't automatically disable keys, etc. That functionality is part of gpg-agent itself if it is enabled.

I am going to try avoiding kgpg for now so that I can learn components of gpg well and see if that works with Kwallet.