When you run KGpg, it checks for the existence of the file ~/.gnupg/gpg.conf and complains if it isn't there. If you have never used GPG, there is no .gnupg/ directory in your $HOME directory. So it's very probable that you'll suffer from this issue and have to mess with the command line before using KGpg. It may be negative for novice users. I believe that KGpg should create this file by itself, just as "gpg" does when you use it for first time and the .gnupg/ directory doesn't exist. Reproducible: Always Steps to Reproduce: 1. Backup the ~/.gnupg/ directory (if exists) and delete the original one. 2. Open KGpg. Actual Results: KGpg complains about the non-existence of the file ~/.gnupg/gpg.conf. Expected Results: I think that KGpg should trigger the creation of the necessary structure automatically, just as "gpg" does.
Created attachment 91617 [details] Window that comes up when the file ~/.gnupg/gpg.conf doesn't exist.
> When you run KGpg, it checks for the existence of the file > ~/.gnupg/gpg.conf > and complains if it isn't there. If you have never used GPG, there is > no > .gnupg/ directory in your $HOME directory. So it's very probable that > you'll > suffer from this issue and have to mess with the command line before > using > KGpg. It may be negative for novice users. The problem does not exist if the user has never run KGpg before. In that case no kgpgrc file will exist and KGpg will run it's first start wizard. The problem only exists when KGpg _has_ been run before, and the configured directory has been (re)moved. But indeed it should be more clever in that case, offering to run the wizard again or just quit to let the user fix it.
Oh, I see. I guess that's why it didn't complain in one of my tests. I deleted the file ~/.kde/share/config/kgpgrc and the directory ~/.gnupg/, and that time it worked as I expected. I also agree that adding an option to re-run the wizard would be of much help. Thank you!
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Yes, this still happens with kgpg-21.04.3 and gpg-2.2.32