I'm talking on ssh and VNC connections as well as login on /dev/tty1, not local X11 display. I know, AFAIU, all these logins/sessions should ensure dbus session running
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c28 --- Comment #28 from Michal Koutný <mkoutny@suse.com> --- (In reply to Dr. Werner Fink from comment #26) through pam_systemd :-/
Can you access your keyring (gnome or kwalletd) with login over ssh, VNC or simply on local console tty1? I can "access" gnome-keyring-daemon on tty1. Also if I `systemctl --user stop dbus.service`, I can see it gets reactivated, i.e. DBus communication works fine. The keyring is locked though (perhaps to lack of pam_gnome_keyring in tty PAM stack).
Idea: you see a timeout message, what if you connect to keyring daemon just fine but the unlock prompt displays on X server that you don't see. -- You are receiving this mail because: You are on the CC list for the bug.