VS-Desktop-3.3.90.31-Beta shows no warning any more for the export of a newly generated key.

So this means, the order in the description should be implemented, right?

Yes, by definition an immutable group doesn't allow any changes for that group. Don't mark a group as immutable if you want to allow changes.

The [KDE Action Restrictions][$i] in XDG_SYSTEM_DIRS/kleopatrarc prevents any changes within the whole group afterwards.
I guess, this is intended by defining an "immutable group", but i doubt that we want to prevent admins to change those settings?

So, regarding the minor version change: the change of order seems not critical (as there was no settings file before), but the introduction of the settings file might be.

I verified, that both in vsd 3.3.2 and vsd 3.3.3 beta90.29 the current implementation is

And we shouldn't change the precedence in a minor release, I believe.

The configuration readout order still needs to be specified/fixed.

Looks good to me on vsd-3.3.3-beta90.29 @ win11

Backported for VSD 3.4 and VSD 3.3.

I couldn't reproduce the problem because I had apparently told Kleopatra in the past "Do not ask again". :/

gpgme log for key creation and export with warning for VSD-Beta29

This is also the case in the latest VSD-Beta29

Looks good to me on gpg4win-5.0.0-beta395 @ win11 (tested with/without keyboxd, 20 keygen rsa3072 each, with/without password)

Shall we merge this with T2196 ? BTW, I have some unpushed commit and a test installer.

Here are places where I found problems.

The regression that the Welcome screen didn't go away after generating the very first key has been fixed. The fix has been backported for VSD 3.4 and VSD 3.3.

As this was finished more than a year ago, this should be included (and testable) in vsd

Fixed and backported for VSD 3.4 and VSD 3.3.

The following workflow works for Markus and me:

Will be backported after 2.2.49

FWIW: The fix rO75f46829054e is part of GpgOL since 2.6.3

Tested with VS-Desktop-3.3.90.12-Beta

Same behavior (on vsd-3.3.3-beta90.12 @ win10) for smime encrypted mails:

Looks good to me on vsd-3.3.3-beta90.12 @ win10:

what ever was fixed with the attached commit we can not test.

Tested with VS-Desktop-3.3.90.12-Beta, GpgOL 6.5 (WIN10 and WIN11)

2.2 test can be done with GnuPG-VS-Desktop-3.3.90.12-Beta-Standard.msi from Sep 17

Test with 3.3.90.12-Beta:
The test mail from before does not cause a spawn cycle and no high CPU load any more. (Tested without "show as text only", as it was not relevant before.)