We have seen that key generation of RSA keys sometimes hangs on Windows because the key creation process does not get the lock for pubring.kbx.
Cause seems to be that the lock is (for a yet unknown reason) not released by one of the two key listing processes which are triggered by the creation of the secret key file.
To work around this we want to suspend the file watcher which triggers the key listing until the key creation process is completely finished.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA42c1e9ad13dd Ensure that Welcome screen is hidden after key generation | |||
| rKLEOPATRA80419512bd29 Ensure that Welcome screen is hidden after key generation | |||
| rKLEOPATRA0f7328d094ca Suspend automatic key listing during key generation | |||
| rKLEOPATRA95edf3252388 Suspend automatic key listing during key generation | |||
| rW Gpg4win | |||
| rW6f34f0c84050 kleopatra: Update patch for T7827 (Add workaround for locking issue) | |||
| rW8bc80780c96c kleopatra: Add patch for T7827 (Add workaround for locking issue) | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Testing | • ikloecker | T7827 Kleopatra: Add workaround for locking issue on key generation | ||
| Testing | • gniibe | T7855 keybox/keydb locking issue in 2.6 | ||
| Testing | • gniibe | T7805 Permission denied on batch deletion of mixed (openpgp+smime) certs |
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.
Looks good to me on gpg4win-5.0.0-beta395 @ win11 (tested with/without keyboxd, 20 keygen rsa3072 each, with/without password)