Error blockMesh Loguru caught a signal: SIGSEGV

ParaView Support
1

After running the blockMesh of a tutorial of openFoam it showed this error:
Created temporary ‘pitzDailySteady.OpenFOAM’

Loguru caught a signal: SIGSEGV
Stack trace:
0 0x7974fdc45330 /usr/lib/x86_64-linux-gnu/libc.so.6(+0x45330) [0x7974fdc45330]
( 0.685s) [paraview ] :0 FATL| Signal: SIGSEGV
Segmentation fault (core dumped)

I’m new to the software so I have no idea what to do

2

please share your entire folder containing the open foam data.

3

blockMeshDict (2.6 KB)
controlDict (1.0 KB)
functions (830 Bytes)
fvSchemes (1.3 KB)
fvSolution (1.5 KB)

4

momentumTransport (939 Bytes)
physicalProperties (732 Bytes)

5

Please create an archive instead of sharing individual files.

6

pitzDailySteady.zip (1.8 MB)
Sorry, here you have it compressed

7

I’m using ubuntu from a windows computer and the problem shows when I try to open ParaView writing the command paraFoam

8

Then use ParaView instead.

9

Using ParaView this happened:
ParaView: command not found

Using paraView this happened:
Command ‘paraView’ not found, did you mean:
command ‘paraview’ from deb paraview (5.11.2+dfsg-4)
Try: sudo apt install

Using paraview this happened:
QStandardPaths: wrong permissions on runtime directory /run/user/1000/, 0755 instead of 0700

Loguru caught a signal: SIGSEGV
Stack trace:
0 0x7652ac645330 /usr/lib/x86_64-linux-gnu/libc.so.6(+0x45330) [0x7652ac645330]
( 4.196s) [paraview ] :0 FATL| Signal: SIGSEGV
Segmentation fault (core dumped)

10

Use the binary release from https://paraview.org/download

11

Which one is it? I downloaded this version
ParaView-6.0.0-RC1-Windows-Python3.12-msvc2017-AMD64.msi

12

If you want to install for Windows, yes.

13

I already have that one, what are you suggesting?

14

I’m suggesting to use that version to open the OpenFOAM folder you shared.

15

First, Is there a way to open ParaView directly from the terminal?
Second, is there a way to see the mesh only, before solving, in paraview?

16

I supose that if ParaView bin directory is in your path, you should be able to open it from a Windows terminal.

Second, is there a way to see the mesh only, before solving, in paraview?

Not directly, but maybe OpenFOAM can generate a .vtk file or something.

17

Usually this error occurs when the GUI is not properly configured with the WSL. Hence you won’t be able to use any GUI applications from WSL.
If you have it installed, try using ‘gedit’. You’ll probably get the same error.

I too had the same issue. I resolved it somehow though I don’t remember it now.
I’ll try to look it up.

One workaround that I used for paraview is adding paraview.exe path to bashrc with alias as paraview513 (I had paraview v5.13).
And use paraview513 command to open it from terminal.

18

It seems that your installation of OpenFOAM is not done correctly.

If you are using WSL, I would suggest you use the command “explorer.exe .”, which will open the folder containing your *.foam file and you can simply load it and view in ParaView.