This might have been https://bugreports.qt.io/browse/QTBUG-65682 which should be fixed meanwhile. So maybe we could remove the workaround again...