Is there a mechanism which can be used for this? Of course this could be done using the usual autostart feature, or we turn the server into a Windows service (ask @alexk). Start the client along with kleopatra?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 10 2024
Thanks for opening a bug report. This is better for our workflow.
Oct 9 2024
But the DEVINFO --watch is required to trigger this hang? Kleopatra does not use this but we see simlar hangs from time to time in the current version.
This is also relevant for VSD 3.3. Backport is not needed, but gpg4win/VSD needs to include current gpgme.
Yes, the fix is included in the Gpg4win 4.3.1.
Replacing gpgrt_spawn_actions_set_environ by gpgrt_spawn_actions_set_envchange is not good, as it's exported and already used.
Oct 8 2024
Was the fix part of a stable release? The beta was 4.2.1b55. Stable download on https://gpg4win.de/ is 4.3.1. Am I correctly assuming, that 4.3.1 includes the fix and this issue here can be closed?
This is a super old bug report, this is likely fixed with a new version of Kleopatra, so I am closing this. If this happen again in the future, feel free to reopen this bug report.
This is no longer possible. The sign/encrypt button is disabled and an info box is displayed.
No reply for a very long time, so I am closing this ticket. This is likely fixed now. Feel free to reopen if this happen again.
No reply for a very long time, let's close this.
This report is a bit old. I just tested gpg --keyserver https://keys.openpgp.org --search-keys mail@mhammerbacher.de on my laptop and this work fine.
gpg4win 4 has been released with unicode support. Closing.
I created https://invent.kde.org/pim/kleopatra/-/merge_requests/287 for the appstream file.
This is now done and it is much simpler now
Pushed the fix for exporting OpenPGP v5 key: rG57dce1ee62c2: common,gpg,scd,sm: Fix for Curve25519 OID supporting new and old.
Oct 7 2024
Backported for gpg4win 4.x
When I last talked about this ticket I had not thought of the fact that we need to have this in some kleowrap wrapper and that currently stdout and stderr are not printed in a process which forwards its call to an already running kleopatra.
I thought about this and any change here has a regression risk and the release is already overdue. If we change this now as a band aid before a release with keyboxd we really need this only for one release.
Regardless of the migration. At least we need to set GNUPGHOME early in Kleopatras main to the value returned by GpgME so that the qt.conf patch works in KF6.
Andre, didn't we conclude that there's nothing worth migrating except the groups configuration (which is migrated)?