"Failed to set wall message" after reboot

Creating a bug report/issue

Required Information

  • DietPi version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=24
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
  • Distro version | bookworm 0
  • Kernel version | Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | RPi4 8GB
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

But it reboots?

Yes.

Ok then just ignore it, see
https://dietpi.com/forum/t/reboot-error-message/17528

1 Like

usually, we added a workaround to hide these messages on reboot. However, we already know, for system updated from Bullseye to Bookworm, this might not work always.

@howardroark
Was your systemt update from Debian Bullseye to Debian Bookworm before?

1 Like

Yes, I did it recently.

ok, unfortunately we are still not sure why the messages are not hidden on some systems. :thinking:

2 Likes

it is annoying :face_with_raised_eyebrow:

Hi - have just started seeing this error after installing avahi-daemon - I am not sure why this package has a dependancy on DBus - there is a dbus reference in the startup initd script - however this can easily be changed to remove the dbus association

It pulls dbus as dependency, but obviously it tries to contact systemd-logind though it. You really see the Failed to set wall message error somewhere, in its journalctl -u avahi-daemon logs or where? Or is it only the 2nd part of the log, about failing logind access, or even about dbus access only?

In its config I see only a dbus connection to provide an additional client API through it: avahi-daemon.conf(5) — avahi-daemon — Debian bookworm — Debian Manpages
Nothing about logind.