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

[OS X] Password input dialog suddenly stopped popping up #191

Closed
maxkrieger opened this Issue Jul 29, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@maxkrieger

maxkrieger commented Jul 29, 2016

System: OS X El Capitan v10.11.5

QtPass: 1.1.3, but was still broken in ~1.1.0 before updating

Problem: The gnupg password input dialog has stopped popping up lately, leaving qtpass grayed out. It pops up fine using pass in the cli. Here's my gpg-agent.conf:

pinentry-program /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
default-cache-ttl 600
max-cache-ttl 7200

@annejan annejan self-assigned this Aug 1, 2016

@betsythefc

This comment has been minimized.

betsythefc commented Sep 1, 2016

I am also experiencing this issue.

@annejan

This comment has been minimized.

Member

annejan commented Sep 5, 2016

I have tried multiple times to reproduce this issue . .

I have no idea how the popup can be "blocked" from a Qt process and not in the CLI . .

@thekelvinliu

This comment has been minimized.

thekelvinliu commented Oct 8, 2016

running into this issue as well. things were working fine when i was on el capitan. i updated to sierra today, and now qtpass never prompts for my key password as @maxkrieger initially described. using pass 1.6.5, gpg (GnuPG/MacGPG2) 2.0.30, and qtpass 1.1.3. i was able to reproduce this issue by running the same setup on a fresh sierra install (on virtualbox). let me know if there's any additional info i can provide to help troubleshoot.

@annejan

This comment has been minimized.

Member

annejan commented Oct 8, 2016

This might be related to the warning on https://gpgtools.org even though not directly.

Investigating..

@annejan

This comment has been minimized.

Member

annejan commented Oct 9, 2016

Could you try changing the location of the gpg executable to: /usr/local/MacGPG2/bin/gpg2
It might be that the MacOS update changed which gpg2 executable is used.

@thekelvinliu

This comment has been minimized.

thekelvinliu commented Oct 9, 2016

that was already the path of gpg2 for me :(

@maomihz

This comment has been minimized.

maomihz commented Oct 14, 2016

I experience the same issue. Then I found out that I accidentally changed the "Program" to 'pass' instead of native gpg/git. And this probably brings another issue, that is the "pass" mode does not work (probably on OSX, I don't know other platforms).

@annejan annejan closed this Jun 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment