On Dec 20, 2023, at 00:31, Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR launcher_run_child @ ../src/launch/launcher.c +347: Permission denied > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_add_services @ ../src/launch/launcher.c +804 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_run @ ../src/launch/launcher.c +1415 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: run @ ../src/launch/main.c +152 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: main @ ../src/launch/main.c +178 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: Exiting due to fatal error: -107 > Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE > Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Most likely, this is the problem, dbus-broker can’t start due to a permissions problem, possibly related to the SELinux relabel requirement. Pretty much everything uses DBUS for interprocess communication in the systemd world, so a failed dbus-broker would break quite a bit. You might need to run the relabel with SELinux in permissive mode. -- Jonathan Billings -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
