Package: gnome-keyring Version: 3.18.0-1 Severity: grave Since upgrading gnome-keyring from 3.16.0-4 to 3.18.0-1, applications trying to retrieve secrets from gnome-keyring no longer can. I see log messages like the following:
Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5801]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory [...] Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't register in session: Timeout was reached Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't communicate with already running daemon: Timeout was reached Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't communicate with already running daemon: Timeout was reached Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Oct 01 10:36:39 jtriplet-mobl1 gnome-keyring-daemon[5844]: couldn't register in session: Timeout was reached [...] Oct 01 10:37:03 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't request name 'org.freedesktop.secrets' on session bus: Timeout was reached [...] Oct 01 10:48:34 jtriplet-mobl1 org.gnome.evolution.dataserver.Sources4[5783]: server_side_source_credentials_lookup_cb: Failed to lookup password: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached Oct 01 10:48:35 jtriplet-mobl1 org.gnome.seahorse.Application[5783]: (seahorse:8293): seahorse-WARNING **: gkr-backend.vala:85: couldn't connect to secret service: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached In addition to that, it also looks like every time an application tries to access the org.freedesktop.secrets service, dbus spawns an instance of gnome-keyring with the --foreground option, likely based on /usr/share/dbus-1/services/org.freedesktop.secrets.service ; does this conflict with the instance already run via /etc/xdg/autostart? - Josh Triplett -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.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-x11 1.10.0-3 ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii gcr 3.16.0-1 ii libc6 2.19-22 ii libcap-ng0 0.7.7-1 ii libcap2-bin 1:2.24-11 ii libgck-1-0 3.16.0-1 ii libgcr-base-3-1 3.16.0-1 ii libgcrypt20 1.6.3-2 ii libglib2.0-0 2.46.0-2 ii p11-kit 0.23.1-3 ii pinentry-gnome3 0.9.5-4 Versions of packages gnome-keyring recommends: ii libpam-gnome-keyring 3.18.0-1 gnome-keyring suggests no packages. -- no debconf information
