Like this:

@@ -1196,10 +1196,25 @@ pr_string (estream_printf_out_t outfnc, void *outfncarg,
    future, when breaking API/ABI is OK, we can change signature of
    gpgrt_string_filter_t to have another argument for precision.  */
   int allow_non_nul_string = (arg->precision >= 0);
+  char *stringbuf = NULL;

We could also pass a nul terminated copy to the filter function in pr_string.

I can test this. For Ebo I want to try using the flatpack so that she can benefit from Dans work on debian stable, too.

In D573#5989, @nicolasfella wrote:

pinentry-gtk etc presumably need similar treatment, so I'm not sure how much sense it makes to add org.gnupg.pinentry.desktop for pinentry-qt. Should this be org.gnupg.pinentry-qt.desktop instead? Or have one desktop file for all pinentries, which could be problematic for the Exec matching in KWin

I do not think this is a very common usecase. For me regarding CMS file operations it would be more important to implement T2435: gpgsm combined sign and encrypt which I find the most annyoing issue regarding CMS file encryption.

I think this is resolved now.

This is what T6799 this needs to be fixed in general.

All icons that are available in normal/light mode should now also be available in dark mode.

Thank you for the detailed report. I will look into it.

I encouraged Eva to create this ticket. While the specific case described here might be fixed in current master, the attachment handling still has issues.

The background for this is that .mime we can treat as as a custom extension for us since no one else that I know uses it but it is a registered extension.

With KMail 5.23.1 the attachment icon is shown as icon. It's also show in the header (I don't see a way to disable this).

This has most likely been fixed already with https://invent.kde.org/pim/messagelib/-/commit/70f39256784280d2034aa7bf1c4765f606c22d56. Please retest with KMail 5.23.1 or later.

pinentry-gtk etc presumably need similar treatment, so I'm not sure how much sense it makes to add org.gnupg.pinentry.desktop for pinentry-qt. Should this be org.gnupg.pinentry-qt.desktop instead? Or have one desktop file for all pinentries, which could be problematic for the Exec matching in KWin

KF6 KWindowSystem has some convenience API to deal with this: https://invent.kde.org/frameworks/kwindowsystem/-/merge_requests/136