Bug#981555: does not appear to respond to DBUS interface anymore

[Martin Steigerwald]

Package: gnome-keyring
Version: 3.36.0-1
Severity: important

Dear maintainers,

Since this work week Evolution on my laptop does not ask for GNOME keyring
password anymore. Instead after some kind of a timeout it directly asks
for the password of the connection.

It does so for retrieving mails, for sending mails, for calendar and 
addressbook access. I am using Evolution EWS with Office 365.

Since this worked before I do not consider this to be an upstream issue.
However also 'gnome-keyring' package does not appear to have been changed
recently. So it may be related to the upgrade of a different package.

I do see

kdeinit5: Got EXEC_NEW 'dbus-send' from launcher.
kdeinit5: preparing to launch 'libkdeinit5_dbus-send'
Could not open dbus-send using a library: Cannot load library libkdeinit5_dbus-send: (libkdeinit5_dbus-send: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)
kdeinit5: PID 13520 terminated.

in ~/.xsession-errors which may be related.

However I did not find 'libkdeinit5_dbus-send' anywhere with 'apt-file search'.

GNOME Keyring daemon, which to my understanding provides Secrets Services
DBUS API, is running, excerpt from 'ps aux':

someuser       13491  0.0  0.0  15756  4984 ?        SL   08:52   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login

However also 'qdbus' reports that the DBUS API is not accessible:

% qdbus org.freedesktop.secrets 
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

It does not even seem to exist:

% qdbus | grep secrets
[… nothing …]

However also if started manually GNOME Keyring does not report an error:

% /usr/bin/gnome-keyring-daemon --login
[… keeps running, no output, even after Evolution failing to connect DBUS
API …]

I am using Runit as PID 1. This has not been an issue before.

Thanks,
Martin

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-rc6-tp520 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]                  1.12.20-1
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gcr                                          3.38.1-1
ii  libc6                                        2.31-9
ii  libcap-ng0                                   0.7.9-2.2+b1
ii  libcap2-bin                                  1:2.44-1
ii  libgck-1-0                                   3.38.1-1
ii  libgcr-base-3-1                              3.38.1-1
ii  libgcrypt20                                  1.8.7-2
ii  libglib2.0-0                                 2.66.4-3
ii  p11-kit                                      0.23.22-1
ii  pinentry-gnome3                              1.1.0-4

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  3.36.0-1
ii  libpam-gnome-keyring  3.36.0-1

gnome-keyring suggests no packages.

-- debconf-show failed