Issues running Salome 9.12 on Debian 12

Install & build
1

Hi everyone,
I am experiencing some problems in running the SALOME binaries on a Debian 12 operating system. The binaries are the ones downloaded with the
SALOME-9.12.0-native-DB12-SRC-423b7a9fc437fd1622d64f1db54468d8.tar.gz
file.
When I run the ./salome command from the SALOME-9.12.0-native-DB12-SRC folder, the gui runs fine until I try to open the geometry or shaper or mesh module (these are the ones I tried, I don’t know about others). As soon as I push on the icon of one of these modules, everything crashes and I get this message on the terminal

X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 3 (X_GetWindowAttributes)
Resource id in failed request: 0xe
Serial number of failed request: 10
Current serial number in output stream: 11

My system check (I report it at the end of the present message) does not indicate that some required libraries are missing.
Has anyone ever encountered a similar problem?
Thanks for the help.

         Andrea

P.S.: the result of my system check is
sat/sat config SALOME-9.12.0-native --check_system

Check the system dependencies declared in the application

  • python3-babel : OK
  • python3-pytest-cython : OK
  • python3-jinja2 : OK
  • python3-pil : OK
  • python3-pyqt5 : OK
  • pyqt5-dev : OK
  • pyqt5-dev-tools : OK
  • python3-pygments : OK
  • python3-sphinx : OK
  • python3-alabaster : OK
  • libboost-all-dev : OK
  • python3-certifi : OK
  • python3-chardet : OK
  • python3-click : OK
  • cmake : OK
  • libcminpack1 : OK
  • libcminpack-dev : OK
  • libcppunit-dev : OK
  • python3-cycler : OK
  • python3-dateutil : OK
  • python3-docutils : OK
  • doxygen : OK
  • libeigen3-dev : OK
  • fftw : OK
  • fftw-dev : OK
  • libfreeimage3 : OK
  • libfreeimage-dev : OK
  • libfreetype6 : OK
  • libfreetype6-dev : OK
  • graphviz : OK
  • libgraphviz-dev : OK
  • python3-idna : OK
  • python3-imagesize : OK
  • python3-kiwisolver : OK
  • liblapack3 : OK
  • liblapack-dev : OK
  • libxml2 : OK
  • libxml2-dev : OK
  • clang : OK
  • llvm-dev : OK
  • python3-markupsafe : OK
  • python3-matplotlib : OK
  • libmetis5 : OK
  • libmetis-dev : OK
  • python3-mpi4py : OK
  • python3-nose : OK
  • python3-numpy : OK
  • python3-numpydoc : OK
  • python3-packaging : OK
  • python3-pandas : OK
  • python3-psutil : OK
  • python3-pyparsing : OK
  • readline-common : OK
  • python3-tz : OK
  • libqwt-qt5-6 : OK
  • libqwt-qt5-dev : OK
  • python3-requests : OK
  • libbsd0 : OK
  • libbz2-1.0 : OK
  • libc6 : OK
  • libdrm2 : OK
  • libegl1 : OK
  • libexif12 : OK
  • libexpat1 : OK
  • libfftw3-double3 : OK
  • libfontconfig1 : OK
  • libgl1 : OK
  • libglu1-mesa : OK
  • libgomp1 : OK
  • libgphoto2-6 : OK
  • libice6 : OK
  • libjbig0 : OK
  • libltdl7 : OK
  • liblzma5 : OK
  • libncurses5 : OK
  • libnuma1 : OK
  • libpcre3 : OK
  • libquadmath0 : OK
  • libraw1394-11 : OK
  • libsm6 : OK
  • libstdc++6 : OK
  • libtiff5 : OK
  • libudev1 : OK
  • libusb-1.0-0 : OK
  • libuuid1 : OK
  • libx11-6 : OK
  • libx11-xcb1 : OK
  • libxau6 : OK
  • libxcb1 : OK
  • libxcb-glx0 : OK
  • libxcb-xfixes0 : OK
  • libxcb-xkb1 : OK
  • libxdmcp6 : OK
  • libxext6 : OK
  • libxft2 : OK
  • libxi6 : OK
  • libxkbcommon0 : OK
  • libxkbcommon-x11-0 : OK
  • libxmu6 : OK
  • libxpm4 : OK
  • libxrender1 : OK
  • libxss1 : OK
  • libxt6 : OK
  • zlib1g : OK
  • libsqlite3 : OK
  • libssl-dev : OK
  • gcc : OK
  • make : OK
  • sed : OK
  • g++ : OK
  • libexpat1-dev : OK
  • libfontconfig1-dev : OK
  • flex : OK
  • bison : OK
  • libglu1-mesa-dev : OK
  • perl : OK
  • libxcb-dri2-0-dev : OK
  • libxkbcommon-dev : OK
  • libxkbcommon-x11-dev : OK
  • bzip2 : OK
  • libxi-dev : OK
  • libxt-dev : OK
  • libxmu-dev : OK
  • libxpm-dev : OK
  • libxft-dev : OK
  • automake : OK
  • libtool : OK
  • libjpeg-dev : OK
  • cmake : OK
  • libicu-dev : OK
  • libopenmpi-dev : OK
  • libreadline-dev : OK
  • libhwloc-dev : OK
  • libsqlite3-dev : OK
  • libcurl4-openssl-dev : OK
  • libxcursor-dev : OK
  • libtbb-dev : OK
  • python3-scipy : OK
  • python3-setuptools : OK
  • python3-sip : OK
  • python3-sip-dev : OK
  • python3-six : OK
  • python3-stemmer : OK
  • python3-sphinx-rtd-theme : OK
  • python3-sphinxcontrib.websupport : OK
  • sphinx-intl : OK
  • python3-statsmodels : OK
  • python3-statsmodels : OK
  • libtcl : OK
  • tcl-dev : OK
  • libtk : OK
  • tk-dev : OK
  • python3-toml : OK
  • python3-urllib3 : OK
