Summary: | import doesnt show keys | ||
---|---|---|---|
Product: | [Applications] kgpg | Reporter: | r3d <iqpg> |
Component: | general | Assignee: | Rolf Eike Beer <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | christian.nitschkowski, sven.burmeister |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
r3d
2008-07-29 12:53:13 UTC
Already reported (167652) Sorry, i reported and then i did a browser refresh and ths was submitted twice ;) *** Bug 167652 has been marked as a duplicate of this bug. *** What have you set in View -> Minimum trust? Maybe your key is simply not trusted and your filter setting hides it. Now I am able to see my private keys. As you told it was hiding by the filter. Its fixed now, so the bug sits in front of the display :p Thank you. solved *** Bug 168279 has been marked as a duplicate of this bug. *** This issue is not solved. If that filter is set by default how should a user know about it? Further, when importing keys, their trust level is set to something that is not shown by the default filter, so a user that does not know about the filters cannot change the trust-level. Setting a filter by default is a bug. I agree with comment #8. I accidentally stumbled upon this filter setting after reporting an already closed bug for this issue myself. How should a user new to kgpg know about this default filter setting? It is a nice feature for advanced users of kgpg but shouldn't be enabled by default. Please reopen this bug or open a new bug describing this issue. kgpg does not even save the state of that filter. save user-settings: 168388 turn off filters by default: bug 168389 reopend: filter settings shouldnt be enabled by default as suggested closed, because there is this bug already submitted -> https://bugs.kde.org/show_bug.cgi?id=168389 |