gnome-keyring doesn't start gnome-keyring-ssh services

Bug #1734791 reported by Tessa
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Looking at the gnome-keyring packages in 17.10, I see the following files, which should be auto-starting the gnome-keyring ssh agent service:

/usr/lib/systemd/user/gnome-keyring-ssh.service
/usr/lib/systemd/user/graphical-session-pre.target.wants/gnome-keyring-ssh.service

As well, I seem to have a file in ~/.config/autostart/gnome-keyring-ssh.desktop which should also start gnome-keyring-daemon with the --components=ssh option.

However, in my actual GNOME session on Wayland, gnome-keyring-daemon is running with the following options:

"/usr/bin/gnome-keyring-daemon --daemonize --login"

and there are no SSH-AGENT related env vars set, and common ssh commands like ssh-add do not work.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 27 16:56:40 2017
InstallationDate: Installed on 2016-07-08 (507 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to artful on 2017-10-19 (39 days ago)

Revision history for this message
Tessa (unit3) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-keyring (Ubuntu):
status: New → Confirmed
Revision history for this message
Walter (wdoekes) wrote :

I have the same problem, but with gpg-agent, which also reverse-depends on graphical-session-pre.target.

Also upgraded from 17.04 (clean install) to 17.10.

I'm not sure where when the --user graphical-session-pre.target is supposed to get started (and by whom), but it appears it never does. If I (re)start it manually, the gpg-agent does start, but then I have to log out and in again to get the SSH_AGENT and related env to work.

I tried a quick fix where I started the --user graphical-session-pre.target from a /usr/local/bin/gnome-session wrapper, but that was still too late (the envvars did not appear).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.