Behavior is the same as 3.0.3 /3.1.0beta32.
It reads encrypted e-mails if Titus plugin is disables (GpgOL as the only plugin).
Strange: Both beta32 and beta38 show the recipients box after pressing the send button, but
the messages are sent unencrypted. After downgrading to 3.0.3 messages are sent encryted,
again.

Hi Werner. Did you by any chance already find the time to look into the changes?

Could you please test again with the beta38 (or later) from https://www.gpg4win.org/version3.1-de.html It contains the change now.

I'm closing this as I've got confirmation that one crash was fixed by disabling async encryption again. And a class of general "Crash when encrypting" bugs that were related to the communication between Kleopatra and GpgOL no longer exists as Kleopatra is no longer used when encrypting from GpgOL in gpg4win 3.1.0.

Thanks for your report. This has been fixed for the next version ( https://bugs.kde.org/show_bug.cgi?id=391222 )

2.2.6 will have this feature in --card-edit, as kdf-setup. Please test.

close my account

Thanks for testing and the confirmation / praise ;-)

Hi Andre,
AWESOME! Thanks a lot. It works and it’s also faster. GREAT!!!
Jacques

From: aheinecke (Andre Heinecke) [mailto:noreply@dev.gnupg.org]
Sent: March 21, 2018 2:41 AM
To: Jacques Latour <Jacques.Latour@cira.ca>
Subject: [Task] [Changed Status] T3847: Pinentry-qt pop up not appearing when I send a signed/encrypted email

aheinecke changed the task status from "Open" to "Testing".
aheinecke triaged this task as "Normal" priority.
aheinecke added projects: gpgol, gpg4win.
aheinecke added a comment.

Hi,

I'm not 100% certain but I think that it is likely that your problem is fixed with the upcoming 3.1 version. We have reworked how GpgOL encrypts there a bit ( T3509https://dev.gnupg.org/T3509 )

Could you please try out the beta of the upcoming version https://www.gpg4win.org/version3.1.html and confirm that the problem is either still there or gone?

Thanks!

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

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

To: aheinecke

Cc: aheinecke, latour_jacques, Mak, 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.

The second user ID in my test case was an "URL". So we now use what ever the "raw" user id data is as the Name if both name and email are empty.

I don't find an easy way to fix this.

I just tested changing passphrases and indeed this is very ugly. Especially as this opens up a wide range of error states where you have different passphrases for different subkeys etc.