# Error blockMesh Loguru caught a signal: SIGSEGV
**URL:** https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858
**Category:** ParaView Support
**Created:** [June 24, 2025, 5:32pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858 "2025-06-24T17:32:27Z")
**Posts on this page:** 18
**Page:** 1
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 24, 2025, 5:32pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/1 "2025-06-24T17:32:28Z")
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
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 7:25am UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/2 "2025-06-25T07:25:56Z")
please share your entire folder containing the open foam data.
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 5:56pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/3 "2025-06-25T17:56:03Z")
[blockMeshDict](https://discourse.paraview.org/uploads/short-url/rgfM9j19SEwPyVAlNY4ZkLpAIz3) (2.6 KB)
[controlDict](https://discourse.paraview.org/uploads/short-url/yfEZEO12hUjfY8L6pT25YrUgmXU) (1.0 KB)
[functions](https://discourse.paraview.org/uploads/short-url/cbTB1vEdx7J2seQLAZvaCGyYY1N) (830 Bytes)
[fvSchemes](https://discourse.paraview.org/uploads/short-url/pr83oTW9d1bbatLAPfBNKZrn71E) (1.3 KB)
[fvSolution](https://discourse.paraview.org/uploads/short-url/icTWFhTf45gmAVwCOBYgJj8G8qz) (1.5 KB)
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 5:56pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/4 "2025-06-25T17:56:27Z")
[momentumTransport](https://discourse.paraview.org/uploads/short-url/svqMJVrZC0NxhfDAQiM6Dn9rgKQ) (939 Bytes)
[physicalProperties](https://discourse.paraview.org/uploads/short-url/stOKGO1omlPLnqhnyMh2JqvFkJu) (732 Bytes)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 6:43pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/5 "2025-06-25T18:43:37Z")
Please create an archive instead of sharing individual files.
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 6:59pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/6 "2025-06-25T18:59:19Z")
[pitzDailySteady.zip](https://discourse.paraview.org/uploads/short-url/eBKOQOdxyQY8TUdZA4lc1liZBRf.zip) (1.8 MB)
Sorry, here you have it compressed
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 7:04pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/7 "2025-06-25T19:04:15Z")
I’m using ubuntu from a windows computer and the problem shows when I try to open ParaView writing the command paraFoam
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 7:08pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/8 "2025-06-25T19:08:23Z")
> [@pedro1](#):
>
> paraFoam
Then use ParaView instead.
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 7:17pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/9 "2025-06-25T19:17:43Z")
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)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 7:19pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/10 "2025-06-25T19:19:21Z")
Use the binary release from [https://paraview.org/download](https://paraview.org/download)
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 7:21pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/11 "2025-06-25T19:21:36Z")
Which one is it? I downloaded this version [
ParaView-6.0.0-RC1-Windows-Python3.12-msvc2017-AMD64.msi
](https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v6.0&type=binary&os=Windows&downloadFile=ParaView-6.0.0-RC1-Windows-Python3.12-msvc2017-AMD64.msi)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 7:23pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/12 "2025-06-25T19:23:09Z")
If you want to install for Windows, yes.
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 7:25pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/13 "2025-06-25T19:25:08Z")
I already have that one, what are you suggesting?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 7:26pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/14 "2025-06-25T19:26:28Z")
I’m suggesting to use that version to open the OpenFOAM folder you shared.
---
### Author:  [@pedro1](https://discourse.paraview.org/u/pedro1)
#### Post date: [June 25, 2025, 8:20pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/15 "2025-06-25T20:20:05Z")
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?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 25, 2025, 8:22pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/16 "2025-06-25T20:22:05Z")
> [@pedro1](#):
>
> First, Is there a way to open ParaView directly from the terminal?
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.
---
### Author:  [@nux-foam](https://discourse.paraview.org/u/nux-foam)
#### Post date: [June 26, 2025, 2:45am UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/17 "2025-06-26T02:45:10Z")
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.
---
### Author:  [@Bortus](https://discourse.paraview.org/u/Bortus)
#### Post date: [July 1, 2025, 5:49pm UTC](https://discourse.paraview.org/t/error-blockmesh-loguru-caught-a-signal-sigsegv/16858/18 "2025-07-01T17:49:16Z")
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.