2

hi, can you:

  • share the output of apt list --installed.
  • check if the issue occurs with mesa_salome launcher.
  • tell whether you’re running remotely (via ssh) or on a virtual machine.
3

aptlistinstalled.txt (268.7 KB)

Thanks Nabil,
I attached the output of of the apt list --installed. Sorry for not mentioning it in my previous message, but I had already checked and the problem is identical if I run mesa_salome . Finally, I am not running salome remotely or on a virtual machine.
Thanks again.

4

At first sight, you can try to install these additional packages and see if it helps.

missing.db12.p1.txt (810 Bytes)

5

Thanks Nabil.
I have installed all the libraries in the list (although I wasn’t able to find glx-alternative-mesa, glx-alternative-nvidia, glx-diversions on my debian repositiories).
However, the behavior is still the same as before. Same crash modality and same error.

Andrea

6

can you check whether:

 SALOME-9.12.0-native-DB12-SRC/mesa_salome context
paraview

at least starts ParaView?

7

I am not sure I am getting correctly what you are asking. If I run the command
SALOME-9.12.0-native-DB12-SRC/mesa_salome context paraview
paraview is not running.
If instead I run
SALOME-9.12.0-native-DB12-SRC/mesa_salome context
and then type
paraview
My system paraview (5.11.0) starts with no issues.
However, I checked and if I start the mesa_salome gui and then mouse-click on the paraview botton, the paraview plugin works fine.
I hope this answers to your question. I apologize but I don’t know exactly what the context command/option is supposed to do and how it works.

Andrea
8

It is hard to guess the issue.
Can you launch again SALOME by setting

SALOME_VERBOSE=1 SALOME-9.12.0-native-DB12-SRC/salome -V2  2>&1 | tee -a salome.log

and share the output file: salome.log - it will hopefully provide some additional information .

In addition, did you try the universal binary and see if it works?

9

salome.log (214.7 KB)

Nabil,
I am attaching the log file you asked me to generate.
As for trying the universal binary, yes I tried it. As for the 9.10 and 9.12 version, the 9.12 version of the universal binary works somewhat ok, although some of the bottons in the GUI (like for instance the explode botton) result in the error

GUI library corresponding to the user action can not be found or loaded

I believe this is a known issue. Because working without some GUI bottons is kind of annoying, I tried to fix it using some of the recipes reported in the forum, but none worked for me.
So, seeing that a specific version for debian 12 was out, I was hoping that I could finally have a fully operational salome suite.

 Andrea
10

Hi Nabil,
did you get the chance to take a look at the log file I posted and understand what the issue is?
Thanks again.

  Andrea
11

Hi Andrea
I did not have time to look at it (i did not find a workstation so far) and see if we can reproduce the issue on our side. Note that in another thread, it was reported some issues with wayland.
Thus are you running it?

Regards

12

Hi Nabil.
I took a look at the thread you referenced.
Indeed, if I switch to a x11 session Salome runs fine and all the GUI buttons appear to be working.
So, the problem is apparently wayland. I am quite surprised to be the only one having this problem, as wayland is now the standard with debian 12.
However, thank you very much for the suggestions, you helped me a lot.

  Andrea

P.S.: for reference,

here it is explained how to switch to x11 from wayland in a reversible way.

1 Like