2.2.44 seems to be released. Is it correct that this issue shows as "open"?

We discussed a different file format for group definitions. It's based on gpg's --with-colons format.

current plan after discussion today is as follows:

Should also work in VSD 3.3

Should work (if correct path is set in qt.conf).

Okay. Let us split it into different tarballs and repos. We will bump the gpgme core version to 2.0 to indicate this split despite that there will be non-ABI/API incompatibility. C++, Qt, Python will then go into separate projects. The old common List stuff will be kept in gpgme core for now. The gpgme core sticks with autoconf stuff but for C++ and Qt cmake style will be used instead.

The Down button should be disabled if no suitable certificates are selected. That may not be the case (in Qt 5) because Qt seems to add disabled rows to the selection and the work around is applied when the Down button is pressed.

In T7019#190282, @aheinecke wrote:

I would vote anyway for hiding the smartcard tab if it has no information, just so that we are not confusing, I can otherwise imagine support questions like: "It says something about smartcards, do I need such a smart card?" As smartcards for crypto is not something generally known by users, i assume.

Just thinking about this, we have at least one customer configuration that uses KXMLGui to hide all smartcard actions and the view. And one other that disables certify actions everywhere. We need to check that this still works with the new details view.

Without administrator rights it does not work for me, since it then cannot write to %PROGRAMDATA% to install the VS-NfD mode config files. But the only thing for "does not work anyway" that I know and could quickly see is that "IPC connect call failed" problem with GPGEX (which we are planning to remove / replace anyway). So I don't think it is very important to remove this and addtionally we do not know if this is something that is used, we have offered it from the beginning but have no data if our customers use it. We can suspect that we would have seen more support questions about the gpgex error if it was widely used. But I always thought that the "only for me" installation option was useful for some use cases.

I think the executables also use the same values for translation.

I would say this could be treated as a duplicate or subtask of T7147: Kleopatra: Add debug information / Log handling KWatchGnuPG is in my opinion not very useful, since as a developer debugging things the command line and "watchgnupg" without the K are more then enough, KWatchGnuPG is basically just a qprocess output viewer of watchgnupg. IMO it would be similar if we would just execute CMD or Konsole with "watchgnupg" and show that window. Logging to a socket has the advantage that the entries are displayed in the order they come in while with files there is an issue of io synchronization and not all components can log in the same file. But you could use same QProcess / watchgnupg to "sync" the log entires and then write them to a file.

works in VS-Desktop-3.2.93.33-Beta

I wouldn't hide the table. We don't hide any tables (e.g. also in smart card view) if they are empty. I would resize ones on very first show (if restoreColumnLayout() returns false). This fixes the initially cut column titles. And then I'd resize to content when the search results are shown, but also only the very first time (i.e. we'd need to remember the first show).

Okay, I see now that this is US-English and Unicode.

Okay. let me do that for the next library releases.

Thanks.

afaik "Valid Until" is actually available for keys coming from WKD

• The status column is already removed in the gpg4win branch but not yet in the test version
• afaik "Valid Until" is actually available for keys coming from WKD
• For the column widths, we could hide the table until the initial search results come in and then resize to content, or just always resize to content when results come in

The whole problem that we now had to take care of marking mails as Read was a misunderstanding of the code. As I assumed since we saved the mail. The property change of "UnRead" would then not be synced to the server, but more testing and user feedback after the last release has shown that the even FC99 which we observed in the "Uncancellable write event" cases was sent to us in conjunction with the property change of UnRead.