On Tue, 6 Mar 2018 09:58:50 +0100
Adam Trhon <adam.tr...@tbs-biometrics.com> wrote:

> > On Fri, 23 Feb 2018 16:00:22 +0100
> > Adam Trhon <adam.tr...@tbs-biometrics.com> wrote:
> >   

> > > This used to work well, but after a systemd update a couple months ago
> > > stopped working with:
> > > 
> > >   weston.service: Unit entered failed state.
> > >   weston.service: Failed with result 'protocol'
> > > 
> > > When we remove the `Type=notify` line, Weston starts fine, but other
> > > apps, which are dependent on it, start too early and fail. The behavior
> > > is consistent across multiple platforms. I checked Weston git history
> > > for changes in compositor/systemd-notify.c, also the bug tracker, but
> > > failed to find any recent changes. 

> 
> The problem was that we use systemd v234 and it contains a bug (fixed in
> v235) that breaks combination of Type=notify and PAMname=login.
> 
> It is fixed here: https://github.com/systemd/systemd/pull/6932

Oh, that's very good to know!


Thanks,
pq

Attachment: pgpSAh2H2Keoq.pgp
Description: OpenPGP digital signature

_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Reply via email to