Open fquirin opened 1 year ago
Probably related error at boot, the userconfig.service
fails as well:
systemctl status userconfig.service
● userconfig.service - User configuration dialog
Loaded: loaded (/lib/systemd/system/userconfig.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-03-03 11:51:23 GMT; 1min 37s ago
Process: 757 ExecStart=/usr/lib/userconf-pi/userconf-service (code=exited, status=126)
Main PID: 757 (code=exited, status=126)
CPU: 66ms
Mar 03 11:51:23 raspberrypi systemd[1]: userconfig.service: Scheduled restart job, restart counter is at 5.
Mar 03 11:51:23 raspberrypi systemd[1]: Stopped User configuration dialog.
Mar 03 11:51:23 raspberrypi systemd[1]: userconfig.service: Start request repeated too quickly.
Mar 03 11:51:23 raspberrypi systemd[1]: userconfig.service: Failed with result 'exit-code'.
Mar 03 11:51:23 raspberrypi systemd[1]: Failed to start User configuration dialog.
I was able to "fix" the DBus server by removing the --websocket
flag from /etc/systemd/system/mark2-hal.service
(and reinstalled dbus-hal as root via bash /usr/local/mycroft/mark-2/dbus-hal/install.sh
just to make sure).
I'm not sure what the purpose is of the websocket connection as I can't find a server, but at least the tools mark2-fan, led ... work now.
[EDIT] I'm assuming the Websocket server is part of Dinkum's messagebus service but is not installed in the sandbox 🤔
Describe the bug
After a fresh installation of the
20221108-mark2_base.img
image the Raspberry Pi will boot up but cannot start the DBus server. As a result the commands to control fan, LEDs and microphone won't work.To Reproduce
Steps to reproduce the behavior:
Expected behavior
DBus server will start as intended.
Log files
Environment (please complete the following information):
Additional context
I think the error is related to user permissions since:
sudo su
thencd /usr/local/mycroft/mark-2/dbus-hal
andpython3 -m dbus_hal