Installing official Salome Meca on Windows 10/11 using WSL2

k_zurawski

Second call produces error

user@W1:/mnt/c/WINDOWS/system32$ export DISPLAY=

user@W1:/mnt/c/WINDOWS/system32$ echo "DISPLAY env. var is now set to : " $DISPLAY

DISPLAY env. var is now set to :

user@W1:/mnt/c/WINDOWS/system32$ singularity exec /opt/sm/salome*.sif glxinfo -B

Error: unable to open display

user@W1:/mnt/c/WINDOWS/system32$

I'm using two monitors, is it by any means significant?

hberro

Ok I advise you to completely remove WSL (check snapshot below) and reinstall it again.

Another user from the community had exactly the same issue which completely disappeared upon reinstalling WSL.

[color=blue]static1.makeuseofimages.com/wordpress/wp-content/uploads/2023/05/wsl-components.jpg[/color]

Let me know if that helps...

k_zurawski

Hi HB,

I wasn't sure if I have wsl up to date. So before reinstallation I shut down wsl and run update command. After that Salome_Meca GUI started. So it seems that it solved my problem. Thank you for the distro and help provided.

Commands used in PowerShell run as admin:

wsl --shutdown

wsl --update

That's it.

hberro

Great news, I will add your suggestion in the original post for troubleshooting.

MauroSogni

Hi, something strange happens to me:

- I installed everything without any problem

- I call Salome by typing salome_meca

- The software starts but it seems that it has been rendered in the wrong place, if you go on an Icon you cannot click on it until you move your mouse a little bit away of it (maybe on another icon)

Has anyone ncountered this issue?

Attached you can see the problem

Have a nice day

Mauro Sogni

EDIT:

I re-installed everythin, it works since I don't close Salome while in a full size windows, if I close it while in a full size windows the next time I open it I have the GUI issue

Does Salome have an option to let it starts in a floating window?

EDIT:

IF you succeed in maximize the window then the issue disappear.

Attached file:
Image.jpg, 337198kb

k_zurawski

I do have the same problem. The window has to be maximized or minimized. Floating window doesn't work really.

I'm also having sigsegv errors with paravis, the rest works just fine.

k_zurawski

I've been using the provided "vm" and in my case is unstable. I actually don't have to do anything else just change between Paravis and AsterStudy modules. Basically Salome-Meca crashes without any prior signs to that. This is a recurring problem and is related to paravis in some way. I attach information displayed in terminal.

What I did:

1. Started and created empty study

2. Shaper - created simple solid and two groups on faces

3. Meshed using linear hexahedra

4. Created linear study in AsterStudy and run it

5. I clicked on Paravis icon, loaded manually rmed file, saved the study

6. Went to AsterStudy, decreased value of Force_face, created new run and calculated it

7. Went to Paravis, reloaded file using those double arrows, used warp by vector, automatically changed warp value, changed scale to autmatically adapt to value set

8. Clicked on AsterStudy icon, clicked on Shaper icon and the software crashed.

Please check if you can replicate this problem. Please let me know if you are getting sigsegv error.

Attached file:
Error.txt, 11713kb

lucas62

Hello everyone,

For those who want to open salome_meca from a windows executable instead of opening wsl terminal, you can create a .bat file with the following line :

wsl -d smeca bash -c "/opt/sm/bin/salome_meca"

Then if you want a magnificent salome_meca.exe shortcut, you can then use bat2exe and feed it with the salome_meca logo and this bat file created earlier.

Finally, I have a tip to face MauroSogni's problem happening when the window isn't maximized.

Pressing F11 twice will maximize the window and solve the problem.

Hoping it will help,

Lucas

Frederic

k_zurawski wrote:
I've been using the provided "vm" and in my case is unstable. I actually don't have to do anything else just change between Paravis and AsterStudy modules. Basically Salome-Meca crashes without any prior signs to that. This is a recurring problem and is related to paravis in some way. I attach information displayed in terminal.

What I did:

1. Started and created empty study

2. Shaper - created simple solid and two groups on faces

3. Meshed using linear hexahedra

4. Created linear study in AsterStudy and run it

5. I clicked on Paravis icon, loaded manually rmed file, saved the study

6. Went to AsterStudy, decreased value of Force_face, created new run and calculated it

7. Went to Paravis, reloaded file using those double arrows, used warp by vector, automatically changed warp value, changed scale to autmatically adapt to value set

8. Clicked on AsterStudy icon, clicked on Shaper icon and the software crashed.

Please check if you can replicate this problem. Please let me know if you are getting sigsegv error.

I can't download your file. Am I the only one having this problem (I can download other attachments from the forum)? Can you resend it in another format or copy it into a message please?

k_zurawski

Frederic

Sorry for the delay. I didn't notice your response.

user@W2:/mnt/c/Users/KrzysztofZurawski$` salome_meca
[ INFO ] Singularity image : /opt/sm/bin/../salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif
[ INFO ] Binding C drive to /mnt/c
[ INFO ] Binding D drive to /mnt/d
[ INFO ] Binding F drive to /mnt/f
[ INFO ] Binding G drive to /mnt/g
glxinfo -B output --------------------------------------------
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 6.0, 256 bits) (0xffffffff)
Version: 18.2.8
Accelerated: no
Video memory: 15840MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.8
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.1 Mesa 18.2.8
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

runSalome running on W2
Searching for a free port for naming service: 2810 - OK
Searching Naming Service + found in 0.1 seconds
Searching /Kernel/Session in Naming Service ++++++++ found in 4.0 seconds
Start SALOME, elapsed time : 4.3 seconds

Warning: module HexoticPLUGIN is improperly configured!
Module HexoticPLUGIN will not be available in GUI mode!

Warning: module GHS3DPLUGIN is improperly configured!
Module GHS3DPLUGIN will not be available in GUI mode!

Warning: module GHS3DPRLPLUGIN is improperly configured!
Module GHS3DPRLPLUGIN will not be available in GUI mode!

Warning: module BLSURFPLUGIN is improperly configured!
Module BLSURFPLUGIN will not be available in GUI mode!

Warning: module NETGENPLUGIN is improperly configured!
Module NETGENPLUGIN will not be available in GUI mode!

Warning: module HYBRIDPLUGIN is improperly configured!
Module HYBRIDPLUGIN will not be available in GUI mode!

Warning: module GMSHPLUGIN is improperly configured!
Module GMSHPLUGIN will not be available in GUI mode!

AsterStudy: dim.-29-20:02:24.318 AsterStudy is activating...
AsterStudy: dim.-29-20:02:24.318 Creating workspace...
AsterStudy: dim.-29-20:02:24.333 Refreshing configuration on localhost...
AsterStudy: dim.-29-20:02:24.861 workspace is ready.
AsterStudy: dim.-29-20:02:29.524 AsterStudy activated
AsterStudy: dim.-29-20:08:53.998 saving case 1-CurrentCase...
AsterStudy: dim.-29-20:09:07.446 saving case 28-RunCase_1...
AsterStudy: dim.-29-20:09:07.447 saving case 1-CurrentCase...
AsterStudy: dim.-29-20:09:07.745 Submitting job on localhost...
AsterStudy: dim.-29-20:09:07.811 job submitted
AsterStudy: dim.-29-20:09:07.812 Asking the server for the job state...
AsterStudy: dim.-29-20:09:07.813 Job 0: status is RUNNING: Running
AsterStudy: dim.-29-20:09:07.814 Getting job output on W2...
AsterStudy: dim.-29-20:09:17.422 Asking the server for the job state...
AsterStudy: dim.-29-20:09:17.424 Job 0: status is FINISHED: Success
AsterStudy: dim.-29-20:09:23.526 saving case 28-RunCase_1...
AsterStudy: dim.-29-20:09:23.528 saving case 1-CurrentCase...

Loguru caught a signal: SIGSEGV
Stack trace:
85 0x55ae8a00809a _start + 42
84 0x7f9f00a022e1 __libc_start_main + 241
83 0x55ae8a00a9ea int AbstractGUIAppMain<GUIAppOldStyle>(int, char) + 4410
82 0x7f9f116cd843 QCoreApplication::exec() + 131
81 0x7f9f116c47f2 QEventLoop::exec(QFlags<QEventLoop:😛rocessEventsFlag>) + 274
80 0x7f9f1172248c QEventDispatcherGlib::processEvents(QFlags<QEventLoop:😛rocessEventsFlag>) + 92
79 0x7f9ef765fbcc g_main_context_iteration + 44
78 0x7f9ef765fb20 /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ab20) [0x7f9ef765fb20]
77 0x7f9ef765f8b7 g_main_context_dispatch + 679
76 0x7f9ea86a0a5a /opt/qt/5.15.2/lib/libQt5XcbQpa.so.5(+0x62a5a) [0x7f9ea86a0a5a]
75 0x7f9f11d18e5b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop:😛rocessEventsFlag>) + 187
74 0x7f9f11d3ce35 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent) + 261
73 0x7f9f11d3bcf3 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent) + 2403
72 0x7f9f116c5e38 QCoreApplication::notifyInternal2(QObject, QEvent) + 264
71 0x55ae8a0089cd SALOME_Session_Server(+0x89cd) [0x55ae8a0089cd]
70 0x7f9f20bca1d6 SalomeApp_ExceptionHandler::handle(QObject, QEvent) + 54
69 0x7f9f20bca4c4 SalomeApp_ExceptionHandler::handleSignals(QObject, QEvent) + 132
68 0x7f9f1262ad97 QApplication::notify(QObject, QEvent) + 519
67 0x7f9f1262431c QApplicationPrivate::notify_helper(QObject, QEvent) + 156
66 0x7f9f1267f143 /opt/qt/5.15.2/lib/libQt5Widgets.so.5(+0x1b9143) [0x7f9f1267f143]
65 0x7f9f1267c477 /opt/qt/5.15.2/lib/libQt5Widgets.so.5(+0x1b6477) [0x7f9f1267c477]
64 0x7f9f1262a32a QApplicationPrivate::sendMouseEvent(QWidget, QMouseEvent, QWidget, QWidget, QWidget, QPointer<QWidget>&, bool, bool) + 506
63 0x7f9f116c5e38 QCoreApplication::notifyInternal2(QObject, QEvent) + 264
62 0x55ae8a0089cd SALOME_Session_Server(+0x89cd) [0x55ae8a0089cd]
61 0x7f9f20bca1d6 SalomeApp_ExceptionHandler::handle(QObject, QEvent) + 54
60 0x7f9f20bca4c4 SalomeApp_ExceptionHandler::handleSignals(QObject, QEvent) + 132
59 0x7f9f1262bcc4 QApplication::notify(QObject, QEvent) + 4404
58 0x7f9f1262431c QApplicationPrivate::notify_helper(QObject, QEvent) + 156
57 0x7f9f127f725c QToolButton::event(QEvent) + 108
56 0x7f9f12662b08 QWidget::event(QEvent) + 488
55 0x7f9f127f718a QToolButton::mouseReleaseEvent(QMouseEvent) + 10
54 0x7f9f12712465 QAbstractButton::mouseReleaseEvent(QMouseEvent) + 213
53 0x7f9f1271226d /opt/qt/5.15.2/lib/libQt5Widgets.so.5(+0x24c26d) [0x7f9f1271226d]
52 0x7f9f1262092e QAction::activate(QAction::ActionEvent) + 158
51 0x7f9f1261e4b2 QAction::triggered(bool) + 50
50 0x7f9f116ff29e /opt/qt/5.15.2/lib/libQt5Core.so.5(+0x2d729e) [0x7f9f116ff29e]
49 0x7f9f17759ff4 /opt/salome_meca/appli_V2022.1.0_scibian_univ/lib/salome/libqtx.so(+0x182ff4) [0x7f9f17759ff4]
48 0x7f9f1769ed8f QtxActionSet::onActionTriggered(bool) + 63
47 0x7f9f17759efe QtxActionSet::triggered(int) + 46
46 0x7f9f116ff29e /opt/qt/5.15.2/lib/libQt5Core.so.5(+0x2d729e) [0x7f9f116ff29e]
45 0x7f9f206f536b LightApp_ModuleAction::activate(int, bool) + 875
44 0x7f9f207240d2 LightApp_ModuleAction::moduleActivated(QString const&) + 34
43 0x7f9f116ff29e /opt/qt/5.15.2/lib/libQt5Core.so.5(+0x2d729e) [0x7f9f116ff29e]
42 0x7f9f20bf5b0d /opt/salome_meca/appli_V2022.1.0_scibian_univ/lib/salome/libSalomeAppImpl.so(+0x9db0d) [0x7f9f20bf5b0d]
41 0x7f9f20bada92 SalomeApp_Application::onModuleActivation(QString const&) + 34
40 0x7f9f206c5d16 LightApp_Application::onModuleActivation(QString const&) + 230
39 0x7f9f206c15f6 LightApp_Application::activateModule(QString const&) + 262
38 0x7f9f20240287 CAM_Application::activateModule(QString const&) + 183
37 0x7f9f206cb08e LightApp_Application::activateModule(CAM_Module) + 14
36 0x7f9f2023fe17 CAM_Application::activateModule(CAM_Module) + 87
35 0x7f9e56274951 SHAPERGUI::deactivateModule(SUIT_Study) + 1057
34 0x7f9e5626e7f5 SHAPERGUI::publishToStudy() + 149
33 0x7f9e4ab8e2a9 PartSet_Module::launchOperation(QString const&, bool const&) + 121
32 0x7f9e55c5a756 ModuleBase_IModule::launchOperation(QString const&, bool const&) + 582
31 0x7f9e55fb991f XGUI_ModuleConnector::processLaunchOperation(ModuleBase_Operation) + 31
30 0x7f9e55fc8c0a XGUI_OperationMgr::startOperation(ModuleBase_Operation*) + 394
29 0x7f9e55c6bf05 ModuleBase_OperationFeature::start() + 453
28 0x7f9e55c6b945 ModuleBase_OperationFeature::createFeature(bool) + 869
27 0x7f9e4b306d53 Model_Document::addFeature(std::string, bool) + 2275
26 0x7f9e7bc7355f SwigDirector_ModelAPI_Feature::execute() + 47
25 0x7f9f156e5b39 PyObject_CallMethod + 185
24 0x7f9f156e51a9 _PyObject_FastCallDict + 137
23 0x7f9f156e54ac _PyObject_Call_Prepend + 204
22 0x7f9f156e528e _PyObject_FastCallDict + 366
21 0x7f9f157aa8e7 _PyFunction_FastCallDict + 727
20 0x7f9f157a1920 /opt/python/3.6.5/lib/libpython3.6.so.1.0(+0x128920) [0x7f9f157a1920]
19 0x7f9f157a64fa _PyEval_EvalFrameDefault + 13770
18 0x7f9f157a26fd /opt/python/3.6.5/lib/libpython3.6.so.1.0(+0x1296fd) [0x7f9f157a26fd]
17 0x7f9f157a1920 /opt/python/3.6.5/lib/libpython3.6.so.1.0(+0x128920) [0x7f9f157a1920]
16 0x7f9f157a6481 _PyEval_EvalFrameDefault + 13649
15 0x7f9f1574583b /opt/python/3.6.5/lib/libpython3.6.so.1.0(+0xcc83b) [0x7f9f1574583b]
14 0x7f9f156e51a9 _PyObject_FastCallDict + 137
13 0x7f9f156e54ac _PyObject_Call_Prepend + 204
12 0x7f9f156e528e _PyObject_FastCallDict + 366
11 0x7f9f157aa8e7 _PyFunction_FastCallDict + 727
10 0x7f9f157a1920 /opt/python/3.6.5/lib/libpython3.6.so.1.0(+0x128920) [0x7f9f157a1920]
9 0x7f9f157a64fa _PyEval_EvalFrameDefault + 13770
8 0x7f9f157a27e5 /opt/python/3.6.5/lib/libpython3.6.so.1.0(+0x1297e5) [0x7f9f157a27e5]
7 0x7f9f1572f5a9 PyCFunction_FastCallDict + 569
6 0x7f9ed8220eb8 /opt/salome_meca/appli_V2022.1.0_scibian_univ/lib/salome/libSMESH_Swig.so(+0x17eb8) [0x7f9ed8220eb8]
5 0x7f9e7bd3c397 swig::SwigPyIteratorClosed_T<std::List_iterator<std::shared_ptr<ModelAPI_Feature> >, std::shared_ptr<ModelAPI_Feature>, swig::from_oper<std::shared_ptr<ModelAPI_Feature> > >::value() const + 119
4 0x7f9e7bc4f12f /opt/salome_meca/appli_V2022.1.0_scibian_univ/lib/python3.6/site-packages/salome/ModelAPI.so(+0x5312f) [0x7f9e7bc4f12f]
3 0x7f9e7bc4d11a /opt/salome_meca/appli_V2022.1.0_scibian_univ/lib/python3.6/site-packages/salome/_ModelAPI.so(+0x5111a) [0x7f9e7bc4d11a]
2 0x7f9f15732246 PyObject_SetAttr + 54
1 0x7f9f15776a2c PyUnicode_InternInPlace + 92
0 0x7f9f084f60e0 /lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0) [0x7f9f084f60e0]
( 865.734s) [paraview ] :0 FATL| Signal: SIGSEGV

lucas62

Frederic wrote:

I can't download your file. Am I the only one having this problem (I can download other attachments from the forum)?

Hi Frédéric, to answer your question you are not the only one, I also can't download the file Error.txt.

pbedenbaugh

Thank you - installs smoothly and passes tests shown in the YouTube example.

However, the help system opens firefox, and then firefox immediately crashes.

I tried a solution given in post "Index» Salome-Meca installation» [SOLVED] SALOME 2018 Online help", but it did not change the crash behavior.

Any suggestsions for activating the help system ?

Julien_L

pbedenbaugh
pbedenbaugh

Hello,
It is the same thing for me.
When I click on the Help Menu, a firefox window opens during one second and closes just after.

Firefox is there, as we can see on this path.
\wsl.localhost\smeca\home\user.mozilla\firefox

But I can't find a file "firefox.bin" in the folder \wsl.localhost\smeca\usr\bin
Can it be the explantation of these mozilla crashes ?

Thank you.

Conen

Hello everyone,

I am also facing problem with the download of the .tar. Can you please help me out @hberro?

Kind regards,
Philipp

Edit: Now it works - Thank you very much!

lIlIl

The Google Drive links provided in the first post are no longer available. The only distribution I could find was in your older post: https://code-aster.org/FICHIERS/wsl/smeca-lgpl-wsl2-opensuse.tar
In this version, the /opt folder is empty. Still, running salome_meca (a function defined in ~/.bashrc) in the same folder as the .sif container does open Salome Meca 2023. Unfortunately, it is not able to run any simulations. Here is the content of the message file:

ERROR: The user login on remote machine MUST be given.
++ using container salome_meca-lgpl-2023.1.0-4-20240327-scibian-10.sif
++ using software rendering mode (should use `mesa_salome` starter)

EDIT: it works with salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif. What steps can we take to use 2023?

My motivation to use Code_Aster in WSL (rather than Code_Aster Windows) is to use UMAT. Unfortunately the testcase umat002a.com2 has failed:

 ╔════════════════════════════════════════════════════════════════════════════════════════════════╗
 ║ <F> <FERMETUR_13>                                                                              ║
 ║                                                                                                ║
 ║ La bibliothèque UMAT n'a pas pu être chargée.                                                  ║
 ║                                                                                                ║
 ║ Nom de la bibliothèque : libumat1.so                                                           ║
 ║                                                                                                ║
 ║ Conseil : Vérifiez que l'environnement est correctement défini,                                ║
 ║           notamment la variable LD_LIBRARY_PATH.                                               ║
 ║                                                                                                ║
 ║                                                                                                ║
 ║ Cette erreur est fatale. Le code s'arrête.                                                     ║
 ╚════════════════════════════════════════════════════════════════════════════════════════════════╝

$LD_LIBRARY_PATH shows nothing.

EDIT: Hassan Berro gives a link for 2002 in the comments of his video
https://drive.usercontent.google.com/download?id=1n0IKKZjhwfVjLCkVNikhBvWjbeZGs8Cm&export=download

lIlIl

Is it possible to have the password for the user or root in the singularity container salome_meca-lgpl-2022.1.0-1-20221225-scibian-9?
I need it to run sudo commands and copy-paste the missing config.txt and profile.sh after installing the development version.

sudo: le uid effectif n'est pas 0. Est-ce que /usr/bin/sudo est sur un système de fichiers avec l'option « nosuid » ou un système de fichiers NFS sans privilèges root ?

> ls -l /usr/bin/sudo
-rwsr-xr-x 1 root root 140944 janv. 23  2021 /usr/bin/sudo
> groups
users singularity
> id
uid=1000(user) gid=100(users) groupes=100(users),479(singularity)

lIlIl

lIlIl To answer my own question: you can use the --fakeroot Singularity option.

$ singularity run --fakeroot ~/sm22/salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif shell
Converting SIF file to temporary sandbox...
Singularity> whoami
root
Singularity> groups
root
Singularity> id
uid=0(root) gid=0(root) groupes=0(root)

Andre Mello

Hi @hberro, any advice for using Salome 2023 with this image?
I can use it in your older openSuse image, but in this ubuntu image, it throws glxinfo -B output error, even though WSLg is installed in my machine.

k_zurawski

Could you explain briefly how --fakeroot works? Will I be able to change some python files inside the image and will the change be permanent?

lIlIl

It seems that all changes are temporary. It only simulates root privileges, it doesn't actually modify the underlying file system. This is part of what makes Singularity safer than Docker images.
https://docs.sylabs.io/guides/latest/user-guide/fakeroot.html

k_zurawski

lIlIl I was afraid of that because of the sandbox word in your post