-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to generate a new keypair, GPGME error #179
Comments
Have you installed GnuPG correctly in your computer? This is crucial for GpgFrontend. |
@saturneric This Error still Occurs on Fedora, Arch and Windows. I also checked and installed GnuPG. |
What is the path where "gpg" and "gpgconf" is installed? Is it in PATH? It looks like GpgME can't find it. |
and the version of gpg should be greater than 2.1.0 |
Ok so I checked and as described in the Arch wiki gpg frontend is installed is installed via flatpak under /var/lib/flatpak/exports/bin. My Version is 2.1.4. This was tested on Arch Linux. |
Ok. Emmm... Can you try the nightly build (AppImage)? It has a new option "-e". Starting with "./GpgFrontend.AppImage -e", GpgFrontend will print all the necessary Environment Information. This will help us to discover the bug before v2.1.6. Nightly Build: https://github.com/saturneric/GpgFrontend/releases/tag/nightly |
I'm a first-time user of GpgFrontend. When attempting to create a new keypair, I received an "General Error" message that referenced GPGME, which I assume is the GnuPG Made Easy library. See screenshot.
I tried adjusting a few values on the Generate Key window, but it didn't make a difference. I looked to see if this issue was reported earlier, but I couldn't find anything.
I checked one of the logs, and I do see a line that may provide a clue:
(For reference, see the full copy of the core.log.)
FYI, I installed the previous release of GpgFrontend (2.1.3) because the newest release isn't compatible with my macOS (11.7.10, Big Sur).
The text was updated successfully, but these errors were encountered: