Your message dated Mon, 12 Oct 2015 11:05:00 +0000 with message-id <e1zlaua-0004cx...@franck.debian.org> and subject line Bug#800617: fixed in gnome-keyring 3.18.0-3 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-3 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: Mon, 12 Oct 2015 13:45:21 +0300 Source: gnome-keyring Binary: gnome-keyring libpam-gnome-keyring Architecture: source Version: 3.18.0-3 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-3) unstable; urgency=medium . [ Michael Biebl ] * Use https:// for Vcs-Browser. . [ Dmitry Shachnev ] * Add another proposed upstream patch from Cosimo Cecchi to make sure fork is done before attempting to use D-Bus connections (fork_before_using_dbus.patch; closes: #800617). Checksums-Sha1: ae849d70fd8d9f3ef3bea9ef72908c00b19e817c 2565 gnome-keyring_3.18.0-3.dsc eef28fca62478dda072a8ac9811b501cd7561976 17796 gnome-keyring_3.18.0-3.debian.tar.xz Checksums-Sha256: cffd47c65ab78c8a4d862ffc8dd33018e832aef32b52bd1de2619325a0b4d303 2565 gnome-keyring_3.18.0-3.dsc 82942996d38cdbb237aa4dd0dfc82ed317a7abc40b8e62021bde7aae09eb6c49 17796 gnome-keyring_3.18.0-3.debian.tar.xz Files: 8b9ee4711380221322010196f905e25c 2565 gnome optional gnome-keyring_3.18.0-3.dsc d64888bb74ef210302201160f2b351cc 17796 gnome optional gnome-keyring_3.18.0-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWG5B9AAoJENb+cQNj+F3TO8sP/1AIgGYJbW+0rCY7mdd6wYY8 kg55jqagoH8HRwA2gzXh48XZPOkWpXZ3irOZ22YXqCNQhELyTcg0jgr4ODLd3+hw 1joQkR+BYZkJ/Znknrsuir1Pf3wwhOBxW+19/SJMPTIEmR1LzLLFNeoPlaSZbmiG 96YanrzxKs4iMSdMFESPkIhV5Rbp3C6XYE7XVXVIpSgzjaWqYvuyQD9sLo0+QEj3 PSVS6kS51SaigIVe4ggjyLU+XTxMTB00wsvFE0XFw/LKYWKIwDMEXHFCAAXZ9ZLA k19+1eOd3yIdK6E9tYZ6oWun3QICUksis3WF2MiqFXB48fcErqpczMJsD73tHuDF sTftEmsufIGca+9kCjiV+AWngI1bdGpr0vvs+PGBmBMT8U+iFQpZyZH8HAcfJHz6 3yWrdLxVhcPtOkEJNUfOSZKjdRhH8knWHkxrJTG/ZpteLV2wgz+I5JKv+OoMoR+Y 5NhK9L+2YbRVeR4pI+l26BYMsz/GrYLZpavISJ4txwDe9PZZgXXZ14i5GFNWSIba 0ikklg6oQjtzVcQNYyMrNTW07EXORYMpdM0S+lTpjLzcbmys6QVUsjQdHVf2o4tN fYp8zLnGqvBSykazZHHWosaepLrm9OEBPi26fAgzZ/oh2vmxNVCCZBDspbDlacKG PvAzUjwzWTGphR56mYga =5C8l -----END PGP SIGNATURE-----
--- End Message ---
