can't sign commits with gpg even thou gpg-keys are unlocked with pam-gnupg

Re: can't sign commits with gpg

Reply #15 – 10 October 2021, 20:52:57

further down the rabbit hole, I'v decided to stick with

export GPG_TTY=$(tty)

in my .zshrc to keep the tty's identical, after a reboot gpg is now working, but it launches the curses interface, and pam-gnupg definitely did not unlock my keys ... I'v went to upstream and filed a bug report with all of the above going step by step and I'v found that other people who use Devuan or Gentoo have similar problems with pam-gnupg not unlocking keys ... if i try to use the pinentry-gnome3 or pinentry-dmenu or pinentry-gtk-2 i get the same errors as my original posts here

in one of the issues opened there, as i'v read trough them all, the developer suggests to use journalctl -b -g pam_gnupg to get a pam_gnupg log ... what would be the equivalent of that command on suite66?

Re: can't sign commits with gpg

Reply #16 – 11 October 2021, 20:04:16

I have reinstalled my system, with runit, and managed to get pam-gnupg working, and on runit my keys are getting unlocked on login ... althou, there is only 1 thing I did different, and it's completely unrelated to git or gpg-agent configuration, seems that pam-gnupg has some missing libraries on Artix, which i noticed when i was installing the package, I hope this is it and that installing these libraries actually made pam-gnupg work and unlock keys, I will now reinstall back to suite66 to see if the same thing will solve the issue there and get back to you ...