Your message dated Sun, 18 Oct 2015 15:50:05 +0000 with message-id <e1znqdl-0005hu...@franck.debian.org> and subject line Bug#800617: fixed in gnome-keyring 3.18.1-1 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.1-1 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: Sun, 18 Oct 2015 17:30:21 +0300 Source: gnome-keyring Binary: gnome-keyring libpam-gnome-keyring Architecture: source Version: 3.18.1-1 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 800660 Changes: gnome-keyring (3.18.1-1) unstable; urgency=medium . * New upstream release. - Now the problems with forking should be really fixed (closes: #800617, the third attempt). * Drop fix_tests_for_new_glib.patch, applied upstream. * Drop init_secret_service.patch, applied upstream. * Drop fork_before_using_dbus.patch, the issue has been fixed properly. * Backport two post-release upstream commits to properly unexport secret prompt objects (fix_object_path_regression.patch; closes: #800660). Checksums-Sha1: ff8cca9e8ed18ba18c1dd038468907884e57f0b8 2526 gnome-keyring_3.18.1-1.dsc 36b4001d90c8916d74896f22d13a5af58426dbf8 1204228 gnome-keyring_3.18.1.orig.tar.xz e353ae34f32869442424951b9fefa40c4f8558d5 16348 gnome-keyring_3.18.1-1.debian.tar.xz Checksums-Sha256: 3070e55f28b2e791c619e6eba98a820d71fef59765daffd05310ff4c84776909 2526 gnome-keyring_3.18.1-1.dsc abc31ab5790bd3bc4e2263a2a2d6b1c6c4d44db79d476e81ca98a278ee3b3444 1204228 gnome-keyring_3.18.1.orig.tar.xz 4facc0025a184511ff32d35db24c3f0e0bc5c4ea2ce55f340363e411b0c0d5ec 16348 gnome-keyring_3.18.1-1.debian.tar.xz Files: f7c27e64cf920dd5ba106a698e6d20bd 2526 gnome optional gnome-keyring_3.18.1-1.dsc 329c75f452028e7dc20b3542ffcb9714 1204228 gnome optional gnome-keyring_3.18.1.orig.tar.xz 8affaacf9ac4e22d65835c6d82747212 16348 gnome optional gnome-keyring_3.18.1-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWI7OvAAoJENb+cQNj+F3TQeQQAKcwpAt3KFv/ioTqnvabq7Xf hVhRYieA7y6933FUBFCDHW59J599+BfitQLaoMoUSdTWwOriR2bmrj0XUXIcQhij ehRchtlXHQlZQwr1gaLOw8Em5v/Fi5EWriV+FC1nw71OeYm8UNqM8+ebyBu5gzte +zRzqVm9zJF27Rb91h9WLjqTyH+XXxT47QNGFjlA9I53Fso37Cu/6as7bgwJL6zO oDkFbK0DLohBqcvvJFUr76Xk3EIMhHt6mcx8rYwA9wTJcqlSmtqZYKfwhsJUoGPa ErDDJHGFwuuLTaBPU3ETQRwL3blslpGAAScZ9bcejKXEGEQPK3RIy9ZGGzH38nzG 6FL20+DsZ4JPl60fRb6yzcmR7CzT8JzGwdiA5LjtSX126xr7QPnTU7AU3Y0n0v14 okxS4oJB5Jf5VA2/uGQu8luqm3MkhF/lHUaLn6jIFQ1jlOymuCOmir8hzaF/F+OT itgd1pCoPnXfAkfiI5tVBWj1AzThTibwNtRcAJSZdfz0/hho1DjNI68aGMrmdH07 /3m1iyUBfxb8qrUXr6IN32bbKIloCsuaQng0iZ8JldaXC/R7TQuWOVW7dDhlkgOm 2mhhhCYHaMDSmYx3vs6AR1G3WSZ1IP0t4LdRQhZb15CSPySPVwScYX34ZN0HM3vb If1DlY44YX/YvLwWSOt5 =iUfJ -----END PGP SIGNATURE-----
--- End Message ---
