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

🔗 View this message in rfc822 format

Subject: bug#937: elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory
Reply-To: public@desmas.net, 937@bugs.devuan.org
Resent-From: public@desmas.net
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Mark Hindley <mark@hindley.org.uk>
Resent-Date: Sat, 24 Jan 2026 18:16:01 +0000
Resent-Message-ID: <handler.937.B937.176927850330000@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
References: <176919624261.27301.12565388510718151229.reportbug@desmas-l-fa617xt.desmas> <aXTxAewx_Dfipw1f@shenstone.ab8.net> <176919624261.27301.12565388510718151229.reportbug@desmas-l-fa617xt.desmas>
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=185.70.43.96; helo=mail-4396.protonmail.ch; envelope-from=public@desmas.net; receiver=bugs.devuan.org 
Date: Sat, 24 Jan 2026 18:14:06 +0000
To: Andrew Bower <andrew@bower.uk>
From: public@desmas.net
Cc: 937@bugs.devuan.org
Message-ID: <-8H38rMe5nzcSivo6VBrcez-Wwy0MWKC2B2Zd0tdxrPv5su8HOQ7jwPvqw9hCvY_xLWV7Q2SgaHim2Vl1iyuX9G9j7-r103tRu95Ns3fiQ8=@desmas.net>
In-Reply-To: <aXTxAewx_Dfipw1f@shenstone.ab8.net>
Feedback-ID: 55650293:user:proton
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="b1=_fmLD2Gao06HNrMhD898zrA7bENlntVC5lyeDQaRT8U"

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

On Saturday, January 24th, 2026 at 10:19, Andrew Bower <andrew@bower.uk> wrote:
> ... snip ...
>
> Now it is far from clear that this is what is actually happening but it
> is a possible cause.
> 
> Would you mind sharing the file /etc/init.d/.depend.start, please, so we
> can see what the dependency chain is on your system? That might reveal
> if there is an issue similar to the Service A/Service B interactions
> I've described above.

Thank you for that detailed explanation Andrew. Attached is /etc/init.d/.depend.start from the system.

On Saturday, January 24th, 2026 at 10:19, Andrew Bower <andrew@bower.uk> wrote:
> Another user has also suggested something to eliminate (1) as a cause of
> this regression. You could reinstall version -4 of the package and edit
> the following variable as such:
> 
> DAEMON_ARGS="-D"
> START_ARGS=""
> 
> i.e. putting the behaviour back how it was but with the structure of the
> new version of the initscript.

I have tested this, and indeed this allows Sway to launch, successfully "Found 2 GPUs" and "Initializing DRM backend for /dev/dri/card...".

On Saturday, January 24th, 2026 at 10:19, Andrew Bower <andrew@bower.uk> wrote:
> This is the failing call:
> 
> ret = sd_bus_call_method(session->bus, "org.freedesktop.login1", session->path,
> 
> "org.freedesktop.login1.Session", "TakeDevice", &error, &msg, "uu",
> major(st.st_rdev), minor(st.st_rdev));

I have attached also the D-Bus system message output, from both 255.17-4 without initscript daemon/startup argument changes (255.17-4-unedited.dbus.log), and also with (255.17-4-edited.dbus.log).

--
Nathan

[.depend.start (application/octet-stream, attachment)]

[255.17-4-unedited.dbus.log (text/x-log, attachment)]

[255.17-4-edited.dbus.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