Your message dated Wed, 07 Oct 2015 15:53:34 +0000 with message-id <e1zjr26-00084o...@franck.debian.org> and subject line Bug#800617: fixed in gnome-keyring 3.18.0-2 has caused the Debian Bug report #800617, regarding Fails to provide secrets 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 ow...@bugs.debian.org immediately.) -- 800617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: gnome-keyring Source-Version: 3.18.0-2 We believe that the bug you reported is fixed in the latest version of gnome-keyring, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 800...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev <mity...@debian.org> (supplier of updated gnome-keyring package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 07 Oct 2015 18:38:06 +0300 Source: gnome-keyring Binary: gnome-keyring libpam-gnome-keyring Architecture: source Version: 3.18.0-2 Distribution: unstable Urgency: medium Maintainer: Josselin Mouette <j...@debian.org> Changed-By: Dmitry Shachnev <mity...@debian.org> Description: gnome-keyring - GNOME keyring services (daemon and tools) libpam-gnome-keyring - PAM module to unlock the GNOME keyring upon login Closes: 800617 Changes: gnome-keyring (3.18.0-2) unstable; urgency=medium . * Add proposed upstream patch from Jan Alexander Steffens to fix the D-Bus service activation race (hopefully closes: #800617). Checksums-Sha1: ae46a68b435126c96a41cd1c1c3d72709c8fd3b3 2564 gnome-keyring_3.18.0-2.dsc 1ecf93707907f7fa003f4abad06aa1dad00274e7 16728 gnome-keyring_3.18.0-2.debian.tar.xz Checksums-Sha256: ce074f0327a88b9eaa9c7855b84a9852d73825786b0120ccc36f17889de51936 2564 gnome-keyring_3.18.0-2.dsc c180040161bbc4cc7ee8710295c8aeaf2ce9bc8cd18d2bbc488bc60461312f8c 16728 gnome-keyring_3.18.0-2.debian.tar.xz Files: aa15dadbed79e4b28213e9929b5052f1 2564 gnome optional gnome-keyring_3.18.0-2.dsc 2e12087c8a6035b087ef9e850e14d2d9 16728 gnome optional gnome-keyring_3.18.0-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWFT2mAAoJENb+cQNj+F3T2v8P/2rtGa0knwpgJqArLZCv5PKB n0EPdXb1cF4YWl1ZMrE+BYx5Gbr62toaOzlXlKyQAk9/1AQFuYB3myrVS1/Q7P8S zsBBC1a3IRHYL72KR5l3soAx3MUpkTShVXFBBwQZizSgd/9j4CWxnCqoq66YlIDy b0QYytkmA1LWfSN3ovvnEm3RLy/6YaLUPBJ/RMh8ZrWoRxUpuslCYQ8l7I2A08dd GbwfF2QyGsSg/IlwVca9Ei+kp8FrfGCysepNQ3vIO3AIyn/5olyqODRLwAJYT7Ev AhaApwk6h8Q+QPXmfeNgp3W/948oYHozzjidJ+sakSXFYlq29P21DcKJHeJ4UCB8 jUJVX04TDAE/821YaSD5gERaEcQZNySaXyIT612vOI4CqtdInytSTW8ocuhpI2cl k2WvSC/csZA3PcKl432TFcTEshbx/XwSu+/1wmu8seuNVuMu5Tuw+vU2pmO4AHhG w23BhycWs/ksv7lOqAIOkVctgHKLBF9i16/P9WsprMNKfs9StAO6oJVMbETpzvXC LAp8leuBZiEOU9IecJLMVMxlLmredmeEXnlag4RQLgYn8WSkMemzZBqqoUIyDYrJ pQQJMwrnXXJjVnEXPMJrnVNVRKCzSu93pVEUhWDVr1iMSkIb6S32Q8qBvZwQn0AN j+7m8yvFRgQgXjBG1j4l =3y0N -----END PGP SIGNATURE-----
--- End Message ---
