Version: Platform Version 4.13.3 on a Windows 10 PRO / 64 bit machine. I am not sure exactly what is wrong here, so I just assuming it is with "kleopatra". I am using claws-mail for my MUA. When I open an email in claws-mail that has a signature, the following error message pops up at the bottom of the screen: The signature can't be checked - Unsupported protocol Next, when I attempt to open that signature file, I receive four error messages telling me that the following "dll" are missing: libkleo.dll libkcmutils.dll libassuan-0.dll libkdeui.dll These "dll"s are actually located in the "C:\Program Files (x86)\GNU\GnuPG" folder. How do I correct this problem so those ".dll"s are found. Also, is that the reason for the error message? Thanks Reproducible: Always
I think that there are two different Problems here: 1. Claws can't find gnupg (unsupported protocol). This should not happen if you use claws from http://www.claws-mail.org/win32/ afaik gnupg is bundled with this installer. Have you modified your PATH variable not to include gnupg maybe? You can test this by opening a command line (cmd.exe) and then type gpg2 --version. That should show some version information but work. If it does not then you have to add gpg2 to your path again (or reinstall gpg4win) 2. Kleopatra startup in gpg4win-2 was controlled by a small wrapper. If you try to start kleopatra without that wrapper it fails with the dll errors. Use C:\Program Files (x86)\GNU\GnuPG\kleopatra.exe instead of C:\Program Files (x86)\GNU\GnuPG\bin\kleopatra.exe Alternatively you can use the beta of gpg4win-3 from https://wiki.gnupg.org/Gpg4win/Testversions Which has an improved and more stable startup of kleopatra (no more wrapper etc.)
(In reply to Andre Heinecke from comment #1) > I think that there are two different Problems here: > 1. Claws can't find gnupg (unsupported protocol). This should not happen if > you use claws from http://www.claws-mail.org/win32/ afaik gnupg is bundled > with this installer. Have you modified your PATH variable not to include > gnupg maybe? > > You can test this by opening a command line (cmd.exe) and then type gpg2 > --version. That should show some version information but work. If it does > not then you have to add gpg2 to your path again (or reinstall gpg4win) Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. C:\Users\Gerard>gpg2 --version gpg (GnuPG) 2.0.29 (Gpg4win 2.3.0) libgcrypt 1.6.4 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: C:/Users/Gerard/AppData/Roaming/gnupg Supported algorithms: Pubkey: RSA, RSA, RSA, ELG, DSA Cipher: IDEA (S1), 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7), AES192 (S8), AES256 (S9), TWOFISH (S10), CAMELLIA128 (S11), CAMELLIA192 (S12), CAMELLIA256 (S13) Hash: MD5 (H1), SHA1 (H2), RIPEMD160 (H3), SHA256 (H8), SHA384 (H9), SHA512 (H10), SHA224 (H11) Compression: Uncompressed (Z0), ZIP (Z1), ZLIB (Z2), BZIP2 (Z3) C:\Users\Gerard> > 2. Kleopatra startup in gpg4win-2 was controlled by a small wrapper. If you > try to start kleopatra without that wrapper it fails with the dll errors. > Use C:\Program Files (x86)\GNU\GnuPG\kleopatra.exe instead of C:\Program > Files (x86)\GNU\GnuPG\bin\kleopatra.exe I am not sure what this is set to or how to change it in "claws-mail". I will investigate further. > Alternatively you can use the beta of gpg4win-3 from > https://wiki.gnupg.org/Gpg4win/Testversions > Which has an improved and more stable startup of kleopatra (no more wrapper > etc.)
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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!
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!