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

QtPass 1.3.2 freezes on macOS 10.15.6 when trying to display password #544

Closed
pbx opened this issue Sep 14, 2020 · 5 comments
Closed

QtPass 1.3.2 freezes on macOS 10.15.6 when trying to display password #544

pbx opened this issue Sep 14, 2020 · 5 comments

Comments

@pbx
Copy link

pbx commented Sep 14, 2020

Versions:

  • QtPass 1.3.2 (installed via dmg)
  • macOS 10.15.6
  • pass 1.7.3 (existing install, working fine in Terminal)
  • pinentry-mac 0.9.4 (existing install, working fine)
  • gpg (GnuPG) 2.2.21
  • git 2.24.3

To reproduce (on my machine at least : )

  1. Launch QtPass
  2. Under Configuration > Programs, choose "Use pass"
  3. Close configuration window
  4. Select an entry for display
  5. QtPass interface become non-responsive

Note: these steps result in a bash process running in the background taking a full core (i.e. 99.x% CPU)

Appearance of window in non-responsive state (entry name is displayed, but not content):

image

This version of QtPass works without issue on my Linux box.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the bug label Sep 14, 2020
@kenji21
Copy link
Contributor

kenji21 commented Sep 14, 2020

It's an issue with pass, you can reproduce it with:

export PATH=/usr/bin:/bin:/usr/sbin:/sbin
/usr/local/bin/pass ls
/usr/local/bin/pass: line 350: /usr/local/bin/getopt: No such file or directory
# 100 % cpu
Killed: 9

To fix it (a fix has been posted on pass mailing list, but not yet merged it seems)

-GETOPT="$(brew --prefix gnu-getopt 2>/dev/null || { which port &>/dev/null && echo /opt/local; } || echo /usr/local)/bin/getopt"
+GETOPT="$({ test -x /usr/local/opt/gnu-getopt/bin/getopt && echo /usr/local/opt/gnu-getopt; } || brew --prefix gnu-getopt 2>/dev/null || { which port &>/dev/null && echo /opt/local; } || echo /usr/local)/bin/getopt"

@pbx
Copy link
Author

pbx commented Nov 30, 2020

Thanks for the fix - that got around the problem for me. Unfortunately, to judge by the pass git repo at least, it looks like there hasn't been significant pass development activity in a couple years.

@annejan
Copy link
Member

annejan commented Dec 8, 2020

Pass development is going on on the mailinglist https://lists.zx2c4.com/pipermail/password-store/
But indeed very slow at the moment.

@annejan annejan closed this as completed Dec 8, 2020
@annejan annejan added bug in pass and removed bug labels Dec 8, 2020
@ChauhanT
Copy link

ChauhanT commented Dec 4, 2022

Hi, I'm facing this on macos Ventura. Where do I have to make the suggested change? In my .zshrc ? QtPass seems to work with the option Native git/gpg but not with Use pass. However, with Native git/gpg I can't actually modify or store new passwords. In any case, I don't understand the difference between the two options. Any help would be awesome. I don't want to stop using pass :(

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

No branches or pull requests

4 participants