Bug 427160 - kgpg doesn't work if ~/.gnupg/gpg.conf doesn't exist
Summary: kgpg doesn't work if ~/.gnupg/gpg.conf doesn't exist
Status: REPORTED
Alias: None
Product: kgpg
Classification: Applications
Component: general (show other bugs)
Version: 20.08
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Rolf Eike Beer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-30 15:04 UTC by Bernhard Rosenkränzer
Modified: 2020-09-30 15:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Rosenkränzer 2020-09-30 15:04:56 UTC 
SUMMARY
If there is no ~/.gnupg/gpg.conf file, kgpg doesn't work, and often simply fails quietly without giving any indication of what's wrong (try e.g. searching for a key on a keyserver).

Even an empty ~/.gnupg/gpg.conf "fixes" this.

Since a ~/.gnupg/gpg.conf file is no longer required for the command line gpg tools, kgpg should work without it (or at least automatically create an empty gpg.conf on first startup).

STEPS TO REPRODUCE
1. Create a fresh user
2. If something (e.g. entry in /etc/skel) generated a .gnupg/gpg.conf, delete it
3. Use gpg on the command line to verify it works and doesn't scream about it
4. Open kgpg, go to the keyserver dialog, and search for something 

OBSERVED RESULT
Fails quietly, simply no matching search results

EXPECTED RESULT
Proper search results, or at least an error message indicating why it didn't work

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenMandriva Cooker
(available in About System)
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
gpg 2.2.23