** Description changed: We have the following issue affecting a significant portion of our machines running the latest stable Ubuntu 24.04.3 LTS. This happens from time to time. Typical messages: "Reload daemon failed: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)" - or - "dbus-daemon[948]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out" + or + "dbus-daemon[948]: [system] Failed to activate service .. + " 'org.freedesktop.systemd1': timed out" - busctl | grep org.freedesktop.systemd1 shows it is as 'activatable' + # busctl | grep org.freedesktop.systemd1 command shows it is as + 'activatable' The error indicates a system deadlock, most commonly between systemd and the DBus service, preventing system services from starting. The only solution is to hard reboot the system. AFAIK, here systemd is trying to talk to D-Bus (or a systemd D-Bus interface) and not getting a timely reply. dbus is just reporting the timeout — not the root cause. systemd is the provider of org.freedesktop.systemd1, and if it’s not answering D-Bus in time, the deadlock is on its side. Google suggests updating the operating system and systemd to a newer, however we already run the latest stable version of systemd.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2126437 Title: system] Failed to activate service 'org.freedesktop.systemd1': timed out Status in systemd package in Ubuntu: New Bug description: We have the following issue affecting a significant portion of our machines running the latest stable Ubuntu 24.04.3 LTS. This happens from time to time. Typical messages: "Reload daemon failed: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)" or "dbus-daemon[948]: [system] Failed to activate service .. " 'org.freedesktop.systemd1': timed out" # busctl | grep org.freedesktop.systemd1 command shows it is as 'activatable' The error indicates a system deadlock, most commonly between systemd and the DBus service, preventing system services from starting. The only solution is to hard reboot the system. AFAIK, here systemd is trying to talk to D-Bus (or a systemd D-Bus interface) and not getting a timely reply. dbus is just reporting the timeout — not the root cause. systemd is the provider of org.freedesktop.systemd1, and if it’s not answering D-Bus in time, the deadlock is on its side. Google suggests updating the operating system and systemd to a newer, however we already run the latest stable version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2126437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
