[Bug 1675925] Re: gpg-agent service sets wrong SSH_AUTH_SOCK value

[André Colomb]

My first attempt to fix this involved trying to move gpg-agent invocation from upstart to systemd --user. I got that to work by creating:
~/.config/upstart/gpg-agent.override (manual)
~/.config/systemd/user/default.target.wants/gpg-agent.service -> /usr/lib/systemd/user/gpg-agent.service
~/.config/systemd/user/gpg-agent.service.d/override.conf ([Unit] 
Before=graphical-session-pre.target)

That correctly started the gpg-agent service, but the environment
variables were not visible within a terminal started from gnome-shell.
Somehow upstart seems to be the only way for setting env vars, the
systemd user service unit does not work as intended. Upstart needs to
die. Fast ;-)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/1675925

Title:
  gpg-agent service sets wrong SSH_AUTH_SOCK value

Status in gnupg2 package in Ubuntu:
  New

Bug description:
  After upgrading from xenial to yakkety, I noticed that my
  SSH_AUTH_SOCK environment variable pointed to $GNUPGHOME/S.gpg-
  agent.ssh, which is no longer the correct location with the current
  gnupg 2.1 package.

  After much investigation, it appears that the variable is set by
  upstart in the /usr/share/upstart/sessions/gpg-agent.conf script.
  Attached patch corrects this script to point to the new default
  location at $XDG_RUNTIME_DIR/gnupg/.

  The logic is shamelessly stolen from gnupg-agent's systemd user
  service file, /usr/lib/systemd/user/gpg-agent.service, which is
  apparently not used.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnupg-agent 2.1.15-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-41.44-lowlatency 4.8.17
  Uname: Linux 4.8.0-41-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 24 21:26:51 2017
  InstallationDate: Installed on 2012-10-22 (1613 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnupg2
  UpgradeStatus: Upgraded to yakkety on 2017-03-19 (5 days ago)
  upstart.no-pinentry-gnome3.log:
   initctl: invalid option: --no-wait
   Try `initctl --help' for more information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1675925/+subscriptions