I have a cubox-i4p just installed arch but for some reason can't get dbus service to run.
$this->bbcode_second_pass_code('', '
systemctl status dbus.socket
● dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: failed (Result: service-start-limit-hit) since Tue 2021-02-23 15:19:01 UTC; 1min 1s ago
Triggers: ● dbus.service
Listen: /run/dbus/system_bus_socket (Stream)
Feb 23 15:19:00 alarm systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 23 15:19:01 alarm systemd[1]: dbus.socket: Failed with result 'service-start-limit-hit'.
systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: failed (Result: exit-code) since Tue 2021-02-23 15:19:01 UTC; 1min 7s ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Process: 23087 ExecStart=/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslo>
Main PID: 23087 (code=exited, status=1/FAILURE)
Feb 23 15:19:00 alarm systemd[1]: Started D-Bus System Message Bus.
Feb 23 15:19:01 alarm dbus-daemon[23087]: Failed to start message bus: Failed to drop capabilities: Invalid argument
Feb 23 15:19:01 alarm systemd[1]: dbus.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 15:19:01 alarm systemd[1]: dbus.service: Failed with result 'exit-code'.
Feb 23 15:19:01 alarm systemd[1]: dbus.service: Start request repeated too quickly.
Feb 23 15:19:01 alarm systemd[1]: dbus.service: Failed with result 'exit-code'.
Feb 23 15:19:01 alarm systemd[1]: Failed to start D-Bus System Message Bus.
')