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

Received: (at 937) by bugs.devuan.org; 25 Jan 2026 21:12:04 +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 21:12:04 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id tzy9GtWGdmnsFAAAmSBk0A
	(envelope-from <andrew@bower.uk>)
	for <bugs@devuan.org>; Sun, 25 Jan 2026 21:10:45 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 1F7DF390; Sun, 25 Jan 2026 21:10:44 +0000 (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1098:0:86:1000:0:2:1; helo=mx1.mythic-beasts.com; envelope-from=andrew@bower.uk; receiver=bugs.devuan.org 
Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1])
	by email.devuan.org (Postfix) with ESMTPS id AD3DB4F
	for <937@bugs.devuan.org>; Sun, 25 Jan 2026 21:10:42 +0000 (UTC)
Received: by mailhub-cam-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 1vk7NY-007CnE-1L;
	Sun, 25 Jan 2026 21:10:40 +0000
Received: from andy by shenstone.ab8.net with local (Exim 4.99.1)
	(envelope-from <andrew@bower.uk>)
	id 1vk7NX-000000001ov-33Hj;
	Sun, 25 Jan 2026 21:10:39 +0000
Date: Sun, 25 Jan 2026 21:10:39 +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: <aXaGz88FXfnrxWWJ@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>
 <Bjgja1kFVg5L9dYrDd2EsIiFHm-M_ckrZBk0GX-0rxm8DRr9uOpdhAhFwSyU2z6o3PWUOCkkEn4jGMgjMH-Yp7CicQYSCs9EVYqnCRgQgq0=@desmas.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Bjgja1kFVg5L9dYrDd2EsIiFHm-M_ckrZBk0GX-0rxm8DRr9uOpdhAhFwSyU2z6o3PWUOCkkEn4jGMgjMH-Yp7CicQYSCs9EVYqnCRgQgq0=@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 08:49:31PM +0000, public@desmas.net wrote:
> 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 ...

Oh no this is perfect, thanks!

Looks like there's a bunch of nonsense about passing fds to PID1 that we
are not interested in and should fail beningly or not be done.

Here's another possible patch. There's probably a multitude of ways we
can solve this.

diff --git a/src/shared/daemon-util.c b/src/shared/daemon-util.c
index 32180a14b..c641799c8 100644
--- a/src/shared/daemon-util.c
+++ b/src/shared/daemon-util.c
@@ -46,6 +46,7 @@ int close_and_notify_warn(int fd, const char *name) {
 
 static int notify_push_fd(int fd, const char *name) {
         _cleanup_free_ char *state = NULL;
+        int r;
 
         assert(fd >= 0);
         assert(name);
@@ -55,7 +56,14 @@ static int notify_push_fd(int fd, const char *name) {
         if (!state)
                 return -ENOMEM;
 
-        return sd_pid_notify_with_fds(0, /* unset_environment = */ false, state, &fd, 1);
+        r = sd_pid_notify_with_fds(0, /* unset_environment = */ false, state, &fd, 1);
+        if (r == -ENOENT) {
+                 log_warning_errno(r,
+                                   "Supervisor notification channel vanished. Cannot store file descriptor \"%s\", ignoring: %m",
+                                   name);
+                 return 0;
+        }
+        return r;
 }
 
 int notify_push_fdf(int fd, const char *format, ...) {

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