I found a good documented PR in another project which explains the dbus errors in detail.
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
Posts
-
RE: Docker Watchtower container restarting and mm container errors after upgrade
-
RE: Version 2.34.0 - Missing X Server or $DISPLAY (Docker version of MMOS)
the dbus errors in the mm logs are only noise, see https://forum.magicmirror.builders/topic/20032/docker-watchtower-container-restarting-and-mm-container-errors-after-upgrade/7#
If the problem occurs:
- can you provide the logs of the labwc container?
docker logs labwc - can yo try to restart the containers without reboot with
cd /opt/mm/run && docker compose up -d --force-recreate?
- can you provide the logs of the labwc container?
-
RE: Universal-PIR - ‘GPIOcommand exited with error'
from the module README.md:
Please test the used commands first outside of MagicMirror². If they not work from a terminal it makes no sense to use them inside this module.
So what is the output if you run
gpiomon -r -b gpiochip0 17on your machine?And provide the version with
gpiomon -v