Wrong draw order using ParaView's pvbatch in an Arch Linux Docker container on GitLab CI

ParaView Support
21

I have at this point got six different branches to figure out where this bug(?) is coming from. You can see an overview here:

screenshot_20240308_161119
screenshot_20240308_161119549×555 45.5 KB

  • archlinux-* branches use Arch Linux.
    • archlinux: installs the current ParaView from the Arch Linux package repositories
    • archlinux-old: installs an older ParaView from the Arch Linux package archive
    • archlinux-full: installs a full ParaView from paraview.org
    • archlinux-headless-egl: installs headless ParaView 5.10 with EGL from paraview.org
    • archlinux-headless-egl-5.12: installs headless ParaView 5.12 with EGL from paraview.org
  • ubuntu-* branches use Ubuntu.
    • ubuntu: installs the current ParaView from the Ubuntu Jammy package repositories
    • ubuntu-headless-egl: installs headless ParaView 5.10 with EGL from paraview.org
    • archlinux-headless-egl-5.12: installs headless ParaView 5.12 with EGL from paraview.org

What I have noticed is:

  1. ParaView 5.10 (*-headless-egl) work on both Arch and Ubuntu. :white_check_mark:
  2. ParaView 5.11 (archlinux) from the Arch repos runs, but has the bug. :bug:
  3. ParaView 5.10 (ubuntu) from the Ubuntu repos crashes (Module not found.). :x:
  4. ParaView 5.10 (archlinux-full) from paraview.org works on Arch. :white_check_mark:
  5. ParaView 5.12 (archlinux-headless-egl-5.12) runs on Arch, but has the bug. :bug:
  6. ParaView 5.12 (ubuntu-headless-egl-5.12) works on Ubuntu. :white_check_mark: