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 #47 received at 937@bugs.devuan.org (full text, mbox, reply):

Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1098:0:82:1000:0:2:1; helo=mx2.mythic-beasts.com; envelope-from=andrew@bower.uk; receiver=bugs.devuan.org 
Date: Sun, 25 Jan 2026 11:11:41 +0000
From: Andrew Bower <andrew@bower.uk>
To: 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: <aXX6bc32OL9pq5Od@shenstone.ab8.net>
References: <176919624261.27301.12565388510718151229.reportbug@desmas-l-fa617xt.desmas>
 <aXTxAewx_Dfipw1f@shenstone.ab8.net>
 <-8H38rMe5nzcSivo6VBrcez-Wwy0MWKC2B2Zd0tdxrPv5su8HOQ7jwPvqw9hCvY_xLWV7Q2SgaHim2Vl1iyuX9G9j7-r103tRu95Ns3fiQ8=@desmas.net>
 <aXVXGa2LGtvhCkbb@arden.ab8.net>
 <zmT_m_nKXVguZywkFoxgaimZF7OJ5qhOxfE1E9bnGso6Dx6upPrMjSo-R-3oLmWpYWUgBBZ1HqS_wtNTqxeWhYw5Y3P04WztnR4jY9dEamg=@desmas.net>
 <aXXb-qCA_8lUBWWc@shenstone.ab8.net>
 <Ebb3IokxY5iTIfgVS7a1A2GzbW2UyI4bLwvQybbY1V0tvbG29LH7QxEBQlfYw3MEcr8LFjHBsyBB_dnkNpjvZT1w9hDErAIhSyuunHTVfjY=@desmas.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Ebb3IokxY5iTIfgVS7a1A2GzbW2UyI4bLwvQybbY1V0tvbG29LH7QxEBQlfYw3MEcr8LFjHBsyBB_dnkNpjvZT1w9hDErAIhSyuunHTVfjY=@desmas.net>
User-Agent: Mutt/2.2.13 (2024-03-09)

On Sun, Jan 25, 2026 at 09:57:02AM +0000, public@desmas.net wrote:
> On Sunday, January 25th, 2026 at 03:01, Andrew Bower <andrew@bower.uk> wrote:
> > It does run as root but I wonder if some privilege has somehow got lost
> > in the different daemonization process. This might give us some clues:
> > 
> > cat /proc/$(cat /run/elogind.pid)/status
> 
> The only difference I see here is that SIGINT is not ignored by elogind (with --no-close etc. START_ARGS; vs elogind-daemon).

How very strange this all is.

Well there is one other thing we could try - could it all be about
timings in the end after all? We could do this combination:

  DAEMON_ARGS=''
  START_ARGS='--verbose --background'

I.e. just remove '--notify-await' but keep s-s-d doing the
backgrounding.

And yet we didn't find anything in your startup sequence that was
waiting for elogind.

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