I don't think the patch above works, for the reason that invoking gpg-
agent without arguments achieves the same effect as invoking gpg-
connect-agent with an empty stdin. Notice that the return code for
former is 0 if the gpg-agent could be detected and 2 if not. The issue
is that since the gpg-agent-info file is in a non-standard location, it
has to be sourced to get the GPG_AGENT_INFO variable, which the startup
script does. Unfortunately, GPG_AGENT_INFO isn't visible to the {gpg-
agent, gpg-agent-connect} test process since it's not exported. That
means the test process would give a nonzero return and cause an orphaned
gpg-agent process to be spawned. A simple fix would be to export the
GPG_AGENT_INFO variable, which is what I proposed in my bug report:
https://bugs.launchpad.net/bugs/804641.-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/743268 Title: gpg-agent not launched correctly in Xsesson scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/743268/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
