Devuan bug report logs - #878
loginctl[2676]: Failed to connect to bus: No such file or directory

Package: runit-services; Maintainer for runit-services is (unknown); Source for runit-services is src:runit-services.

Reported by: Andrew Bower <andrew@bower.uk>

Date: Fri, 7 Mar 2025 19:10:01 UTC

Severity: normal

Tags: debian, moreinfo, unreproducible

Fixed in version runit-servics/0.9.0

Done: Lorenzo <plorenzo@disroot.org>

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#878: loginctl[2676]: Failed to connect to bus: No such file or directory
Reply-To: Andrew Bower <andrew@bower.uk>, 878@bugs.devuan.org
Resent-From: Andrew Bower <andrew@bower.uk>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: devuan-dev@lists.dyne.org
X-Loop: owner@bugs.devuan.org
Resent-Date: Mon, 17 Mar 2025 18:44:01 +0000
Resent-Message-ID: <handler.878.B878.17422369316074@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 878
X-Devuan-PR-Package: runit-services
X-Devuan-PR-Keywords: debian unreproducible moreinfo
References: <174137446378.8017.1332012618778784328.reportbug@arden.ab8.net> <Z8yMdObdu9Vfb2yB@hindley.org.uk> <174137446378.8017.1332012618778784328.reportbug@arden.ab8.net> <Z9aYRfZNmwj9JQi2@arden.ab8.net> <Z9ckLq55RAjROME3@hindley.org.uk> <Z9c_4BxpUqeLf8wv@arden.ab8.net> <20250317011057.7010acdd@lorenz.fritz.box> <Z9fGAQaRBgfhedl1@hindley.org.uk> <20250317112326.1e1492dc@lorenz.fritz.box> <174137446378.8017.1332012618778784328.reportbug@arden.ab8.net>
Received: via spool by 878-submit@bugs.devuan.org id=B878.17422369316074
          (code B ref 878); Mon, 17 Mar 2025 18:44:01 +0000
Received: (at 878) by bugs.devuan.org; 17 Mar 2025 18:42:11 +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.16)
	for <debbugs@localhost> (single-drop); Mon, 17 Mar 2025 18:42:11 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id sKMnB9hs2GfnLAAAmSBk0A
	(envelope-from <andrew@bower.uk>)
	for <bugs@devuan.org>; Mon, 17 Mar 2025 18:41:28 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 028D949C; Mon, 17 Mar 2025 18:41:27 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
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=<UNKNOWN> 
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 EA2EC81
	for <878@bugs.devuan.org>; Mon, 17 Mar 2025 18:41:26 +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.94.2)
	(envelope-from <andrew@bower.uk>)
	id 1tuFOu-003W7D-4R; Mon, 17 Mar 2025 18:41:24 +0000
Received: from ajb85 by arden.ab8.net with local (Exim 4.98.1)
	(envelope-from <andrew@bower.uk>)
	id 1tuFOs-00000000763-378F;
	Mon, 17 Mar 2025 18:41:22 +0000
Date: Mon, 17 Mar 2025 18:41:22 +0000
From: Andrew Bower <andrew@bower.uk>
To: Lorenzo <plorenzo@disroot.org>
Cc: Mark Hindley <mark@hindley.org.uk>, 878@bugs.devuan.org
Message-ID: <Z9hs0ilbHJP-cCof@arden.ab8.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20250317112326.1e1492dc@lorenz.fritz.box>
User-Agent: Mutt/2.2.13 (2024-03-09)
X-BlackCat-Spam-Score: 0

On Mon, Mar 17, 2025 at 11:23:26AM +0100, Lorenzo wrote:
> On Mon, 17 Mar 2025 06:49:37 +0000
> Mark Hindley <mark@hindley.org.uk> wrote:
> 
> > On Mon, Mar 17, 2025 at 01:10:57AM +0100, Lorenzo wrote:
> > > > I suspect it's the elogind check script (/etc/sv/elogind/check).
> > > > Let's bring in Lorenzo.
> > > 
> > > very likely; since dbus, elogind and login managers are started at
> > > the same time, I'd expect elogind check at least to fail once at
> > > boot.
> > 
> > Wouldn't it be better to start dbus first?
> > 
> > Mark
> 
> yeah, we already do that, (elogind waits for dbus) but the way the
> start "sequence" works in runit imply that the elogind check file is
> run to check whether elogind is available when starting a login manager
> and there is no guarantee that elogind is ready in the first iteration.
> I guess Andrew is using a login manager that has no hard dependency on
> dbus so the run file, after checking for dbus proceeds on checking for
> elogind even if dbus is not ready yet ..
> Andrew, are you using slim or sddm ?

slim:

  sv start dbus || true
  sv start elogind || true

But 'sv start' will run the check script, won't it, which now tests a
dbus 'ping'.

So probably on my system it is what we (I) recently added [1],

docker:

  sv start elogind

But I don't think we want to start encoding transitive dependencies
which aren't also first class dependencies, so I think we just divert
stderr in the dbus check file as you first suggested!

-Andrew

[1] https://salsa.debian.org/debian/runit-services/-/commit/047d1c88479f0ab750bacdb45a1113d1269641b4

Send a report that this bug log contains spam.

Devuan bug report logs - #878 loginctl[2676]: Failed to connect to bus: No such file or directory

Devuan bug report logs - #878
loginctl[2676]: Failed to connect to bus: No such file or directory