Ok that fixed it. The issue was this one line. Thanks for showing me your example. Shepherd's logs showed gpg-agent launching fine. I just had the incorrect file-append incantation. Presumably pinentry is a symbol inside of the home-environment.services.service context.
;; incorrect (pinentry-program (file-append pinentry-curses "/bin/pinentry-curses")) ;; correct (pinentry-program (file-append *pinentry* "/bin/pinentry-gtk-2")) Many thanks 👏🏿 I would have been stuck on that for a while. Tim On Wed, 15 Jan 2025 at 10:41, Richard Sent <[email protected]> wrote: > > *Troubleshooting* > > > > I've tried all the commands I can think of to launch the gpg agent. It's > > just not happening. > > > > guix home reconfigure home-config.scm > > gpg --list-keys > > gpgconf --kill gpg-agent > > > > herd status shows that the gpg-agent service has started. > > > > herd status > > Started: > > + gpg-agent > > + root > > > > > > But ps aux | grep gpg doesn't show anything. > > And gpg key generation can't connect to the pinentry daemon. Trying to > > generate a keypair gives me this error... What am I missing in this > > setup? > > It's been a while since I set up gpg-agent. Home shepherd places logs in > $HOME/.local/state/log/shepherd.log, perhaps you'll find some useful > information there. > > If it's any help here's my configuration with a working gpg-agent used > for both ssh and gnupg. > > https://git.sr.ht/~freakingpenguin/rsent/tree/master/item/rsent/home/base.scm#L52 > > -- > Take it easy, > Richard Sent > Making my computer weirder one commit at a time. >
