bbaldino

Looks like it takes a decent amount of time to join the page, which could be the chrome sluggishness I mentioned above. Did you try what I suggested?

Is the machine rebooting after each session? I don't think you need to keep chrome running, just start it up after reboot. I think @aaronkvanmeerten is more familiar with what...

@aaronkvanmeerten was the mastermind behind it, but I'm pretty sure it just comprised of starting chrome up on boot, as it does a fair bit of initialization that first time.

The Jibri readme is out of date unfortunately (I just created a PR [here](https://github.com/jitsi/jibri/pull/134) to update it). You can check the updated instructions there. As for the snd-aloop issue, @aaronkvanmeerten...

> For many kernels, the snd-aloop is in the -extra package, like: linux-image-extra-virtual @aaronkvanmeerten it looks like this is the one he tried. maybe it's the location it's searching for...

I'm planning on taking a look at this soon (after some current tasks), but if you have a chance to repro you might be able to speed things along. If...

Those Jibri logs look harmless, though I'd be able to tell more with the full log. > 2018-08-02 18:56:43.727 SEVERE: [37] org.jitsi.jibri.capture.ffmpeg.executor.impl.AbstractFfmpegExecutor.isHealthy() Ffmpeg is running but doesn't appear to be...

Nothing jumps out from the Jibri logs, it shut down fine due to being in an empty call (it didn't detect any other participants in the call so it leaves...

So is failover without Jibri working consistently? Or no?

@bgrozev any ideas there for the bridge failover?