Was reported to me for Windows but I can also reproduce it with latest GPA on GNU/Linux:
Trying to create a new key fails with "gpagenkeysimpleop:c:159 Invalid Argument." On Linux it also segfaults right after that.
Description
Description
Details
Details
- Version
- master
Revisions and Commits
Revisions and Commits
| rM GPGME | |||
| rM78f6291a3bf5 core: Fix ERR_INV_ARG check in genkey_start | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | • werner | T4265 GPA: Can't create new keys with GPGME 1.12.x | ||
| Resolved | • aheinecke | T4264 Gpg4win 3.1.6 | ||
| Resolved | • werner | T4289 GnuPG 2.1.12 release |
Event Timeline
Comment Actions
Gets reported multiple times and should be fixed for the next Gpg4win release as it is a bad first impression. (Although it can convert users to Kleopatra ;-) )
Comment Actions
Can you give me a reproducer on Linux. I am not able to reproduce it. What versions of gnupg and gpgme are you using (see gpa's about)
Comment Actions
GPA 0.11.0-beta5 [70858dc]
Just by going through the standard "new key wizard".
GPA 0.11.0-beta5 [70858dc]
(GPGME 1.12.1-beta68)
(GnuPG 2.2.12-beta19)
Comment Actions
Sorry, I am still not able to replicate it:
gpa 0.11.0-beta1
gpgme 1.12.1-beta12
gnupg 2.2.12-beta15
The beta numbers might not be correct; I actually use the latest versions of gpa and gnupg; let me check gpgme.
Comment Actions
I ran it with GPGME_DEBUG and it errors out at
GPGME 2018-12-07 10:34:32 <0x19c43> gpgme_op_genkey_start:293: error: Invalid argument <GPGME>
The check in 174af15725d4989a840ff3098996cc8a0568f724 should have been "if (!ctx || !parms)".
Kleo is not affected as it does not use the async functions.
I'll fix it.
Comment Actions
Should we close this or do you want to investigate why the segfault happened after the error?
Comment Actions
Regession due to my commit 10 days after the last release. Thus no need to do a release.