Matthias, this issue has been identified as a bug in the latest version of paraview. I am told it will be included in the 3.8.2 release later this summer. Until then, continue using 3.6. See below for what I received from the paraview developers.
best,
Jeremy