When importing any of the VTK Python bindings, an immediate segmentation fault occurs. Reproducible: Always Steps to Reproduce: $ mock -r fedora-rawhide-x86_64 --clean $ mock -r fedora-rawhide-x86_64 -i 'python3dist(vtk)' $ mock -r fedora-rawhide-x86_64 --shell <mock-chroot> sh-5.2# python3 >>> from vtkmodules.vtkCommonCore import vtkVersion Segmentation fault (core dumped) Actual Results: Segmentation fault (core dumped) Expected Results: Successful import; and then, calling vtkVersion() should work and should return something reasonable, e.g.: >>> v = vtkVersion() >>> v.GetVTKMajorVersion() 9 In addition to Rawhide/F42, I can also reproduce this in Fedora 41. Fedora 40 seems to be OK.
I’m not certain that this is a Python 3.13 issue, but it seems likely since it appears starting in Fedora 41, and there have been no major packaging changes in vtk itself since Fedora 40. I’m therefore blocking the Python 3.13 tracker bug.
FEDORA-2024-b0d61199f3 (vtk-9.2.6-18.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b0d61199f3
FEDORA-2024-b0d61199f3 (vtk-9.2.6-18.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-286c09b59e (Mayavi-4.8.2-3.fc41 and vtk-9.2.6-18.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-286c09b59e
FEDORA-2024-286c09b59e has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-286c09b59e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-286c09b59e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-286c09b59e (Mayavi-4.8.2-3.fc41 and vtk-9.2.6-18.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.