Skip to content
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

Hangs forever on Generate GnuPG keypair #215

Closed
jeroenrnl opened this issue Nov 2, 2016 · 6 comments
Closed

Hangs forever on Generate GnuPG keypair #215

jeroenrnl opened this issue Nov 2, 2016 · 6 comments
Assignees

Comments

@jeroenrnl
Copy link

@jeroenrnl jeroenrnl commented Nov 2, 2016

After I have started QtPass for the first time and entered the info for the GnuPg key generation, it seems to be generating the key, but then hangs forever.
Executing ps -ef | grep gpg reveals that gpg2 is not running anymore.
The CLI simply shows the batchfile (no "Generating a default key"):

"/usr/local/sbin/pass"
"/usr/local/bin/pass"
"/usr/bin/pass"
"/usr/local/sbin/git"
"/usr/local/bin/git"
"/usr/bin/git"
"/usr/local/sbin/gpg2"
"/usr/local/bin/gpg2"
"/usr/bin/gpg2"
"/usr/local/sbin/pwgen"
"/usr/local/bin/pwgen"
"/usr/bin/pwgen"
()
"/usr/bin/gpg2,--gen-key --no-tty --batch,#           QtPass GPG key generator\n#\n#      first test version please comment\n#\n%echo Generating a default key\nKey-Type: default\nSubkey-Type: default\nName-Real: My Name\nName-Comment: QtPass\nName-Email: my@mail.nl\nExpire-Date: 0\nPassphrase: abc123\n# Do a commit here, so that we can later print \"done\" :-)\n%commit\n%echo done"

I have tried manually feeding the generated batch file to gpg2 and then it works alright, no error messages.
I have tried changing the batch file into simply "%echo working", but that doesn't change anything, also no output of the echo on the CLI (I'm not sure if that is supposed to happen)

/usr/bin/gpg2 existst and if I manually feed it a batch file, it works...

@jeroenrnl
Copy link
Author

@jeroenrnl jeroenrnl commented Nov 2, 2016

Version 1.1.5

@annejan annejan self-assigned this Nov 3, 2016
@annejan
Copy link
Member

@annejan annejan commented Nov 3, 2016

Probably related to: #202

GPG keygen needs better "error" handling . .

@annejan
Copy link
Member

@annejan annejan commented Nov 3, 2016

Could you tell me if you are on FreeBSD, Linux or macOS and which "flavour" or version @jeroenrnl ?

I have just done a quick test on macOS and FreeBSD and couldn't reproduce your issue . .

@jeroenrnl
Copy link
Author

@jeroenrnl jeroenrnl commented Nov 3, 2016

I'm using Arch Linux

@YoshiMan
Copy link

@YoshiMan YoshiMan commented Nov 16, 2016

I guess it should be solved with #216. I had the same problem. For your workaround execute mkdir ~/.password-store. This will create the default passwordstore from pass, which is later set as working directory from the gpg2 command.

@jeroenrnl
Copy link
Author

@jeroenrnl jeroenrnl commented Nov 16, 2016

Yes! That did solve it!. Thanks.

@annejan annejan closed this Nov 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants