Solution for singularity error: GLIBC_2.34 not found (Ubuntu22.04)

sb1966

Dear hberro,

Thanks a lot for your solution.

It has worked perfectly with Linux Mint 21.2 (code-named Victoria) in an old PC having NVIDIA GM108M [GeForce 920MX] card.

Best regards.

Sukumar

NorbertS

To run on Debian 11 and Debian 12 it is necessary to comment out libGLX.so in /etc/singularity/nvliblist.conf

libGLX_nvidia.so

libglx.so

#libGLX.so

libnvcuvid.so

Than it is possible to run salome-meca in GPU mode.

There is a singularity-container for Debian 11 and 12.

Add 'deb https: //fasttrack.debian.net/debian-fasttrack/ bullseye-fasttrack main contrib'

to /etc/apt/sources.list

Make 'apt install fasttrack-archive-keyring' before installing the singularity-container.

Norbert

scimulate

This isn't exactly a solution, but I'm running Salome-Meca through WSL on Windows 11 and ran into this issue when attempting to install on Ubuntu-22.04 and OpenSUSE Tumbleweed. For those doing similarly, install Oracle Linux 9.1 (glibc is version 2.34 on this), enable EPEL, install Singularity-CE, and then install the Salome-Meca Singularity container. That worked out-of-the-box for me.

SamiHa

Hello all,
I am new in Salome meca and I faced with Traceback (most recent call last) but not sure is the type you mentioned, mine shows a Key error of one of the operator I used.
Traceback (most recent call last):
File "./RunCase_3_Stage_1.comm.changed.py", line 78, in <module>
MODELE=FEM1)
File "/opt/salome_meca/V2022.1.0_scibian_univ/tools/Code_aster_stable-1560/lib/aster/code_aster/Supervis/ExecuteCommand.py", line 172, in run
return cmd.run(**kwargs)
File "/opt/salome_meca/V2022.1.0_scibian_univ/tools/Code_aster_stable-1560/lib/aster/code_aster/Supervis/ExecuteCommand.py", line 224, in run
self.exec(keywords)
File "/opt/salome_meca/V2022.1.0_scibian_univ/tools/Code_aster_stable-1560/lib/aster/code_aster/Supervis/ExecuteCommand.py", line 704, in exec
output = self._op(self, **keywords)
File "/opt/salome_meca/V2022.1.0_scibian_univ/tools/Code_aster_stable-1560/lib/aster/code_aster/MacroCommands/crea_elem_ssd_ops.py", line 43, in crea_elem_ssd_ops
CARA_ELEM=args['CARA_ELEM'],
KeyError: 'CARA_ELEM'

<FIN> MEMOIRE JEVEUX MINIMALE REQUISE POUR L'EXECUTION : 37.09 Mo
 <FIN> MEMOIRE JEVEUX OPTIMALE REQUISE POUR L'EXECUTION : 47.81 Mo
 <FIN> MAXIMUM DE MEMOIRE UTILISEE PAR LE PROCESSUS LORS DE L'EXECUTION : 1113.00 Mo

FERMETURE DES BASES EFFECTUEE

STATISTIQUES CONCERNANT L'ALLOCATION DYNAMIQUE :
TAILLE CUMULEE MAXIMUM : 48 Mo.
TAILLE CUMULEE LIBEREE : 2 Mo.
NOMBRE TOTAL D'ALLOCATIONS : 9073
NOMBRE TOTAL DE LIBERATIONS : 8899
APPELS AU MECANISME DE LIBERATION : 0
TAILLE MEMOIRE CUMULEE RECUPEREE : 0 Mo.
VOLUME DES LECTURES : 0 Mo.
VOLUME DES ECRITURES : 0 Mo.

MEMOIRE JEVEUX MINIMALE REQUISE POUR L'EXECUTION : 37.09 Mo
- IMPOSE DE NOMBREUX ACCES DISQUE
- RALENTIT LA VITESSE D'EXECUTION
MEMOIRE JEVEUX OPTIMALE REQUISE POUR L'EXECUTION : 47.81 Mo
- LIMITE LES ACCES DISQUE
- AMELIORE LA VITESSE D'EXECUTION
MAXIMUM DE MEMOIRE UTILISEE PAR LE PROCESSUS : 1113.00 Mo
- COMPREND LA MEMOIRE CONSOMMEE PAR JEVEUX,
LE SUPERVISEUR PYTHON, LES LIBRAIRIES EXTERNES

FIN D'EXECUTION LE : ME-22-MAI -2024 11:10:00
INFO 'glob.' deleted
INFO 'vola.' deleted

EXECUTION_CODE_ASTER_EXIT_143893=1

restoring result databases from 'BASE_PREC'...
WARNING: execution failed (command file #1): <F>_ABNORMAL_ABOR

Is his the same problem?
Best,
Sami

katoulos

hberro

Reporting success with salome_meca-lgpl-2022.1.0-1-20221225-scibian-9 on a SuSE Tumbleweed laptop

many thanks

mimis@hyugens:/opt/Salome-Meca $ inxi -G Graphics: Device-1: Intel CometLake-S GT2 [UHD Graphics 630] driver: i915 v: kernel Device-2: NVIDIA TU104M [GeForce RTX 2080 SUPER Mobile / Max-Q] driver: nvidia v: 550.78 Device-3: Realtek Integrated_Webcam_HD driver: uvcvideo type: USB Device-4: Tobii AB EyeChip driver: N/A type: USB Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.0 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa dri: iris gpu: i915,nvidia resolution: 1: 3840x2160 2: 1920x1080 API: EGL v: 1.5 drivers: iris,nvidia,swrast,zink platforms: wayland,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78 renderer: NVIDIA GeForce RTX 2080 Super/PCIe/SSE2 API: Vulkan v: 1.3.283 drivers: N/A surfaces: xcb,xlib,wayland

kaengo

Hello Hberror.
Many thanks for your solution.
Can you adapt it for salome_meca-lgpl-2023.1.0-4-20240327-scibian-10 please?

Greetings,
Holger

hberro

https://drive.google.com/file/d/1h4ASnmq9lzkETMiNqdcA9na8nqzDU1LG/view?usp=sharing

Here are some newer GL files (Scibian 11), You will need to replace the original script sc9gl folder contents with those and try if it works with SM-2023.

kaengo

Hello Hberro,
unfortunately didn't work for me
salome_meca-lgpl-2023.1.0-4-20240327-scibian-10
und Ubuntu 22.04
apptainer version 1.3.2

Tried also with the singularity from the website.

Greetings,
Holger

benico

hberro

Thanks !

bash ./sm2022_libgl_patch_ub22.04.run
./salome_meca-20221225-scibian-9 -B "./sc9gl:/opt/prerequisites/gl/dispatch"

mjb

Dear Colleagues,
in Kubuntu 22.04 or/and 24.04 I used/use, I hope in Ubuntu as well, always work for me a little change in etc/sigularity/nvliblist.conf file. The following libraries have to be greyed:

libGLdispatch.so

libglx.so

libGLX.so

Regards,
mjb

pidou46

Thanks mjb, but it doesn't work for me WSL2 + Ubuntu 24.04.2 LTS

If I remove thoses lib from /etc/singularity/nvliblist.conf file, I get theses error when salome startup:

SIGSEGV 'segmentation violation' detected. Address 0

hberro

pidou46

Hello pidou46

Which WSL2 distribution are you using ?

I suggest that you test the tweaked Scibian11 WSL2 distribution from

https://forum.code-aster.org/public/d/28014-salome-meca-20241-on-wsl2-ready-to-use-distribution

It already includes Salome Meca 2024.1 and should work on any gpu configuration.

gbaz

hberro
Good afternoon and fist of all many many thanks to you and all the forum's people for your big work helping us with Salome-Meca and Code Aster.

The wls2 version could be installed directly in Ubuntu 24.04?
Is there any attention to pay?
Please be aware that I'm a totally beginner in everything.
Many thanks.
King regards

vishwas

Hello,
I installed latest salome_meca distribution on Ubuntu 24.04
Unfortunately none of the above solutions worked for me.
Interestingly my nvliblist.conf is located under /usr/local/etc/singularity/ and not /etc/singularity/
Nevertheless I commented out those libGLX type lines , all of them but whenever I launch salome it opens but when I switch to GEOM or any other module throws the following error:
![

I also downloaded the .run file and newer gl files and did overwrite in sc9gl folder but same error always.
I would be grateful if someone find the solution.

Thanks
Vishwas
](https://)

LucasSovre

@vishwas#p75235 Have you tried using the Docker image available here: https://hub.docker.com/r/simvia/code_aster? It might make things easier for you.

If you really prefer using Singularity, here's how you can convert a Docker image into a Singularity image:
https://docs.sylabs.io/guides/2.6/user-guide/singularity_and_docker.html#import-a-docker-image-into-a-singularity-image

This documentation might also be helpful:
https://github.com/simvia-tech/Videos/blob/main/%5BTips%20%26%20Tricks%5D%20Install%20Salome_Meca%20on%20Windows%20using%20WSL/Commands%20used%20in%20the%20video.md

Regards,
Lucas SOVRE

RichIndesteege

Hello,
Last week I upgraded to OpenSUsE Leap 15.6
Installed singularity and Nvida driver, Cuda, ... and nvidia-container-toolkit and edited the .bashrc file with the path to salome-meca and the alias "salome2024" to invoke the salome-meca containerized application.
Everything worked as expected!
Today (sept 8-2025) I updated my system and a new apptainer-package was installed and therefore singularity-package was removed!
However, the command "singularity" to invoke salome-meca still exist in the new apptainer package, so I did not need to alter the .bashrc file, but I now encountered again the "libGL" errors!
Editing the /etc/apptainer/nvliblist.conf file and commenting out the lines "libGLdispatch.so" and also "libGLX.so" made that it worked again!
Regards,
Richard Indesteege

jmarcelino

Dear all,

I think I have finally managed to create a solution that enables the use of the sif container with GPU acceleration.

My system:

HP HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC
11th Gen Intel® Core™ i7-11850H × 16
32.0 GiB
NVIDIA RTX A2000 Laptop GPU

Ubuntu 24.04

Besides the instalation described in the salome-meca website:

1) install virtualgl.deb

problem: there are some libraries no present in ubuntu 24.04 so a tailor made version is necessary.
you can correct this (ask chagpt) or ask me to send the file (it is not possible to post it here)

2) Then comment out:

libGLdispatch.so
libglx.so
libGLX.so

/etc/singularity/nvliblist.conf

3) run salome-meca with:
export DISPLAY=:1
export __NV_PRIME_RENDER_OFFLOAD=1
export __GLX_VENDOR_LIBRARY_NAME=nvidia
vglrun -d :1 ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11

et voilá!

Hope it helps!

João

code_gangster

I have sovled the problem.
You do not need to instasll any additional programs.
Please follow the steps below:

1. Open the configuration file

sudo nano /etc/apptainer/nvliblist.conf
(Note: Use /etc/singularity/nvliblist.conf if you are using Singularity instead of Apptainer.)

2. Locate and comment out the following two lines Find these lines and add a # at the beginning:

#libGLX.so

#libGLdispatch.so

3. Save the changes and run Salome-meca in normal mode

Why this works:
This prevents the container from importing the host's latest libraries, which cause the version conflict (specifically the GLIBC_2.34 not found error). By commenting out these lines, the container will use its own internal libraries that are compatible with its environment.

« Previous Page