Bug#1065270: Unable to open VTK file with appended data that were fine with previous versions (invalid token in vtkXMLDataParser)

[Giuseppe Bilotta]

Package: paraview
Version: 5.11.2+dfsg-6+b1
Severity: important

Per the title, after a recent upgrade opening any data file with
appended data in 'raw' format, which was possible before the update,
fails with errors like:

vtkXMLDataParser (0x56138248c210): Error parsing XML in stream at line 27, column 1, byte index 1348: not well-formed (invalid token)

This may be an issue with the system expat library, at least according
to the thread
https://discourse.paraview.org/t/i-cannot-read-a-vtp-file-i-could-open-yesterday-can-someone-try-to-open-it/13938
where the same issue is being discussed for an Arch installation.

As reported there, downgrading libexpat1 to 2.5.0-2+b2 seems to fix the
issue, so it's either an issue in expat or in the way ParaView is using
it (maybe some changed default about the strictness off the parsing?).

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages paraview depends on:
ii  libadios2-mpi-c++11-2  2.9.2+dfsg1-13
ii  libavcodec60           10:6.1.1-dmo1
ii  libavformat60          10:6.1.1-dmo1
ii  libavutil58            10:6.1.1-dmo1
ii  libc6                  2.37-15
ii  libdouble-conversion3  3.3.0-1+b1
ii  libexpat1              2.6.0-1
ii  libfreetype6           2.13.2+dfsg-1+b1
ii  libgcc-s1              14-20240201-3
ii  libgdal34              3.8.4+dfsg-1
ii  libgl2ps1.4            1.4.2+dfsg1-2
ii  libglew2.2             2.2.0-4+b1
ii  libglx0                1.7.0-1
ii  libgmsh4.12            4.12.1+ds1-1
ii  libhdf5-openmpi-103-1  1.10.10+repack-3+b1
ii  libjpeg62-turbo        1:2.1.5-2+b2
ii  liblz4-1               1.9.4-1+b2
ii  liblzma5               5.4.5-0.3
ii  libnetcdf19            1:4.9.2-3+b1
ii  libogg0                1.3.5-3
ii  libopengl0             1.7.0-1
ii  libopenmpi3            4.1.6-5
ii  libpng16-16            1.6.42-1
ii  libpython3.11          3.11.8-1
ii  libpython3.12          3.12.2-1
ii  libqt5core5a           5.15.10+dfsg-7
ii  libqt5gui5             5.15.10+dfsg-7
ii  libqt5help5            5.15.10-6
ii  libqt5network5         5.15.10+dfsg-7
ii  libqt5opengl5          5.15.10+dfsg-7
ii  libqt5widgets5         5.15.10+dfsg-7
ii  libstdc++6             14-20240201-3
ii  libswscale7            10:6.1.1-dmo1
ii  libtheora0             1.1.1+dfsg.1-16.1+b1
ii  libtiff6               4.5.1+git230720-4
ii  libx11-6               2:1.8.7-1
ii  libxcursor1            1:1.2.1-1
ii  libxml2                2.9.14+dfsg-1.3+b2
ii  python3-matplotlib     3.6.3-1+b2
ii  python3-mpi4py         3.1.5-5
ii  tcl [tclsh]            8.6.13+b1
ii  zlib1g                 1:1.3.dfsg-3+b1

Versions of packages paraview recommends:
ii  mpi-default-bin   1.15
ii  paraview-doc      5.11.2+dfsg-6
ii  python3-paraview  5.11.2+dfsg-6+b1

Versions of packages paraview suggests:
pn  h5utils     <none>
ii  hdf5-tools  1.10.10+repack-3+b1

-- no debconf information