Change Details

If the subkey for an ADSK set by `default-new-key-adsk` is not in the keyring, the key generation error in Kleopatra is generic: {F31165956} If possible, the error should include, that it's about a missing ADSK to point the user in the right direction. I once forgot to delete the gpg.conf entry and it took a while until i figured it out. As soon as ADSK is used more widely, many end users with admin provided setups might be confronted with this.

If the subkey for an ADSK set by `default-new-key-adsk` is not in the keyring, the key generation error in Kleopatra is generic: {F31165956} If possible, the error should include, that it's about a missing ADSK to point the user in the right direction. I once forgot to delete the gpg.conf entry and it took a while until i figured it out. As soon as ADSK is used more widely, many end users with admin provided setups might be confronted with this. Edit 2025-11-17: We want to solve this by adding a link (button in case of the 5.0 version) labeled "Diagnostics" to the audit log. There the user will find the ADSK mentioned.

If the subkey for an ADSK set by `default-new-key-adsk` is not in the keyring, the key generation error in Kleopatra is generic: {F31165956} If possible, the error should include, that it's about a missing ADSK to point the user in the right direction. I once forgot to delete the gpg.conf entry and it took a while until i figured it out. As soon as ADSK is used more widely, many end users with admin provided setups might be confronted with this. Edit 2025-11-17: We want to solve this by adding a link (button in case of the 5.0 version) labeled "Diagnostics" to the audit log. There the user will find the ADSK mentioned.