Package: python3-paraview
Version: 5.10.1-2+b1
Followup-For: Bug #1010027
The bug is still present in 5.10.1-2+b1, and it affects both pvpython
and (arguably even worse) pvbatch. It seems that the command-line
options are never even read, even putting in a bogus file name like:
pvbatch nonexistent.py
(with no actual nonexistent.py file present) has no effect.
This is in contrast e.g. with 5.9.0 that (as expected) errored out with:
/usr/bin/../lib/x86_64-linux-gnu/vtkpython: can't open file
'/xxxx/xxxxx/nonexistent.py': [Errno 2] No such file or directory
One thing of note is that in the working 5.9 installation, pvpython ends
up delegating to vtkpython. Running strace on the broken 5.10 reveals
pvpython trying to access vtkpython and failing
readlink("/usr/bin/../lib/x86_64-linux-gnu/vtkpython", 0x7fffe0794790,
4096) = -1 ENOENT (No such file or directory)
and then falling back to the standard python interpreter. I suspect this
may be related to the issue.
-- System Information:
Debian Release: bookworm/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 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-paraview depends on:
ii libc6 2.33-8
ii libgcc-s1 12.1.0-7
ii libpython3.10 3.10.5-1
ii libstdc++6 12.1.0-7
ii paraview 5.10.1-2+b1
ii python3 3.10.5-3
python3-paraview recommends no packages.
python3-paraview suggests no packages.
-- no debconf information
