Your message dated Fri, 2 Nov 2018 09:10:47 +0000
with message-id <[email protected]>
and subject line Re: Bug#854318: gnome-keyring: Attempts to provide ssh-agent
has caused the Debian Bug report #854318,
regarding gnome-keyring: Attempts to provide ssh-agent
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
854318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854318
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.20.0-3
Severity: important
A recent upgrade to gnome-keyring appears to have resulted in it once
again trying to provide a SSH agent. Since I use a gnupg smartcard to
store my authentication keys for SSH (which is supported by GnuPG but
not by gnome-keyring) this breaks my ability to SSH into most remote
systems, including things like preventing me from doing anything on
kernel.org.
I have previously removed /etc/xdg/autostart/gnome-keyring-ssh.desktop
(which is still removed) but it appears that this is now triggred by
systemd somehow.
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-keyring depends on:
ii dbus-user-session [default-dbus-session-bus] 1.10.14-1
ii dbus-x11 [dbus-session-bus] 1.10.14-1
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2
ii gcr 3.20.0-3
ii libc6 2.24-9
ii libcap-ng0 0.7.7-3
ii libcap2-bin 1:2.25-1
ii libgck-1-0 3.20.0-3
ii libgcr-base-3-1 3.20.0-3
ii libgcrypt20 1.7.6-1
ii libglib2.0-0 2.50.2-2
ii p11-kit 0.23.3-5
ii pinentry-gnome3 1.0.0-1
Versions of packages gnome-keyring recommends:
ii libpam-gnome-keyring 3.20.0-3
gnome-keyring suggests no packages.
-- Configuration Files:
/etc/xdg/autostart/gnome-keyring-ssh.desktop [Errno 2] No such file or
directory: '/etc/xdg/autostart/gnome-keyring-ssh.desktop'
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.25.90-1
On Mon, 08 May 2017 at 23:28:20 +0100, Tim Retout wrote:
> Having disabled the desktop files as you describe, when I choose the
> "GNOME on Wayland" option from gdm, I see
> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh . With just "GNOME", I get
> /run/user/1000/gnupg/S.gpg-agent.ssh
>
> This appears to be connected to this code in gnome-session:
>
> http://sources.debian.net/src/gnome-session/3.22.3-1/gnome-session/main.c/#L415
That code was removed in upstream version 3.25.3, so this bug should no
longer exist in buster.
smcv
--- End Message ---
