On Do, 30.11.17 11:16, Martyn Welch (martyn.we...@collabora.co.uk) wrote:

> Debugging suggested that XDG_RUNTIME_DIR was not being created when it
> failed. There are 2 processes setting a PAMName, the failing Weston
> service and the user@.service (IIRC this gets called as part of user
> session creation, which I think was triggered by "User=xuser" in our
> weston.service). The user@.service has "PAMName=systemd-user" where as
> weston.service has "PAMName=login". When user@.service called PAM first
> everything worked as expected, if weston.service called PAM first it
> failed. This was our attempt at forcing the former rather than the
> latter.

Ah yeah, we discussed this recently here:

https://github.com/systemd/systemd/issues/7339

So the problem is that user@.service currently can't be started
independently of logind, it must be logind that starts it for you at
the right moment. If you do anyway, XDG_RUNTIME_DIR won't be set, and
things fall apart. We should fix that though...

Lennart

-- 
Lennart Poettering, Red Hat
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Reply via email to