# "Failed to set wall message" after reboot **URL:** \ **Category:** Troubleshooting\ **Created:** [26 November 2023 06:35 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507 "2023-11-26T06:35:30Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![howardroark](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/6a8cbe/32.png) [@howardroark](https://dietpi.com/forum/u/howardroark)\ **Post date:** [26 November 2023 06:35 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/1 "2023-11-26T06:35:30Z")
### Creating a bug report/issue ![image](https://dietpi.com/forum/uploads/default/original/2X/e/e250f1867a13a6e99f4f593a374dff60384436e4.png) #### Required Information - DietPi version ```auto 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 ```auto 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 ``` ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [26 November 2023 12:44 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/2 "2023-11-26T12:44:26Z")
But it reboots? ---
**Author:** ![howardroark](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/6a8cbe/32.png) [@howardroark](https://dietpi.com/forum/u/howardroark)\ **Post date:** [26 November 2023 12:56 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/3 "2023-11-26T12:56:47Z")
Yes. ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [26 November 2023 13:30 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/4 "2023-11-26T13:30:52Z")
Ok then just ignore it, see [https://dietpi.com/forum/t/reboot-error-message/17528](https://dietpi.com/forum/t/reboot-error-message/17528) ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [27 November 2023 08:21 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/5 "2023-11-27T08:21:29Z")
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? ---
**Author:** ![howardroark](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/6a8cbe/32.png) [@howardroark](https://dietpi.com/forum/u/howardroark)\ **Post date:** [27 November 2023 08:29 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/6 "2023-11-27T08:29:06Z")
> [@Problem with installing Wordpress through dietpi-software](https://dietpi.com/forum/t/problem-with-installing-wordpress-through-dietpi-software/18451/15): > > When I use the apt-upgrade command, I see an output like this. Is this normal? The following packages have been kept back: \*\* rpi-eeprom\*\* apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: rpi-eeprom The following packages will be upgraded: containerd.io firmware-atheros firmware-brcm80211 firmware-iwlwifi firmware-misc-nonfree firmware-realtek 6 upgraded, 0 โ€ฆ Yes, I did it recently. ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [27 November 2023 08:33 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/7 "2023-11-27T08:33:01Z")
ok, unfortunately we are still not sure why the messages are not hidden on some systems. ๐Ÿค” ---
**Author:** ![Uli007git](https://dietpi.com/forum/user_avatar/dietpi.com/uli007git/32/5110_2.png) [@Uli007git](https://dietpi.com/forum/u/Uli007git)\ **Post date:** [19 December 2023 18:30 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/8 "2023-12-19T18:30:42Z")
it is annoying ๐Ÿคจ ---
**Author:** ![billybigpotatoes](https://dietpi.com/forum/user_avatar/dietpi.com/billybigpotatoes/32/7346_2.png) [@billybigpotatoes](https://dietpi.com/forum/u/billybigpotatoes)\ **Post date:** [8 January 2025 16:53 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/9 "2025-01-08T16:53:47Z")
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 ---
**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\ **Post date:** [9 January 2025 05:16 UTC](https://dietpi.com/forum/t/failed-to-set-wall-message-after-reboot/18507/10 "2025-01-09T05:16:41Z")
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](https://manpages.debian.org/avahi-daemon.conf#enable_dbus=) Nothing about logind.