Because bluedevil-monolithic goes to background, BlueDevilDaemon::finished triggers immediately.
Both BlueDevilDaemon::finished() and BlueDevilDaemon::monolithicQuit() were added in the same commit. monolithicQuit() is triggered on d-bus reply.
I suspect that after processing the "quit" message bluedevil-monolithic is still registered in dbus for some time and will prevent another instance. So this watcher is probably not needed.
If it's true, bluedevil-monolithic needs a flag to run in foreground.
Because bluedevil- monolithic goes to background, BlueDevilDaemon ::finished triggers immediately.
Both BlueDevilDaemon ::finished( ) and BlueDevilDaemon ::monolithicQui t() were added in the same commit. monolithicQuit() is triggered on d-bus reply. monolithic is still registered in dbus for some time and will prevent another instance. So this watcher is probably not needed.
I suspect that after processing the "quit" message bluedevil-
If it's true, bluedevil- monolithic needs a flag to run in foreground.