- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 8 2024
@werner Please review the changes again. I think Tobias addressed your comments.
@heirecka The changes were applied. Please close this MR. (Unfortunately, only the author can close patches.)
I guess the agent was still running when you deleted and soon re-created the ~/.gnupg directory. The agent is responsible for the private keys subdir and it did not yet noticed that its homedir (and thie subdir) vanished. Depending on your system the agent should terminate itself after some time in case the homedirectory was deleted. Thus to remove the homedir please use
Apr 7 2024
Apr 6 2024
Apr 5 2024
Oops. I closed the task accidentally.
We decided the latter is to small an issue, we'll close this ticket without opening another for the reverse case.
Tested only in VS-Desktop-3.1.92.39-Beta yet
I created a pubkey (actually a subkey) for your above test keys:
I don't see a problem here. Of course Kleopatra could run a gpgconf -K all when it really exits but I doubt that we need to do that in this special elevated case
Fixed (for GnuPG 2.4). I hope 2.2 prints the same status messages.
The General Error happens also when the PIN is blocked and no Pinentry opens.
As in this case, where the indicated "Generate New Keys" button was used on a blocked card.
This change also avoids the accessibility problem (from the report) that tool tips close automatically if one moves the mouse cursor out of the tool tip.
The following patch works.
I use this for testing: