[xisluke]

Hi guys, I'm trying to install OpenFOAM 10 on Ubuntu 22.04 LTS, I'm running Linux on the WSL2, Windows 10.
I followed the exact instructions enlighted at the official link from The OpenFOAM Foundation (https://openfoam.org/download/windows/). Everything is fine until the enabling of graphical application; as I stated before, I followed exactly the same procedure by installing VcXsrv, but if I try to run gedit or paraFoam, basically nothing is working. XLaunch is running in the background but the only thing I see is the pointer blinking on the terminal without any window opening. I already used OpenFOAM few times ago with WSL1 but I didn't experienced this issue.
The .bashrc file has these two strings at the end:

. /opt/openfoam10/etc/bashrc
export DISPLAY=<IP ADDRESS>:0

Some suggestions? I tried to search out on the web but I really didn't find something that really helped me, I am not used to work with Linux nor WSL.
Thanks!

[olesen]

Related topics:

• https://develop.openfoam.com/Develop...raview-plugins
• https://discourse.paraview.org/t/i-w...n-should-i-use

You are better to use a Windows installation of ParaView.

[xisluke]

Ok, let's say to install ParaView directly on Windows and solving the problem. How can I manage the issue with gedit?

[alexvaleije]

Originally Posted by xisluke

Ok, let's say to install ParaView directly on Windows and solving the problem. How can I manage the issue with gedit?

Hi Luca,

I do not get the question. Install paraview in Windows, and in the case folder generate a blank file with a ".openfoam" termination. For example, "case.openfoam".

Then, open that file with paraView and when it asks for the reader type, select OpenFoam Reader, and then your case will be loaded.

Much easier and better display than depending on the parafoam command and X acceleration

Hope that helps. Best regards,

[Yann]

Originally Posted by xisluke

Ok, let's say to install ParaView directly on Windows and solving the problem. How can I manage the issue with gedit?

You can directly access your files from windows explorer and edit it using something like notepad++ or any other editor you like to use.

Originally Posted by alexvaleije

Install paraview in Windows, and in the case folder generate a blank file with a ".openfoam" termination. For example, "case.openfoam".

Then, open that file with paraView and when it asks for the reader type, select OpenFoam Reader, and then your case will be loaded.

I would even say: create a blank file with the ".foam" extension rather than ".openfoam". It will be recognized by ParaView who will automatically use the OpenFOAM reader. (so you skip the part where you have to manually select the OpenFOAM reader in paraview when opening the case)

Cheers,
Yann

[xisluke]

Thank you guys, as I mentioned before I used OpenFOAM few times ago mainly at the university, professors told us to go with X Server and since I did not experienced any issues my intention was to go in the exact same way.

You can directly access your files from windows explorer and edit it using something like notepad++ or any other editor you like to use.

I would say that at that time I tried to modify directly in Windows some scripts, but I often got problems in the readability of the files in WSL, I do not remember the reason but the only way was gedit... It is also true that I was using Windows Notepad, not a more advanced editor like Notepad++ or Sublime Text

[alexvaleije]

Without further information, I would say that those problems might have been caused by the carriage return that Windows Notepad does.

With Notepad++, or using nano in the terminal you should be safe. I know some people that likes vim, but I hate it so much hahaha

@Yann Nice trick the .foam instead .openfoam extension, I hadn't noticed so far

Originally Posted by xisluke

Thank you guys, as I mentioned before I used OpenFOAM few times ago mainly at the university, professors told us to go with X Server and since I did not experienced any issues my intention was to go in the exact same way.



I would say that at that time I tried to modify directly in Windows some scripts, but I often got problems in the readability of the files in WSL, I do not remember the reason but the only way was gedit... It is also true that I was using Windows Notepad, not a more advanced editor like Notepad++ or Sublime Text

[Yann]

Originally Posted by alexvaleije

Without further information, I would say that those problems might have been caused by the carriage return that Windows Notepad does.

With Notepad++, or using nano in the terminal you should be safe. I know some people that likes vim, but I hate it so much hahaha

@Yann Nice trick the .foam instead .openfoam extension, I hadn't noticed so far

I agree with that. In notepad++ you can convert End Of Line characters to maintain the Linux format when editing the file from windows.
I've been doing this on a daily basis for years, no issues with it, as long as you remember to check it and convert from Windows to Linux if needed.

Notepad++ maintain the original format of the file so if you open OpenFOAM files with it it will be fine. You just need to be careful when creating a new file from windows.

Cheers,
Yann