Enno G.

@bbaldino Thanks for the quick response. I will try tomorrow morning and see if it helps!

Okay I tried now to do a `mvn clean` and then compiled again. After that I checked if the logging directory exists. Both actions did not change anything as far...

So I now tried to upgrade the Selenium POM to `3.141.59` which didn't made a difference. I will now do a downgrade of our Chrome to V78 which you are...

Also a small note here: https://stackoverflow.com/questions/2210720/how-to-analyse-a-noclassdeffounderror-caused-by-an-ignored-exceptionininitialize

I more and more get the feeling that this is not Jibri related but rather a Selenium/Chrome problem. We don't have `static` initilizers as far as I can tell (maybe...

@bbaldino That is the new current setup. I downgraded from 11 to 1.8 yesterday evening. EDIT: I upgraded to Git HEAD this morning after some tries with Tag 8.0.

Leap 15.2 1. `zypper ar https://download.opensuse.org/repositories/home:/SchoolGuy:/jitsi/openSUSE_Leap_15.2/home:SchoolGuy:jitsi.repo` 1. `zypper in nginx prosody lua51-zlib jitsi-meet jitsi-videobridge jitsi-jicofo` 1. Adjust the setup according to your Debian instructions.

In some minutes I will push a more extensive commit to this PR: https://github.com/jitsi/handbook/pull/82

This is our package: https://build.opensuse.org/package/show/home:SchoolGuy:jitsi/Jitsi-Jibri

Regarding Source installation: Take the `maven_repo.tar,gz` from the package and do the following: 1. `zypper ar http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google-Chrome` 1. `wget https://dl.google.com/linux/linux_signing_key.pub` 1. `rpm --import linux_signing_key.pub` 1. `zypper ref -f` 1....