Comment # 26 on bug 1156501 from Dr. Werner Fink

(In reply to Michal Koutn� from comment #25)
> I'm getting slightly lost. Can this be pinpointed to a particular (pam,
> systemd, dbus,...) update or it only became visible because of the osc
> client update?

I had done a `zypper dup'  and ru into this problem with osc on local X11
display ... and lateron I noticed that I can not work from at home on the same
Tumbleweed system anymore. Only the Leap system is usable.


> (In reply to Dr. Werner Fink from comment #24)
> > Is there a way to cause
> > pam_system(.so) to use path=/run/user/<pid>/bus for dbus connections
> > regardless what interface is used, that for X11 *and* tty.
> On my TW it works (I use gdm). The socket itself is started by the user
> instance and the environment variable is (likely) set by pam_systemd [1].
> 
> Such a socket is recognizable by residing under /run/user/$UID/bus. I guess
> the /tmp placed socket is created by display manager in xinitrc.

I'm talking on ssh and VNC connections as well as login on /dev/tty1, not local
X11 display.
Can you access your keyring (gnome or kwalletd) with login over ssh, VNC or
simply on local console tty1?

> 
> [1]
> https://github.com/openSUSE/systemd/blob/SUSE/v243/src/login/pam_systemd.c#L206

Yep ... I have read this also ... and pam_sm_open_session()