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

[Simon McVittie]

On Mon, 01 Feb 2021 at 12:06:04 +0100, Martin Steigerwald wrote:
> 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.
...
> 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 think this might be triggered by security hardening in GLib that results
in gnome-keyring-daemon no longer trusting its parent process to supply it
with a DBUS_SESSION_BUS_ADDRESS. See <https://bugs.debian.org/981420> and
upstream issue <https://gitlab.gnome.org/GNOME/glib/-/issues/2305>.

> I am using Runit as PID 1.

Presumably that means you're getting your D-Bus session bus from dbus-x11
(dbus-launch), because the recommended implementation dbus-user-session
requires systemd?

The reporter of #981420 *is* using systemd, but one theory about why
their gnome-keyring isn't working is that they might be using dbus-x11
rather than dbus-user-session. I haven't been able to confirm or disprove
that theory yet.

The various consequences of a non-systemd init, not all of which are
immediately obvious, are not really something that GNOME projects are
designed to support. We try to keep this working in Debian, but there's
a limit to what we can do in that direction: if the underlying system
does not meet various design assumptions then sometimes we will just
have to say "sorry, you don't have the requirements for this".

    smcv