Same here. I noticed the problem after an update on 14.May - maybe it's an coincidence. My workaround was that one described in #11
Same here. I noticed the problem after an update on 14.May - maybe it's an coincidence.
My workaround was that one described in #11