Thanks for the feedback. I sadly forgot to include the italian translations of GpgOL in the installer. So they will only be part of the next relase.

Problem solved in Gpg4win 3.1.15 version! I think it can be closed!

That says "Interface not supported" when GpgOL is trying to obtain some data from Outlook. AFAIK this can only happen if the server is either not a Microsoft MAPI server like OpenExchange or KOPANO or so. But even these two are known to work.

Maybe it helps:
Here is another log from a user with a similar looking problem, same symptoms:

Thanks for the feedback

Ok, I found the message and tried some opening and clicking around w/o any crashes. But back then I also couldn't reproduce it. Please close the issue. I'll ask for reopening if I ever come across it once more. Thanks for your good work!

I set it to Normal priority. It would be good to find out what exactly is the problem with this key so that we can fix this in kleopatra and handle it.

The about dialog where it tells unknown windows version means it's Gpg4win-3.1.13 (the only version affected by T5056 )

It's version 2

Please let us know your gpg4win version.

Released

I am getting the initial exception again:

That would mean I could remember the exact problem. Can you extract the mail name from my logs? I should still have it...

Reopening this as I have seen such hangs multiple times during testing. When importing multiple keys with Kleopatra at once this can be reproduced sometimes.

Noteworthy changes in Version 3.1.15 (unreleased)

We are hoping to have at least a beta release soon with gcrypt 1.9 that we can put in a Gpg4win-4 beta.

This works with the message class changing. We still need to do it for OpenPGP, too.

This has been resolved with rOb05416e7bc41

This can be closed now that we have the system wide gnupg configuration.

I'm also getting this same error with GPG4Win 3.1.14.

This works now with 0c1bd9076958e584820fadf997ca7d8a248b6888 but needs more testing before this can be relased. It will probably be part of a Gpg4win-4 beta.

I'd suggest to first try the current version to see whether the bug has been solved.

I think the option you are looking for is "--homedir" with that option on the command line you can redirect where GnuPG looks for options and keys.

@glr thanks for the offer. Right now the number of support requests is low enough that we can handle them during the normal triage.

I removed gnupg from the %AppData% directory and restarted Kleopatra, but I am running into the same permissions issue.

please move away %AppData%\gnupg
it usually expands to c:\users\yourusername\AppData\Roaming\gnupg

Screenshots of the issue are attached.

GnuPG uses the systems locale.

In a discussion we decided that we need a deadline for GnuPG 2.3.0 so that we finally release it.

For support please use one of the community resources (see gpg4win.org) and read the manula (compedium) or one of the hundreds of HOWTO floating in the net.

Hartmut, please read Andre's mail again - we can't do anything about it if Outlook considers an extra delay of 20ms as too slow.

Andre,

thats wrong.
if i disable the Addin, the effect is gone.

Best regards
Hartmut

Von: aheinecke (Andre Heinecke) <noreply@dev.gnupg.org>
Gesendet: Freitag, 11. Dezember 2020 08:35
An: hartmut.jacobi@hotmail.de
Betreff: [Task] [Closed] T5176: Problem with Office 365 GnuPG Outlook addin, Outlook reports not to be primary Mail client

aheinecke closed this task as "Invalid".
aheinecke added a comment.

Hi, you can change the default mail app under systemsettings in windwos 10, this has nothing to do with GpgOL, and the delayed start report, I can't do anything about. Outlook just shows this for any COM Addin to shift the blame, seriously we took 0,02s or 20ms on your system for our initialization. That is reasonably fast.

TASK DETAIL
https://dev.gnupg.org/T5176

EMAIL PREFERENCES
https://dev.gnupg.org/settings/panel/emailpreferences/

To: aheinecke

Cc: aheinecke, gnupg, HackyJ, Neurone, ccharabaruk, gp_ast

This is an automated email from the GnuPG development hub. If you have registered in the past at https://bugs.gnupg.org/ your account was migrated automatically. You can visit https://dev.gnupg.org/ to set a new password and update your email preferences.

Hi, you can change the default mail app under systemsettings in windwos 10, this has nothing to do with GpgOL, and the delayed start report, I can't do anything about. Outlook just shows this for any COM Addin to shift the blame, seriously we took 0,02s or 20ms on your system for our initialization. That is reasonably fast.

I have reproduced the bug

A backtrace with gdb from migw-w64 results in

I did a fresh install of Gpg4win 3.1.14 and imported my standard pubkey, by using

gpg --locate-key bernhard@intevation.de

on the command line.

Sorry, I can' reproduce thus. What kind of key is causing the crash?

Thank you very much

Select your key in the certificate view, click right, select "Backup Secret keys ...", store to a file. Then copy that file in a secure why (USB stick etc) to the new box, import it there.

And I also did a backport to 2.2 :-) See rGa028f24136a062f55408a5fec84c6d31201b2143

It worked again, attaching the screenshot. Unfortunately had disabled the logging and hence no log info.

Long since resolved.

Ah no, this is about the sending part, where we only encrypt to online validated keys, that is not mitigated at all. Disregard my last comment.

This is resolved with the preview feature in GpgOL-2.4.6 Gpg4win-3.1.12

there was an issue that has been fixed in 3.1.14 which was creating problems / crashes when the home directory of a user had a unicode character in it. So maybe your one user had such a username?

On Debian, please see: /usr/share/doc/g++-mingw-w64-i686-win32/README.Debian

IIUC, the error occurred when Kleo is exiting and a destructor (in libKF5ConfigWidgets) is called with null pointer.

Version 3.1.14 released 2020-11-25
Kleopatra / GnuPG: Unicode home directories are now supported. (T5055)

Will be fixed with 3.1.14

Works, I've tested with Kleopatra.

Removing 2.2 tag because it has been fixed in one of the last releases.

3.1.12 was released on 2020-07-24.