Devuan bug report logs - #937
elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory

Package: src:elogind; Maintainer for src:elogind is Mark Hindley <mark@hindley.org.uk>;

Reported by: Nathan Schulte <public@desmas.net>

Date: Fri, 23 Jan 2026 19:26:02 UTC

Severity: grave

Tags: patch

Found in version elogind/255.17-4

Full log

Message #97 received at 937@bugs.devuan.org (full text, mbox, reply):

Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=79.135.106.105; helo=mail-106105.protonmail.ch; envelope-from=public@desmas.net; receiver=bugs.devuan.org 
Date: Sun, 25 Jan 2026 20:49:31 +0000
To: Andrew Bower <andrew@bower.uk>
From: public@desmas.net
Cc: Mark Hindley <mark@hindley.org.uk>, 937@bugs.devuan.org
Subject: Re: elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory
Message-ID: <Bjgja1kFVg5L9dYrDd2EsIiFHm-M_ckrZBk0GX-0rxm8DRr9uOpdhAhFwSyU2z6o3PWUOCkkEn4jGMgjMH-Yp7CicQYSCs9EVYqnCRgQgq0=@desmas.net>
In-Reply-To: <aXZxyIz3dx-EcRoK@shenstone.ab8.net>
References: <Ebb3IokxY5iTIfgVS7a1A2GzbW2UyI4bLwvQybbY1V0tvbG29LH7QxEBQlfYw3MEcr8LFjHBsyBB_dnkNpjvZT1w9hDErAIhSyuunHTVfjY=@desmas.net> <TApNvbVBVivJwgIYZqIIXozxt3Sy3vJbp5sJLK0wI28obQhFrxOul9aGYozJKN-Xoumx1vpNV9XhVgR6ohxmZBlGyUb89StfNl6GaKcqqQY=@desmas.net> <aXZkkvwiIbWp_Jd-@shenstone.ab8.net> <aXZmH-qltlHnhqwr@shenstone.ab8.net> <5lwDWAzFVgO0qJvAwWKDgJDugs-J0m_YmZuHh-EiotjlVKsI3mtqLpJrW5hsG_qHXYcb1mbEkCpF6Rg-H8u8lrIO5tVhqQLIJOiZLUaEj48=@desmas.net> <aXZpxAlx-TsyvpRh@shenstone.ab8.net> <7mNBwywdoAN79Oaj5pO9iAzPG3ta4A_iwhFdrl82DopmmP88qhVyH9s-Fml5_8XvGxZHotFzH1pAfqif16VsKFaPho1iSLgAIS4Qh4aZ7cI=@desmas.net> <aXZtSb99Wa3n5bNw@shenstone.ab8.net> <aXZxyIz3dx-EcRoK@shenstone.ab8.net>
Feedback-ID: 55650293:user:proton
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="b1=_VE9ubjs2mmAnOCF7DCqkMSofmgDVabODcOwrYBX7Q"

[Message part 1 (text/plain, inline)]

On Sunday, January 25th, 2026 at 13:40, Andrew Bower <andrew@bower.uk> 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

[elogind-reaxdy.log (text/x-log, attachment)]

Send a report that this bug log contains spam.

Devuan bug report logs - #937 elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory

Devuan bug report logs - #937
elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory