Your message dated Wed, 30 Aug 2023 22:47:29 +0100
with message-id <0fc39bd487ffd5222b241a7918382dce908f1bda.ca...@debian.org>
and subject line Re: reboot/poweroff throw errors if dbus/systemd-logind is not
running
has caused the Debian Bug report #1042015,
regarding reboot/poweroff throw errors if dbus/systemd-logind is not running
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 ow...@bugs.debian.org
immediately.)
--
1042015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 252.12-1
Since Debian Bookworm (systemd 252), the reboot, poweroff and "shutdown
now" commands throw the following error if the dbus service is not running:
-------
Failed to connect to bus: No such file or directory
-------
and if dbus is running, but systemd-logind is not:
-------
Failed to set wall message, ignoring: Unit
dbus-org.freedesktop.login1.service failed to load properly, please
adjust/correct and reload service manager: File exists
Call to Reboot failed: Unit dbus-org.freedesktop.login1.service failed
to load properly, please adjust/correct and reload service manager: File
exists
-------
The action however finishes properly. I know that systemd-logind is
required for scheduled shutdowns/reboots, but it is not for immediate
ones. I am not sure if those were ever supposed to send a wall message,
as the possible purpose is minimal if the action is performed
immediately. However, the "wall" command works perfectly fine without
the two services and until Debian Bullseye, those errors were not thrown.
The "--no-wall" flag, which is supposed to suppress wall messages sent
by those commands, has no effect on the dbus/systemd-logind contact
attempt/error messages. Also I could not find any setting in
/etc/systemd to change this new behaviour. "reboot -f" works, but it has
unwanted implications, most notably no "sync" and unclean/no umounts.
The motivation to solve these errors without installing dbus and
enabling systemd-logind is that both are not required on most server
systems. systemd-logind is used for desktop sessions and by some GUI
applications, and for mentioned scheduled shutdowns/reboots, but for a
single admin server system it is usually not needed/used. For embedded
systems with low power/RAM it can hence make sense to have
systemd-logind masked and dbus uninstalled, to free up some resources,
cleanup the process tree, logs etc.
I guess it is an upstream question/issue, but I wanted to be sure about
this first. Hopefully someone can give more insights.
Best regards,
Micha
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
On Tue, 25 Jul 2023 21:37:51 +0200 MichaIng <mi...@dietpi.com> wrote:
> Package: systemd
> Version: 252.12-1
>
> Since Debian Bookworm (systemd 252), the reboot, poweroff and
"shutdown
> now" commands throw the following error if the dbus service is not
running:
>
> -------
> Failed to connect to bus: No such file or directory
> -------
>
> and if dbus is running, but systemd-logind is not:
>
> -------
> Failed to set wall message, ignoring: Unit
> dbus-org.freedesktop.login1.service failed to load properly, please
> adjust/correct and reload service manager: File exists
> Call to Reboot failed: Unit dbus-org.freedesktop.login1.service
failed
> to load properly, please adjust/correct and reload service manager:
File
> exists
> -------
You can choose between installing one of the D-Bus implementations, or
keeping the warnings and ignoring them. Dependencies are documented
quite clearly.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
--- End Message ---
