[Bug 1901724] Re: Systemd user environment generator is not executable.

[Alain Wolf]

> I thought gnome-shell started its own agent for ssh on startup?
My keys are on hardware security devices and I also use gpg-agent-forwarding, so afaik gnome-keyring-ssh will not do in this setup.

> Or did you configure your system to run the gnupg agent before starting gnome?
The way I understand it, that is exactly what user-environment-generators/90gpg-agent does.


** Description changed:

- On Ubuntu 20.04.1, with gnupg-agent 2.2.19-3ubuntu2
+ Ubuntu 20.04.1
+ gnupg-agent 2.2.19-3ubuntu2
+ gnome-shell 3.36.4-1ubuntu1~20.04.2
+ systemd 245.4-4ubuntu3.2
  
- Using the GnuPG SSH agent with interactive terminal sessions works as
- expected, after manually setting up the usual environment variables in
- ~/.profile and .bashrc.
+ 
+ Using the GnuPG SSH agent with interactive terminal sessions works as expected, after manually setting up the usual environment variables in ~/.profile and .bashrc.
  
  But Nautilus is failing to open remote SFTP directories, it ask for
  username and password, where it just should use keys from the GnuPG SSH
  agent.
  
  Only if I manually restart the gvfs-daemon.service Nautilus starts to
  work as expected.
  
  After a fresh system startup and login the main pid of the gvfs-daemon
  service will not have SSH_AUTH_SOCK variable set.
  
  After a manual service restart they are correctly set.
  
  I noticed that the file /lib/systemd/user-environment-generators/90gpg-
  agent has no execution bit set.
  
  After changing the user environment script as executable everything
  works as expected.
  
  Steps to reproduce:
  
  1. Reboot system and login.
  
  3. Get the PID of your gvfs-daemon.service:
  
-     $ systemctl --user status gvfs-daemon.service | grep "Main PID:"
+     $ systemctl --user status gvfs-daemon.service | grep "Main PID:"
  
  4. Check the environment of that process:
  
-     $ tr "\0" "\n" < /proc/$(pidof -s gvfsd)/environ
+     $ tr "\0" "\n" < /proc/$(pidof -s gvfsd)/environ
  
  Workaround:
  
  1. Make the systemd user environment generator for gpg-agent executable:
  
-     $ sudo chmod +x /lib/systemd/user-environment-generators/90gpg-agent
+     $ sudo chmod +x /lib/systemd/user-environment-generators/90gpg-agent
  
  2. Reboot system and login.
  
- 
- I also noticed while trying to find a workaround, that after simple logout and re-login of my Gnome session, it sometimes appeared to be working as expected. But then failed again after full system restart.
+ I also noticed while trying to find a workaround, that after simple
+ logout and re-login of my Gnome session, it sometimes appeared to be
+ working as expected. But then failed again after full system restart.

-- 
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/1901724

Title:
  Systemd user environment generator is not executable.

Status in gnupg2 package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1
  gnupg-agent 2.2.19-3ubuntu2
  gnome-shell 3.36.4-1ubuntu1~20.04.2
  systemd 245.4-4ubuntu3.2

  
  Using the GnuPG SSH agent with interactive terminal sessions works as expected, after manually setting up the usual environment variables in ~/.profile and .bashrc.

  But Nautilus is failing to open remote SFTP directories, it ask for
  username and password, where it just should use keys from the GnuPG
  SSH agent.

  Only if I manually restart the gvfs-daemon.service Nautilus starts to
  work as expected.

  After a fresh system startup and login the main pid of the gvfs-daemon
  service will not have SSH_AUTH_SOCK variable set.

  After a manual service restart they are correctly set.

  I noticed that the file /lib/systemd/user-environment-generators
  /90gpg-agent has no execution bit set.

  After changing the user environment script as executable everything
  works as expected.

  Steps to reproduce:

  1. Reboot system and login.

  3. Get the PID of your gvfs-daemon.service:

      $ systemctl --user status gvfs-daemon.service | grep "Main PID:"

  4. Check the environment of that process:

      $ tr "\0" "\n" < /proc/$(pidof -s gvfsd)/environ

  Workaround:

  1. Make the systemd user environment generator for gpg-agent
  executable:

      $ sudo chmod +x /lib/systemd/user-environment-generators/90gpg-
  agent

  2. Reboot system and login.

  I also noticed while trying to find a workaround, that after simple
  logout and re-login of my Gnome session, it sometimes appeared to be
  working as expected. But then failed again after full system restart.

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