Bug 371115 - KWallet service unable to locate Gpg keys.
Summary: KWallet service unable to locate Gpg keys.
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kwallet
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Valentin Rusu
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-18 13:42 UTC by Karl D. Asmussen
Modified: 2018-10-27 03:32 UTC (History)
1 user (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 Karl D. Asmussen 2016-10-18 13:42:10 UTC
When I wish to utilize KWallet, it prompts me to create a new wallet. When I select the GPG option, I am told I have no keys. KGpg contradicts this statement: I have one key, ultimately trusted, en-and-decryption capable.

Reproducible: Always

Steps to Reproduce:
1. Open KWallet manager, create new wallet
2. Select GPG as encryption method

Actual Results:  
Reports that no GPG keys exist on the system (false, freshly created encryption-capable key pair exists on machine, KGpg confirms)

Expected Results:  
Creating a new wallet for storing passwords in.

Confirmation here: https://askubuntu.com/questions/763551/kwallet-gpg-kubntu
My own askubuntu question here: https://askubuntu.com/questions/838509/kwallet-not-finding-my-gpg-key
Comment 1 Valentin Rusu 2016-11-11 21:51:08 UTC
What are the "ultimate trust" key's usage flags?

You need to have the encrypting usage flag set. See this for more (for example):
http://unix.stackexchange.com/questions/31996/how-are-the-gpg-usage-flags-defined-in-the-key-details-listing
Comment 2 Andrew Crouthamel 2018-09-26 22:25:24 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 03:32:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!