zbus yields `reply timeout expired` when run as Systemd service

Hi, first of all, thanks for the awesome crate, it is so much better in comparison to other alternatives, great work.

So the issue is:

When I use zbus in a standard app everything works as expected, but when I try to run my dbus server as a systemd service it does not work on initial connection.

What I mean by that is that systemd will automatically start service associated with dbus service name. So for example, if I call SayHello method (using dbus-send) on org.zbus.server it will start the service responsible for handling it, and our dbus server will return the requested data.

It works as expected when testing with dbus-rs server example

But with zbus server example it never returns data, it starts as expected and just hangs, and after some time we get Error org.freedesktop.DBus.Error.NoReply, when service is already started we can send the request again and then it will return data as expected, so there is some problem with initial startup call, that zbus ignores. Actually, the event never reaches function associated with it, so in the above example say_hello is never called

EDIT: I'll test it with low level example and I'll let you know if this helps