SIGABRT and paraview does not start

ParaView Support
1

I installed Paraview via the package manager pacman on Artixlinux (A derivative of Archlinux).
However, I’m unable to start paraview on my machine. I also tested, a month or so ago, the binary provided by the paraview website, but that also led to the same result.

Here is the log for when I issue the command paraview in the terminal:

Loguru caught a signal: SIGABRT
Stack trace:
39      0x56440e6e188e paraview(+0x788e) [0x56440e6e188e]
38      0x7f2e80514b25 __libc_start_main + 213
37      0x56440e6e1564 paraview(+0x7564) [0x56440e6e1564]
36      0x56440e6e6985 paraview(+0xc985) [0x56440e6e6985]
35      0x56440e6e2775 paraview(+0x8775) [0x56440e6e2775]
34      0x7f2e803952aa pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1114
33      0x7f2e8030689c pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 332
32      0x7f2e7f64ed1a pqObjectBuilder::createServer(pqServerResource const&, int) + 410
31      0x7f2e7e699ac6 vtkSMSession::ConnectToSelf(int) + 134
30      0x7f2e7de4ec85 vtkProcessModule::RegisterSession(vtkSession*) + 149
29      0x7f2e7bdbfed2 /usr/lib/libvtkCommonCore.so.1(+0x42aed2) [0x7f2e7bdbfed2]
28      0x7f2e7bc1e869 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
27      0x7f2e7e79a2ae /usr/lib/libvtkGUISupportQt.so.1(+0x262ae) [0x7f2e7e79a2ae]
26      0x7f2e7eb4e90b /usr/lib/libQt5Core.so.5(+0x2fa90b) [0x7f2e7eb4e90b]
25      0x7f2e7f5e1923 pqServerManagerObserver::connectionCreated(long long) + 67
24      0x7f2e7eb4e90b /usr/lib/libQt5Core.so.5(+0x2fa90b) [0x7f2e7eb4e90b]
23      0x7f2e7f69d57d pqServerManagerModel::onConnectionCreated(long long) + 893
22      0x7f2e7f5de483 pqServerManagerModel::serverAdded(pqServer*) + 67
21      0x7f2e7eb4e90b /usr/lib/libQt5Core.so.5(+0x2fa90b) [0x7f2e7eb4e90b]
20      0x7f2e8035c670 pqDefaultViewBehavior::onServerCreation(pqServer*) + 688
19      0x7f2e7f64abab pqObjectBuilder::createView(QString const&, pqServer*) + 187
18      0x7f2e7e6a81b7 vtkSMSessionProxyManager::NewProxy(char const*, char const*, char const*) + 183
17      0x7f2e7e6a7dc0 vtkSMSessionProxyManager::NewProxy(vtkPVXMLElement*, char const*, char const*, char const*) + 736
16      0x7f2e79cc8f5a vtkSMViewProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 26
15      0x7f2e7e66f1f9 vtkSMProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 1673
14      0x7f2e7e671753 vtkSMProxy::CreateSubProxiesAndProperties(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 451
13      0x7f2e7e66e469 vtkSMProxy::NewProperty(char const*, vtkPVXMLElement*) + 617
12      0x7f2e7e6dc010 vtkSMStringVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 48
11      0x7f2e7e6e6bea vtkSMVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 42
10      0x7f2e7e6584ff vtkSMProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 5071
9       0x7f2e79c8d83d vtkSMRendererDomain::ReadXMLAttributes(vtkSMProperty*, vtkPVXMLElement*) + 29
8       0x7f2e79c8d4bc vtkSMRendererDomain::Update(vtkSMProperty*) + 60
7       0x7f2e76e4dee9 vtkOSPRayPass::IsBackendAvailable(char const*) + 89
6       0x7f2e76e2eb82 /usr/lib64/libvtkRenderingRayTracing.so.1(+0x1eb82) [0x7f2e76e2eb82]
5       0x7f2e709a6c96 ospInit + 1766
4       0x7f2e3cb0964b ospray::api::ISPCDevice::commit() + 427
3       0x7f2e3cb7ffe0 ISPCDevice_programCount + 64
2       0x7f2e80513862 abort + 278
1       0x7f2e80529ef5 gsignal + 325
0       0x7f2e80529f80 /usr/lib/libc.so.6(+0x3cf80) [0x7f2e80529f80]
(   4.904s) [paraview        ]                       :0     FATL| Signal: SIGABRT
[1]    17287 IOT instruction  paraview

Here is the ouput of paraview --mesa:

Loguru caught a signal: SIGABRT
Stack trace:
39      0x55b93c9b888e paraview(+0x788e) [0x55b93c9b888e]
38      0x7f81a64f4b25 __libc_start_main + 213
37      0x55b93c9b8564 paraview(+0x7564) [0x55b93c9b8564]
36      0x55b93c9bd985 paraview(+0xc985) [0x55b93c9bd985]
35      0x55b93c9b9775 paraview(+0x8775) [0x55b93c9b9775]
34      0x7f81a63752aa pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1114
33      0x7f81a62e689c pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 332
32      0x7f81a562ed1a pqObjectBuilder::createServer(pqServerResource const&, int) + 410
31      0x7f81a4679ac6 vtkSMSession::ConnectToSelf(int) + 134
30      0x7f81a3e2ec85 vtkProcessModule::RegisterSession(vtkSession*) + 149
29      0x7f81a1d9fed2 /usr/lib/libvtkCommonCore.so.1(+0x42aed2) [0x7f81a1d9fed2]
28      0x7f81a1bfe869 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
27      0x7f81a477a2ae /usr/lib/libvtkGUISupportQt.so.1(+0x262ae) [0x7f81a477a2ae]
26      0x7f81a4b2e90b /usr/lib/libQt5Core.so.5(+0x2fa90b) [0x7f81a4b2e90b]
25      0x7f81a55c1923 pqServerManagerObserver::connectionCreated(long long) + 67
24      0x7f81a4b2e90b /usr/lib/libQt5Core.so.5(+0x2fa90b) [0x7f81a4b2e90b]
23      0x7f81a567d57d pqServerManagerModel::onConnectionCreated(long long) + 893
22      0x7f81a55be483 pqServerManagerModel::serverAdded(pqServer*) + 67
21      0x7f81a4b2e90b /usr/lib/libQt5Core.so.5(+0x2fa90b) [0x7f81a4b2e90b]
20      0x7f81a633c670 pqDefaultViewBehavior::onServerCreation(pqServer*) + 688
19      0x7f81a562abab pqObjectBuilder::createView(QString const&, pqServer*) + 187
18      0x7f81a46881b7 vtkSMSessionProxyManager::NewProxy(char const*, char const*, char const*) + 183
17      0x7f81a4687dc0 vtkSMSessionProxyManager::NewProxy(vtkPVXMLElement*, char const*, char const*, char const*) + 736
16      0x7f819fca8f5a vtkSMViewProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 26
15      0x7f81a464f1f9 vtkSMProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 1673
14      0x7f81a4651753 vtkSMProxy::CreateSubProxiesAndProperties(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 451
13      0x7f81a464e469 vtkSMProxy::NewProperty(char const*, vtkPVXMLElement*) + 617
12      0x7f81a46bc010 vtkSMStringVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 48
11      0x7f81a46c6bea vtkSMVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 42
10      0x7f81a46384ff vtkSMProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 5071
9       0x7f819fc6d83d vtkSMRendererDomain::ReadXMLAttributes(vtkSMProperty*, vtkPVXMLElement*) + 29
8       0x7f819fc6d4bc vtkSMRendererDomain::Update(vtkSMProperty*) + 60
7       0x7f819ce2dee9 vtkOSPRayPass::IsBackendAvailable(char const*) + 89
6       0x7f819ce0eb82 /usr/lib64/libvtkRenderingRayTracing.so.1(+0x1eb82) [0x7f819ce0eb82]
5       0x7f8196986c96 ospInit + 1766
4       0x7f816c61964b ospray::api::ISPCDevice::commit() + 427
3       0x7f816c68ffe0 ISPCDevice_programCount + 64
2       0x7f81a64f3862 abort + 278
1       0x7f81a6509ef5 gsignal + 325
0       0x7f81a6509f80 /usr/lib/libc.so.6(+0x3cf80) [0x7f81a6509f80]
(   1.391s) [paraview        ]                       :0     FATL| Signal: SIGABRT
[1]    17780 IOT instruction  paraview --mesa

the output of glxinfo | grep Vendor:

Vendor: nouveau (0x10de)

and finally, uname -a:

Linux guts 5.10.78-1-lts #1 SMP Thu, 11 Nov 2021 21:24:30 +0000 x86_64 GNU/Linux
2
  • Try with --dr
  • make sure you do not have anything related to QT in your env var
  • If all else fails, build ParaView yourself and run in debug.
3

Sorry for late response.

I tried the --dr flag but no help. BTW, this flag was not in the Paraview help.
I guess you meant -dr (that didn’t work too). I check my env and there wasn’t any instance of the string “QT” in them. I’m not sure what could be related to QT…

I will build it and tell you the result.

Thanks for the guide!

4

I built Paraview and it worked!

I had to define -DVTK_QT_VERSION:STRING=5 macro from the command line to tell CMake to consider QT of version 5. I don’t know why I have two versions of QT!

Thanks again!

5

FYI @Sankhesh_Jhaveri @cory.quammen : this may be problematic

6

What hardware are you running? x86_64? arm64?

7

My changes from

https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8683
https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5361

should fix these issues.

@jupyter Mind giving it a try?

8

As I stated in my question, x86_64. It’s an ancient hardware with Pentium E5300 (2) @ 2.600GHz CPU and NVIDIA GeForce 9500 GT GPU.

9

Not at all. But I need some time, like a week, ⁣:smile: to build it. My hardware is an ancient one.

10

Oh, I think I only need to check if the CMake thingy works fine. I removed the QT6 on my system. I will reinstall it and tell you the result.

11

Knowing that I cloned the repository via: git clone --recursive https://gitlab.kitware.com/paraview/paraview.git
I pulled the changes with the git pull --recurse-submodules command. Then, I ran the following CMake command:
cmake -GNinja -DPARAVIEW_USE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB -DCMAKE_BUILD_TYPE=Release ../paraview, and it finished without any error, except this warning:

CMake Warning (dev) at /usr/share/cmake-3.22/Modules/CMakeDependentOption.cmake:84 (message):
  Policy CMP0127 is not set: cmake_dependent_option() supports full Condition
  Syntax.  Run "cmake --help-policy CMP0127" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.
Call Stack (most recent call first):
  VTK/Common/Core/CMakeLists.txt:19 (cmake_dependent_option)
This warning is for project developers.  Use -Wno-dev to suppress it.

I hope I didn’t mess the pulling changes (I checked the git log and your commits were there, though). If I did something wrong, let me know.

Thanks for the update!

12

Thanks for testing @jupyter. You can safely ignore that warning. Glad to know that the issue is resolved.