Subject: Re: elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory

From: [email-masked]
Date: Sun, 25 Jan 2026 20:49:31 +0000

On Sunday, January 25th, 2026 at 13:40, Andrew Bower <[email-masked]> wrote:
> Instead we should find out exactly what is calling sd_notify() at these
> later points and make it handle the -errno style error code
> appropriately. I can't see where this is getting called.
> 
> We could hack s-s-d to keep showing us or hack elogind to print them
> out. One quick way might be to hack src/shared/daemon-util.h
> NOTIFY_READY definition to misspell 'READY' as 'REAxDY' and whack a big
> --notify-timout into START_ARGS; then s-s-d will keep waiting and
> printing everything it gets from elogind and we can trace it that way.

Not sure there's enough detail with this method; attached elogind-reaxdy.log; double line breaks are entered by me (marking before sway, w/in sway, exiting sway); sd_notify(true, ...) reverted.  Sway launches successfully ...

START_ARGS='--background --notify-await --notify-timeout 120 --verbose --no-close'

--
Nathan