Closed pbx closed 3 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.95. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
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"
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.
Pass development is going on on the mailinglist https://lists.zx2c4.com/pipermail/password-store/ But indeed very slow at the moment.
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 :(
Versions:
To reproduce (on my machine at least : )
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):
This version of QtPass works without issue on my Linux box.