Hello Ryo IGARASHI, I just trying to triage this bug, and have in a minimal Buster amd64 VM installed just paraview installed and could not reproduce the issue.
Could you please check the output in your system for any differences to the outputs below: dpkg -l | grep -E "paraview|libqt5core5a" md5sum /usr/lib/x86_64-linux-gnu/libQt5Core.so.5* /usr/lib/paraview/paraview env | grep -E "^LD" If they are equal, maybe the output of following call could give a hint? LD_DEBUG=libs ldd /usr/lib/paraview/paraview LD_DEBUG=files ldd /usr/lib/paraview/paraview Kind regards, Bernahrd PS.: I received following in my VM: root@debian:~# dpkg -l | grep -E "paraview|libqt5core5a" ii libqt5core5a:amd64 5.11.3+dfsg1-1 amd64 Qt 5 core module ii paraview 5.4.1+dfsg4-3.1+b2 amd64 Parallel Visualization Application ii paraview-doc 5.4.1+dfsg4-3.1 all Parallel Visualization Application. Comprehensive documentation ii paraview-python 5.4.1+dfsg4-3.1+b2 amd64 Parallel Visualization Application. python-support root@debian:~# md5sum /usr/lib/x86_64-linux-gnu/libQt5Core.so.5* /usr/lib/paraview/paraview 4acffc4ba6ef46508773294c59849734 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 4acffc4ba6ef46508773294c59849734 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.11 4acffc4ba6ef46508773294c59849734 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.11.3 bd7619e0e0a906543e62ec737aa7ba10 /usr/lib/paraview/paraview root@debian:~# env | grep -E "^LD" root@debian:~#