Bug 366040 - libkf5wallet5: timeout when using GPG and gpg-agent
Summary: libkf5wallet5: timeout when using GPG and gpg-agent
Status: CONFIRMED
Alias: None
Product: frameworks-kwallet
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.23.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Valentin Rusu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-24 15:28 UTC by Lisandro Damián Nicanor Pérez Meyer
Modified: 2017-04-07 17:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lisandro Damián Nicanor Pérez Meyer 2016-07-24 15:28:52 UTC
From the original bug report at http://bugs.debian.org/832289

I use the KDE 5 wallet with GPG encryption, and I use gpg-agent.

When an application wants to open the wallet, kwallet triggers gpg-agent, which in turn uses pinentry to ask for the private key's passphrase.

After some time, applications seem to run into a timeout waiting fo rthe wallet to be opened and start asking for passwords.

If I enter the ocrrect passphrase immediately, everything works, but missing the prompt for half a minute or mistyping the passphrase and having to retype it triggers this issue (and yes, this sometimes
prevents me from opening the wallet in time after some glasses of beer…).

Reproducible: Always

Steps to Reproduce:
1. Log in
2. Wait some time before filling out the GPG passphrase
3. Applications time out and start asking for passwords.
Comment 1 Rewarp 2016-08-09 01:12:06 UTC
I would like to add, that my gpg-protected kwallet does not provide ample time to type in my passphrase before proceeding with authentication procedures after logging in. This causes two major issues which are:

1. Connection to an encrypted WiFI network fails as the saved password is not provided because kwallet has yet to be unlocked immediately after logging in. I have to manually cancel the password dialogue box after unlocking kwallet before attempting to connect.

2. Failure to connect to the WiFi network always results in KMail failing to connect to my email servers, whose status will remain unchanged unless I manually restart the connection to my email servers.

I am running kwallet 5.24 on opensuse Tumbleweed.
Comment 2 Rolf Eike Beer 2017-04-07 17:25:32 UTC
Same on 5.30. Even worse: after e.g. suspend the password must be typed in again (or copied from kwalletmanager5) as there seems tobe no try to reconnect to wallet (which could be a NM problem, but I had similar issues with KMail in KDE4 days).