Bug 498997

Summary: kgpg asks whether a configuration file should be created: It should already offer to specify an existing one
Product: [Applications] kgpg Reporter: postix <postix>
Component: generalAssignee: Rolf Eike Beer <kde>
Status: REPORTED ---    
Severity: wishlist Keywords: usability
Priority: NOR    
Version First Reported In: 24.12.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description postix 2025-01-22 10:40:44 UTC 
SUMMARY

If you start to use KGpg the first time, it will first ask you which Gpg executable to use.
In the second step, it will tell you that it hasn't found any config file and asks you if it should create a new one or not.

At this point I am puzzled: Why should I use either option? Why is there an option at all? This needs an explanation!



SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Comment 1 postix 2025-01-22 10:46:36 UTC 
I see in the next step, if choosing "don't create one", it asks the user to specify the path to an existing one. 
For a better UX, I think these options should be renamed or even better then additional model warning dialog be combined with the dialog to specify a config file at a certain path:

GnuPG config file hasn't been found.  [ Create a new one ] [Choose an existing one]
Comment 2 postix 2025-01-22 10:49:12 UTC 
It's also weird that when no config file exists and I choose not to create, but also don't specify any, I can still click on "continue" without any warning and get to the last page of the welcome dialog to finalize the setup.