Okay, discussion on IRC seems to believe that this is related to dbus' Upstart job believing that DBus is listening before it actually is (my wife says I have this problem as well). To fix that we need to change the session job to expect a fork, and have the daemon fork, as it will listen before forking.
<jodh> tedg: once you can recreate the problem, I wonder if it is worth tweaking the session dbus.conf job to "expect fork" and "--fork" like the system dbus job already does. That may give a "more correct" started event time.
<tedg> jodh, Why would that be more correct?
<xnox> tedg: dbus forks after it starts to listen, thus expect fork with --fork will make sure started is emitted only after dbus is ready.
Okay, discussion on IRC seems to believe that this is related to dbus' Upstart job believing that DBus is listening before it actually is (my wife says I have this problem as well). To fix that we need to change the session job to expect a fork, and have the daemon fork, as it will listen before forking.
<jodh> tedg: once you can recreate the problem, I wonder if it is worth tweaking the session dbus.conf job to "expect fork" and "--fork" like the system dbus job already does. That may give a "more correct" started event time.
<tedg> jodh, Why would that be more correct?
<xnox> tedg: dbus forks after it starts to listen, thus expect fork with --fork will make sure started is emitted only after dbus is ready.