Home | Devuan | Git | Forum | Packages | Popcon
Donate now!
Download

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

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#937: elogind: SwayWM fails to launch from vTTY: Could not take device: No such file or directory
Reply-To: Andrew Bower <andrew@bower.uk>, 937@bugs.devuan.org
Resent-From: Andrew Bower <andrew@bower.uk>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Mark Hindley <mark@hindley.org.uk>
X-Loop: owner@bugs.devuan.org
Resent-Date: Sun, 25 Jan 2026 19:08:01 +0000
Resent-Message-ID: <handler.937.B937.176936805731787@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 937
X-Devuan-PR-Package: src:elogind
X-Devuan-PR-Keywords: 
References: <aXTxAewx_Dfipw1f@shenstone.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> <aXZmH-qltlHnhqwr@shenstone.ab8.net> <5lwDWAzFVgO0qJvAwWKDgJDugs-J0m_YmZuHh-EiotjlVKsI3mtqLpJrW5hsG_qHXYcb1mbEkCpF6Rg-H8u8lrIO5tVhqQLIJOiZLUaEj48=@desmas.net> <176919624261.27301.12565388510718151229.reportbug@desmas-l-fa617xt.desmas>
X-Devuan-PR-Source: elogind
Received: via spool by 937-submit@bugs.devuan.org id=B937.176936805731787
          (code B ref 937); Sun, 25 Jan 2026 19:08:01 +0000
Received: (at 937) by bugs.devuan.org; 25 Jan 2026 19:07:37 +0000
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 19:07:37 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Ofb7AslpdmmZAwAAmSBk0A
	(envelope-from <andrew@bower.uk>)
	for <bugs@devuan.org>; Sun, 25 Jan 2026 19:06:49 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id CE8EA390; Sun, 25 Jan 2026 19:06:48 +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 690604F
	for <937@bugs.devuan.org>; Sun, 25 Jan 2026 19:06:46 +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 1vk5Rc-0040kY-3B;
	Sun, 25 Jan 2026 19:06:45 +0000
Received: from andy by shenstone.ab8.net with local (Exim 4.99.1)
	(envelope-from <andrew@bower.uk>)
	id 1vk5Rc-000000003yL-2jyM;
	Sun, 25 Jan 2026 19:06:44 +0000
Date: Sun, 25 Jan 2026 19:06:44 +0000
From: Andrew Bower <andrew@bower.uk>
To: public@desmas.net
Cc: Mark Hindley <mark@hindley.org.uk>, 937@bugs.devuan.org
Message-ID: <aXZpxAlx-TsyvpRh@shenstone.ab8.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5lwDWAzFVgO0qJvAwWKDgJDugs-J0m_YmZuHh-EiotjlVKsI3mtqLpJrW5hsG_qHXYcb1mbEkCpF6Rg-H8u8lrIO5tVhqQLIJOiZLUaEj48=@desmas.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 07:03:54PM +0000, public@desmas.net wrote:
> On Sunday, January 25th, 2026 at 12:51, Andrew Bower <andrew@bower.uk> wrote:
> > 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.
> 
> This is correct; with --verbose in START_ARGS, I do see this "ready for service" message upon `service elogind restart`.
> 
> Also, man sd_notify has interesting notes about $NOTIFY_SOCKET w/re: return values of calls re: status messages and supporting the various schemes of service managers, but I don't have enough knowledge to know if it's pertinent.
> 
> I'm happy to test any branch or patch made available, but drumming one up myself is unlikely right now.

I have a hunch this will do it...

The error is indeed coming from a call that will cause failure. Setting
this argument to 'true' will deconfigure use of the notify socket once
we've signalled readiness.

$ git diff
diff --git a/src/shared/daemon-util.h b/src/shared/daemon-util.h
index 711885bba..6823cc31d 100644
--- a/src/shared/daemon-util.h
+++ b/src/shared/daemon-util.h
@@ -12,7 +12,7 @@
 
 static inline const char *notify_start(const char *start, const char *stop) {
         if (start)
-                (void) sd_notify(false, start);
+                (void) sd_notify(true, start);
 
         return stop;
 }

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:46 2026;