Dbus-broker service issues with F33/F34

A few days ago, after almost a week of Firefox crashing like crazy, I decided to upgrade to F34. The upgrade went well, but the boot process took way longer than before - It was getting stuck at Starting Login Session. But even after passing that and being able to log in, networking doesn’t work at all - I have to manually run systemctl restart NetworkManger && systemctl restart systemd-resolved. Taking a look at what fails, I see that dbus-broker service throws this message: May 28 18:50:30 fedora dbus-broker-launch[2704]: Noticed file-system modification, trigger reload. I have no idea why this happens. And I just got a new firefox tab dead on me out of a sudden.

During boot I could see that dbus-broker was the only service not being started, throwing errors and warnings.

Here’s part of the dbus-broker service logs:

-- Boot a6e4c774799a409f86eb8635189f4570 --
May 28 20:22:38 fedora systemd[1]: Starting D-Bus System Message Bus...
May 28 20:22:38 fedora systemd[1]: Started D-Bus System Message Bus.
May 28 20:22:38 fedora dbus-broker-lau[496]: Ready
May 28 20:24:20 ocfedo systemd[1]: Starting D-Bus System Message Bus...
May 28 20:24:20 ocfedo dbus-broker-launch[2321]: Non unix-domain-socket passed as listener
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:20 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:20 ocfedo systemd[1]: Starting D-Bus System Message Bus...
May 28 20:24:20 ocfedo dbus-broker-launch[2351]: Non unix-domain-socket passed as listener
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:20 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:20 ocfedo systemd[1]: Starting D-Bus System Message Bus...
May 28 20:24:20 ocfedo dbus-broker-launch[2400]: Non unix-domain-socket passed as listener
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:20 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:20 ocfedo systemd[1]: Starting D-Bus System Message Bus...
May 28 20:24:20 ocfedo dbus-broker-launch[2430]: Non unix-domain-socket passed as listener
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:20 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:20 ocfedo systemd[1]: Starting D-Bus System Message Bus...
May 28 20:24:20 ocfedo dbus-broker-launch[2481]: Non unix-domain-socket passed as listener
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:20 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 28 20:24:20 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:20 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:21 ocfedo systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 28 20:24:21 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:21 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:21 ocfedo systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 28 20:24:21 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:21 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:21 ocfedo systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 28 20:24:21 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:21 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:22 ocfedo systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 28 20:24:22 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:22 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:22 ocfedo systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 28 20:24:22 ocfedo systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 28 20:24:22 ocfedo systemd[1]: Failed to start D-Bus System Message Bus.
May 28 20:24:51 ocfedo systemd[1]: Starting D-Bus System Message Bus...
May 28 20:24:51 ocfedo systemd[1]: Started D-Bus System Message Bus.
May 28 20:24:51 ocfedo dbus-broker-lau[3650]: Ready
May 28 20:33:40 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 28 20:33:40 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 30 12:45:11 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 30 12:45:11 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 30 12:50:12 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 30 12:50:57 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 30 12:50:57 ocfedo dbus-broker-launch[3650]: Noticed file-system modification, trigger reload.
May 30 13:05:58 ocfedo dbus-broker[3661]: Dispatched 47622 messages @ 9(±15)μs / message.
May 30 13:05:58 ocfedo systemd[1]: Stopping D-Bus System Message Bus...
May 30 13:05:58 ocfedo systemd[1]: dbus-broker.service: Deactivated successfully.
May 30 13:05:58 ocfedo systemd[1]: Stopped D-Bus System Message Bus.
May 30 13:05:58 ocfedo systemd[1]: dbus-broker.service: Consumed 2.650s CPU time.

Any idea on how to troubleshoot this further?

1 Like

Searching a bit more I found two related bugs in bugzilla:

  1. https://bugzilla.redhat.com/show_bug.cgi?id=1963782
  2. 1965859 – When booting from a kernel built with dracut 054-12.git20210521.fc34, the system is unusable after boot

I was able to boot without issues after downgrading dracut to version 053-4 and re-building the initramfs - but it only works (for me) with kernel version 5.11.12-300. Re-building and booting with initramfs for kernel version 5.12.7-300 still gives me the errors above.

2 Likes

Bluetooth support was added to dracut in that time frame. You could well be bumping into this dracut issue because you have a Bluetooth mouse/keyboard/something connected to your computer. If so, rather than downgrading dracut, an alternative would be to disable the new dracut Bluetooth support using one of the workarounds given in the above issue.

1 Like

Thanks! Great find - I’ve read through it and I’ll try the workaround with disabling bluetooth in dracut - even though I have a bluetooth keyboard and I’ve been waiting for SOOOO LONG to be able to input my luks passphrase using it.

So, for the moment I’ll use the workaround and I’ll monitor the progress in the github issue.

I updated 30 systems from F33 to F34 on the weekend. Two systems did not bring up networking on restart because of this problem. None has Bluetooth, so there is something else going on.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.