On Mon, Jan 10, 2022 at 06:16:03PM +0100, pelzflorian (Florian Pelz) wrote: > Reverting elogind commit 150d7b05074f16db70a2872765edbb39066d80af > makes sway start again. See attached patch. We could graft elogind > or put it on core-updates, but I have not yet properly tested nor > understood. I will test and try understanding now.
Closing, because: * muradm added seatd-service-type and using (service seatd-service-type) in lieu of (elogind-service) works. It looks like a better (?) workaround than making elogind work. * I have not understood and do not plan to debug further. Maybe that I can no longer start sway by typing sway in a virtual terminal is even a deliberate change in logind, but then again I don’t see it on x86_64. Regards, Florian
