FWIW, the assumption that calling gpg-agent without arguments will not
create another gpg-agent instance does seem to hold true for lucid for
me. Maybe this changed in 10.10?
$ pidof gpg-agent
1821
$ gpg-agent
gpg-agent: gpg-agent running and available
$ pidof gpg-agent
1821
--
You received
** Changed in: gnupg2 (Ubuntu)
Importance: Undecided => Medium
--
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 notificat
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-ag
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg2 (Ubuntu)
Status: New => Confirmed
--
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-
** Tags added: patch
--
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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
** Patch added: "This is the patch. It changes the script from running
gpg-agent to running gpg-connect-agent."
https://bugs.launchpad.net/bugs/743268/+attachment/1943742/+files/90gpg-agent.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
