No, that's about publishing a new service, not calling into others. It's probably due to dbus-broker supporting SO_PEERSEC to acquire credentials. On Fri, 29 Mar 2024 at 21:14, Mantas Mikulėnas <grawity@xxxxxxxxx> wrote: > > I don't know, but it might be related to this note: > https://github.com/systemd/systemd/commit/0a207d8f234ff7ea0d7988445e38685090fc930e > > On Fri, Mar 29, 2024, 19:53 Nils Kattenbeck <nilskemail@xxxxxxxxx> wrote: >> >> On Fri, Mar 29, 2024 at 7:04 AM Mantas Mikulėnas <grawity@xxxxxxxxx> wrote: >> > >> > It's probably a difference between dbus-daemon and dbus-broker, I suspect. >> >> Hi, that was indeed the problem. Installing dbus-broker on one of the >> machines did in fact fix this. Any idea why that might be? I do not >> know the differences between the two so I am not completely >> comfortable with replacing dbus-daemon with dbus-broker just to fix >> this small issue. This issue at least confirms to me that they are not >> drop-in compatible. >> >> Kind regards, >> Nils