Page MenuHome GnuPG

"gpg --gen-key" failed on Windows
Closed, ResolvedPublic

Description

I need to run "gpg --gen-key" on my Windows(Win_8.1_x64), but I got the following
error!

E:\code\java\spring-roo>gpg --gen-key
gpg (GnuPG) 2.1.1; Copyright (C) 2014 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Note: Use "gpg --full-gen-key" for a full featured key generation dialog.

GnuPG needs to construct a user ID to identify your key.

Real name: Donghua Liu
Email address: liudonghua123@gmail.com
You selected this USER-ID:

    "Donghua Liu <liudonghua123@gmail.com>"

Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: End of file
Key generation failed: End of file

E:\code\java\spring-roo>

And When I looked into Event Viewer, I found something maybe helpful for what's
wrong behind.

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: gpg-agent.exe
P2: 2.1.1.2240
P3: 549051a1
P4: libgcrypt-20.dll
P5: 1.6.2.45971
P6: 54905081
P7: c0000005
P8: 0002a242
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_gpg-
agent.exe_639be57faaefdf26b3ffef8eb29f977961b317b_3be5dbe9_3f196b5c

Analysis symbol:
Rechecking for solution: 0
Report Id: bc9f6fee-a0a2-11e4-829b-a0481c81842f
Report Status: 2097252
Hashed bucket:

The error log file is attached.

Details

Version
2.1.1

Event Timeline

werner lowered the priority of this task from High to Normal.Jan 21 2015, 3:28 PM

Please try 2.1.3 or the soon to be released 2.1.4

werner claimed this task.

Probably already fixed.

aheinecke added a subscriber: aheinecke.

Duplicate of T2085

Nope not fixed. But let's track this in T2085.

Forgot to resolve this as superseeded.