When starting with a fresh keyring and inserting a smartcard that has a key on ldap after the import the keylistview is not refreshed and still shows the welcomewidget.
Description
Revisions and Commits
rLIBKLEO Libkleo | |||
rLIBKLEO4d7c53d59885 Fix watching for files that are removed and then re-added | |||
rLIBKLEO2fd71da00d5f Add function returning list of folders to watch for changes | |||
rLIBKLEO1dbd2b55b574 Add the secret key files to the whitelist of files to watch | |||
rKLEOPATRA Kleopatra | |||
rKLEOPATRA20177db4a448 Watch all relevant folders for changes |
Related Objects
- Mentioned In
- T6829: Kleopatra: Loop reading keys from smartcard
Event Timeline
I tried to reproduce this. Experimentally, I added P15CardWidget::searchPGPFpr() to OpenPGPKeyCardWidget, commented out the code that checks for an LDAP keyserver and called the function with a fixed fingerprint.
First experiment:
- I started Kleopatra with an OpenPGP card already inserted.
- Kleopatra did the key lookup and import, and then the welcome widget was replaced by the key list listing the imported key.
Second experiment:
- I started Kleopatra without OpenPGP card inserted.
- Kleopatra showed the welcome widget.
- I inserted an OpenPGP card, switched to the Smartcards view, and pressed F5.
- Kleopatra did the key lookup and import.
- I switched back to the Certificates view.
- Kleopatra showed the key list listing the imported key.
I don't see what should be different for a lookup via LDAP or for a P15 card instead of an OpenPGP card.
Needs more info how to reproduce.
Lets downgrade the priority and keep it open in case we get reports from customers. The other option would be to replicate this here using our AD demo network. But that is a bit time consuming.
I had a look at the file system watcher we use to react on changes in the GnuPG home directory. It doesn't watch the private keys living in private-keys-v1.d. Moreover, it does not handle the removal of files properly.
The issues mentioned in the previous comment have been fixed.
OTOH, those issues shouldn't have caused the original problem because the import from LDAP also touches the public key ring file and therefore Kleopatra should have performed a refresh. Therefore, I'm leaving this task open. Feel free to close.