Version: unspecified (using Devel) OS: Linux Configuring signing and encryption keys or certificates in the Cryptography tab does not work. Reproducible: Always Steps to Reproduce: Prerequisite: Having an S/MIME signing certificate and/or an encryption OpenPGP key for the recipient - Launch Kmail-mobile - Open the 'Actions' tab - Click on 'Identities' - Select an identity and click on 'Modify...' button - Go to the 'Cryptography' tab - Scroll down to the line 'S/MIME signing certificate:' and click onto the corresponding 'Change...' button Actual Results: A pop up dialogue appears with the message: 'Fetching keys...' and a progress bar. Nothing more happens they keys are never found not matter how long the user waits. Expected Results: The keys should be found properly. Note: Even when the user has managed to configure its keys if she clicks on the 'Change' button the 'Fetching keys...' message appears and deletes the all the correct keys leaving all the fields empty in the cryptography tab. I am setting this bug as high priority since it prevents me to fully test the sign and encryption functionalities N900, 4:4.6~20101125.1200370-1maemo1.1200491
Seems to be triggered by a not running gpg-agent. Eg. running "gpgsm --list-secret-keys" on the console correctly auto-starts the gpg-agent, and then keylisting works correctly in kmail afterwards as well. @Marcus: gpg-agent auto-start bug in gpgme?
this is probably just the "gpg-agent crashes under system load bug". That one keylisting works in one scenario is then just random luck.
forget my last comment, that was windows ce only.
Hej, any news on this topic? Ciao, Tobias
Hi Tobias! I retested this today and I managed to configure successfully: - my OpenPGP encryption key - my S/MIME signing certificate - my S/MIME encryption certificate But unfortunately I cannot configure my OpenPGP signing key. When I click on 'Change...' button from the Edit Identity dialogue the list is empty whereas for the other keys a number is listed and can be selected. Because of this I am reopening this bug. N900, 4:4.6~.20110105.0808.gitba42ec9-1maemo1.121147
(Note: the bug is now about OpenPGP, not S/Mime anymore). gpg-agent is running. gpg says "secret key available". Signing on the command line (e.g. gpg --clearsign file) works fine. But KMail doesn't offer the key when selecting a key for signing.
Hej, what does 'gpg2 --list-secret-keys --with-colons' return on the command line? Ciao, Tobias
Hi Tobias! gpg2 --list-secret-keys --with-colons' returns nothing However gpg --list-secret-keys --with-colons returns sec::1024:17:FAD230F76BADBFA6:2009-10-25::::Sabine Faure <sabine@kdab.net>::: uid:::::::04C2FCFE444BF25A87A0400E254F30EB6BD7BB84::Sabine Faure <sabine@kdab.com>: ssb::2048:16:F9938188A67E65EC:2009-10-25::::::: sec::1024:17:87890CAB8F8F0B3A:2010-08-20::::Sabine Test <sabinetest@kdab.com>::: ssb::2048:16:1AE98C7F21022C72:2010-08-20::::::: Do you think that it is a configuration pb on my N900 then? I am reopening until you let me know. N900, 4:4.6~.20110114.0754.git620f98b-1maemo1.121392
Sabine, please try to install the gnupg2 package. It might be missing.
gnupg2 is installed, obviously, otherwise `gpg2` (as used in comment #8) wouldn't be there...
David, I wasn't sure, because it is strange that gpg gives output that gpg2 does not. I believe this is where we need to check what the issue is. Try "gpg2 -vvv --list-secret-keys" and "gpg2 -vvv --debug-all --list-secret-keys". Also check the permission on all in .gnupg, should not be root. You may ping me if we are both online for interactive debugging.