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

version graph

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

Received: (at 937) by bugs.devuan.org; 25 Jan 2026 18:52:46 +0000
Return-Path: <andrew@bower.uk>
Delivered-To: bugs@devuan.org
Received: from email.devuan.org [2a01:4f9:fff1:13::5fd9:f9e4]
	by doc.devuan.org with IMAP (fetchmail-6.4.39)
	for <debbugs@localhost> (single-drop); Sun, 25 Jan 2026 18:52:45 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id QD2XHyNmdmnqfwAAmSBk0A
	(envelope-from <andrew@bower.uk>)
	for <bugs@devuan.org>; Sun, 25 Jan 2026 18:51:15 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 479D3390; Sun, 25 Jan 2026 18:51:15 +0000 (UTC)
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 
Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1])
	by email.devuan.org (Postfix) with ESMTPS id D18884F
	for <937@bugs.devuan.org>; Sun, 25 Jan 2026 18:51:12 +0000 (UTC)
Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <andrew@bower.uk>)
	id 1vk5CZ-003x8F-1s;
	Sun, 25 Jan 2026 18:51:11 +0000
Received: from andy by shenstone.ab8.net with local (Exim 4.99.1)
	(envelope-from <andrew@bower.uk>)
	id 1vk5CZ-000000003ID-0X6m;
	Sun, 25 Jan 2026 18:51:11 +0000
Date: Sun, 25 Jan 2026 18:51:11 +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: <aXZmH-qltlHnhqwr@shenstone.ab8.net>
References: <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>
 <aXX6bc32OL9pq5Od@shenstone.ab8.net>
 <AjiPqLeGnaXYHikPoKEtmYFHJZ3levS3USxQ1D9RRqAb2-AxK6C8sEghJhdPu9hGmM3XemacXuJblCOYHkdwqHdFPaM4POuQ5rQFa2IsQFc=@desmas.net>
 <TApNvbVBVivJwgIYZqIIXozxt3Sy3vJbp5sJLK0wI28obQhFrxOul9aGYozJKN-Xoumx1vpNV9XhVgR6ohxmZBlGyUb89StfNl6GaKcqqQY=@desmas.net>
 <aXZkkvwiIbWp_Jd-@shenstone.ab8.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aXZkkvwiIbWp_Jd-@shenstone.ab8.net>
User-Agent: Mutt/2.2.13 (2024-03-09)
X-BlackCat-Spam-Score: 0
X-Spam-Status: No, score=0.0
On Sun, Jan 25, 2026 at 06:44:34PM +0000, Andrew Bower wrote:
> On Sun, Jan 25, 2026 at 06:21:25PM +0000, public@desmas.net wrote:
> > I've built elogind packages with log-trace: true and debug-extra: ['elogind'], and it provides more detail, e.g.:
> > 
> > > elogind[13734]: Got message type=method_call sender=:1.30 destination=org.freedesktop.login1 path=/org/freedesktop/login1/session/_38 interface=org.freedesktop.login1.Session member=TakeDevice  cookie=10 reply_cookie=0 signature=uu error-name=n/a error-message=n/a
> > > elogind[13734]: Failed to send notify message to '/run/.s-s-d-notify.49UVq6/notify': No such file or directory
> > > elogind[13734]: Sent message type=signal sender=n/a destination=:1.30 path=/org/freedesktop/login1/session/_38 interface=org.freedesktop.login1.Session member=PauseDevice cookie=76 reply_cookie=0 signature=uus error-name=n/a error-message=n/a
> > > elogind[13734]: Sent message type=error sender=n/a destination=:1.30 path=n/a interface=n/a member=n/a cookie=77 reply_cookie=10 signature=s error-name=org.freedesktop.DBus.Error.FileNotFound error-message=No such file or directory
> > > elogind[13734]: Failed to process message type=method_call sender=:1.30 destination=org.freedesktop.login1 path=/org/freedesktop/login1/session/_38 interface=org.freedesktop.login1.Session member=TakeDevice cookie=10 reply_cookie=0 signature=uu error-name=n/a error-message=n/a: No such file or directory
> 
> Oh this is interesting.
> 
> Since the initial readiness exchange seems to work OK, I wonder if

Just to confirm this with you - when you added '--verbose' to
START_ARGS, did the output confirm to you:

 -> Notification => ready for service.

? If you only relied on reboot then 'service elogind start' should show
this.

> what's happening is elogind continues to send information over this
> channel through its lifetime despite the fact it is now closed, and I
> wonder if it then takes some wrong code paths which prevents it from
> performing its main function properly.
> 
> It might be worth it looking at the places that elogind tries to signal
> a notification and make sure failure to signal on a closed channel is
> ignored and doesn't cause a broader error.

Send a report that this bug log contains spam.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Mon Jan 26 17:37:44 2026;