Bug#994961: glib2.0: gnome-keyring unable to unlock login keyring on some systems since GLib 2.70.0-1

Francois Marier francois at debian.org
Sun Sep 26 18:57:53 BST 2021


On 2021-09-24 at 02:28:05, Simon McVittie (smcv at debian.org) wrote:
> > I do have the dbus-user-session package installed.
> 
> I'm surprised by this. It's clearly still picking up XDG_RUNTIME_DIR
> from the environment, so I would have expected it to be able to connect
> to $XDG_RUNTIME_DIR/bus (arguably that's a bug, in that it should not be
> trusting the environment at all when run with capabilities, but it's
> necessary as long as gnome-keyring-daemon is setcap).
> 
> Do you have a socket at $XDG_RUNTIME_DIR/bus owned by your uid?

It doesn't look like it:

$ ls -lh $XDG_RUNTIME_DIR/bus
ls: cannot access '/run/user/1000/bus': No such file or directory

> What is the status of the session bus? (`systemctl --user status dbus.service`
> and `systemctl --user status dbus.socket`)

$ systemctl --user status dbus.service
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status dbus.socket
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1

I'll give gnome-keyring 40.0-3 a go once it makes it to unstable.

Francois

-- 
https://fmarier.org/



More information about the pkg-gnome-maintainers mailing list