-
Notifications
You must be signed in to change notification settings - Fork 6
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
doesn't work, some python error #38
Comments
I can only guess the error is here. (And not properly propagated...) |
Except that I can use gpg manually, and my other password-store tools just fine:
Yet if I restart pass-secret-service and just use it again, it fails with the same error: Better paste this time:
|
FWIW, I'm using |
But still it seems to have issues finding your keys. Is it running as the right user? |
I did track this down, I needed to correctly list my LONG format gpg-id in the .gpg-id file in the password-store. I think that's mostly got things working. |
Yeah, it's just back to doing this again, even though I haven't changed anything in my password-store setup. I have no idea what's different. Joy. |
It's probably something to do with GNUPGHOME not getting hoisted into the systemd-user environment. Restoring the .gnupg symlink to where my gnpug home actually is fixes it again. Well, other than #40 . |
I think you can insert the GNUPGHOME variable into your systemd session with |
I can't deal with python anymore so I haven't dug in. NoneType, hurray.
gopass
,prs
, etc work fine.The text was updated successfully, but these errors were encountered: