Investigate boltd "hangs" on polkit_authority_get_sync
21:29:00 cobalt boltd[3280]: bolt 0.5 starting up.
21:29:00 cobalt boltd[3280]: config: loading user config
21:29:00 cobalt boltd[3280]: bouncer: initializing polkit
21:29:25 cobalt boltd[3280]: udev: initializing udev
21:29:25 cobalt boltd[3280]: store: loading devices
NB: the 25 seconds gap between the bouncer
and udev
. The significant bit that happens is the creating of the policy kit authority in bolt-bouncer.c:bouncer_initialize
; which indeed we create in a sync way.
The question is: are we ok with that, or should we do something differently. Quick ideas:
- declare the dependency in on polkit in the systemd unit
- use the async version and delay object exports to after we got the authority back
- will that interfere with
boltd
dbus activation, because now the unit might be active before we are actual ready to receive dbus calls?
- will that interfere with