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

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Lorenzo <plorenzo@disroot.org>
Subject: bug#878: marked as done (loginctl[2676]: Failed to connect to
 bus: No such file or directory)
Message-ID: <handler.878.D878.174429307214489.ackdone@bugs.devuan.org>
References: <20250410155027.020b983f@lorenz.fritz.box>
 <174137446378.8017.1332012618778784328.reportbug@arden.ab8.net>
X-Devuan-PR-Message: closed 878
X-Devuan-PR-Package: runit-services
X-Devuan-PR-Keywords: debian unreproducible moreinfo
Reply-To: 878@bugs.devuan.org
Date: Thu, 10 Apr 2025 13:52:01 +0000
Content-Type: multipart/mixed; boundary="----------=_1744293121-14507-0"

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

Your message dated Thu, 10 Apr 2025 15:50:27 +0200
with message-id <20250410155027.020b983f@lorenz.fritz.box>
and subject line done in Debian - runit-services 0.9.0
has caused the Devuan bug report #878,
regarding loginctl[2676]: Failed to connect to bus: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)


-- 
878: https://bugs.devuan.org/cgi/bugreport.cgi?bug=878
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Andrew Bower <andrew@bower.uk>

To: Devuan Bug Tracking System <submit@bugs.devuan.org>

Subject: loginctl[2676]: Failed to connect to bus: No such file or directory

Date: Fri, 07 Mar 2025 19:07:43 +0000

Package: elogind
Version: 255.17-2
Severity: normal

Dear Maintainer,

I see this reported through syslog at the error level:

  loginctl[2676]: Failed to connect to bus: No such file or directory

I'm not aware of anything notably special about my environment. I've not
noticed it before, but that's probably because I just switched syslog daemon.

Thanks,

Andrew


-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 6 (excalibur/ceres)
Release:	6
Codename:	excalibur ceres
Architecture: x86_64

Kernel: Linux 6.10.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages elogind depends on:
ii  dbus                  1.16.2-1devuan1
ii  debconf               1.5.89
ii  init-system-helpers   1.68devuan1
ii  libacl1               2.3.2-2+b1
ii  libc6                 2.41-3
ii  libcap2               1:2.73-4
ii  libelogind0           255.17-2
ii  libeudev1 [libudev1]  3.2.14-2
ii  libmount1             2.40.4-5devuan1
ii  libpam0g              1.7.0-3
ii  libselinux1           3.8-4

Versions of packages elogind recommends:
ii  libpam-elogind  255.17-2
ii  polkitd         126-2devuan1

elogind suggests no packages.

-- no debconf information

[Message part 3 (message/rfc822, inline)]

From: Lorenzo <plorenzo@disroot.org>

To: 878-done@bugs.devuan.org

Subject: done in Debian - runit-services 0.9.0

Date: Thu, 10 Apr 2025 15:50:27 +0200

Package: runit-servics
Version: 0.9.0

thanks

Send a report that this bug log contains spam.