We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug QtPass shows: /usr/local/bin/pass: line 388: gpg: command not found
To Reproduce Steps to reproduce the behavior:
Expected behavior no error
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
QtPass tries to execute:
bash /usr/local/bin/pass show some/password
but PATH injected is :
PATH=/usr/bin:/bin:/usr/sbin:/sbin
as gpg binary is in /usr/local/bin/, it is not found since pass command define it:
GPG="gpg"
since 2014
Workaround by adding PATH=/usr/local/bin/:$PATH on top of the pass command
PATH=/usr/local/bin/:$PATH
But I assume env is patched here: https://github.com/IJHack/QtPass/blob/master/src/pass.cpp#L51
but never injected within Executor instance
The text was updated successfully, but these errors were encountered:
works on current master 89e759b
Sorry, something went wrong.
No branches or pull requests
Describe the bug
QtPass shows:
/usr/local/bin/pass: line 388: gpg: command not found
To Reproduce
Steps to reproduce the behavior:
Expected behavior
no error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
QtPass tries to execute:
but PATH injected is :
as gpg binary is in /usr/local/bin/, it is not found since pass command define it:
since 2014
Workaround by adding
PATH=/usr/local/bin/:$PATH
on top of the pass commandBut I assume env is patched here:
https://github.com/IJHack/QtPass/blob/master/src/pass.cpp#L51
but never injected within Executor instance
The text was updated successfully, but these errors were encountered: