Should current behavior of 'starting with no arguments' be preserved? or should we add a --generate or --doit or similar ?

A bit tricky to fix unfortunately, making the window active is not really possible on Windows. See https://doc.qt.io/qt-6/qwidget.html#activateWindow but there seems to be some tricks one can use: https://forum.qt.io/topic/1939/activatewindow-does-not-send-window-to-front/11?_=1750663659477

The question is whether any part of Qt/KF6/MTP forks another process and does not do it correctly. For example it is required that the child figures out the fds to close and then closes them and does not rely here on the parent.

For each part that needs to be reencrypted I create a QGpgME Encrypt Job

Do you start other process while this context is in use? If you do a fork, you need to make sure that all file descriptors are closed. How is that done?

Interesing part of the logs:

This is not really easy to change, since the proposed paths doesn't match QStandardPath