Package Details: salome-meca-bin 2017.0.2-3

Git Clone URL: (read-only)
Package Base: salome-meca-bin
Description: Integration of the Code_Aster solver in the Salome platform
Upstream URL:
Licenses: LGPL
Provides: salome-meca
Submitter: m-pilia
Maintainer: m-pilia
Last Packager: m-pilia
Votes: 0
Popularity: 0.000000
First Submitted: 2017-12-01 13:56
Last Updated: 2018-02-25 13:04

Latest Comments

m-pilia commented on 2018-03-19 06:28

Hello Tomatopaste!

If the checksum is ok, then it is very unlikely that the tarball is corrupted. But it is possible that some libraries get corrupted during the install process, for instance I noticed that for this package yaourt removes all the content of most shared libraries, leaving empty files, I guess something goes wrong with the symbol stripping.

Also, I see from your comment (2018-03-18 00:20) you launched salome with system's python2. Did you try using the bundled version of Python and relative bin and library paths? (using the command I posted in my comment 2018-03-10 11:46)

If it still fails, you can check whether the shared libraries are corrupted, maybe installing salome manually in user space and comparing the files for which you get an error (e.g. /opt/salome_meca/V2017.0.2/prerequisites/Occ-710p1/lib/

Tomatopaste commented on 2018-03-19 00:36

Hello m-pilia!

I used wget to store the tgz from the link above in /tmp. Then I used makepkg and installed it via pacman -U. So it's a similar process as with yaourt, but manually. My /tmp has a size of roughly 8GiB.

What catched my attention was that sometimes the download from the source was halted and resumed, but the md5 checksum was still okay. It may be an unjustified guess, but maybe the tgz from the source is corrupted?

Best, Tomatopaste

m-pilia commented on 2018-03-18 10:16

Hello Tomatopaste!

It seems there is something wrong with the content of the shared libraries. Did you create the package with yaourt (or some other AUR helper)? In that case, you could try creating it with makepkg instead. There is some problem with the shared libraries when packaging this with yaourt (that I still have to investigate).

Tomatopaste commented on 2018-03-18 00:20

Hi m-pilia!

I'm facing problems starting your 'salome-meca-bin' package. Installing with your PKGBUILD finishes successfully, though. Do you have an idea?

Best, Tomatopaste

[marc@zam482 appli_V2017.0.2]$ python2 ./salome
runSalome running on zam482
Searching for a free port for naming service: 2813 - OK
Searching Naming Service + found in 0.1 seconds 
SALOME_Session_Server: error while loading shared libraries: /opt/salome_meca/V2017.0.2/prerequisites/Occ-710p1/lib/ file too short
SALOME_LauncherServer: error while loading shared libraries: /opt/salome_meca/V2017.0.2/prerequisites/Libxml2-290/lib/ file too short
SALOME_ConnectionManagerServer: error while loading shared libraries: /opt/salome_meca/V2017.0.2/prerequisites/Libxml2-290/lib/ file too short
Traceback (most recent call last):
  File "/opt/salome_meca/appli_V2017.0.2/bin/salome/", line 625, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "/opt/salome_meca/appli_V2017.0.2/bin/salome/", line 570, in startSalome
  File "/opt/salome_meca/V2017.0.2/modules/KERNEL_V8_3_0/bin/salome/", line 174, in waitNSPID
    raise RuntimeError, "Process %d for %s not found" % (thePID,theName)
RuntimeError: Process 11973 for /Kernel/Session not found
Searching /Kernel/Session in Naming Service

--- Error during Salome launch ---

m-pilia commented on 2018-03-17 09:31

Hello bodbod!

Since salome starts with the command I suggested, the problem you mentioned in your post on 2018-03-09 07:39 may be due to some outdated launcher still present from a previous installation, so if you find and remove such file(s) you should solve that issue.

About your new problem, it looks like there is something wrong with the rendering of the UI. Unfortunately the warnings may not be very helpful, since I get the same warnings on my installation, that works correctly (I use KDE). May I ask you which desktop environment you use?

Also, may I ask whether you have already tried installing salome manually, following the instructions from the official website?

Because if it works correctly that way, it means that there is some problem with this package, otherwise it may be a problem with the DE, or maybe some missing dependency... Unfortunately Arch is not officially supported by salome, so if something goes wrong (e.g. with broken dependencies) it can be tricky to find the cause.

bodbod commented on 2018-03-16 22:44

I also updated the system, i.e. pacman -Syu, but that also did not help

bodbod commented on 2018-03-16 21:18

I should also mention that the menu items DO work even though I can not see them. For example: File > bottom line of blank menu - This will exit salome-meca

bodbod commented on 2018-03-16 21:13

Hello m-pilia, Closer but not quite there! The gui opens up this time, but I get a blank menu if I: -click on the one of the menu items at the top of the screen or -right click on the pane in the left hand window.

Also I received the warnings shown below. I tried searching for those in the arch repositories in case they were missing dependencies, but I couldn't find anything.

INFO:MainThread:Problem loading PortManager file: /tmp/.salome_PortManager.cfg INFO:PortManager:Problem loading PortManager file: /tmp/.salome_PortManager.cfg Searching for a free port for naming service: 2810 - OK Searching Naming Service + found in 0.1 seconds Searching /Kernel/Session in Naming Service +++++++++++++++++++++Warning: this type (Study,objref) already exists, it will be ignored. + found in 11.0 seconds Start SALOME, elapsed time : 12.9 seconds

  • Warning: HYBRIDPLUGIN GUI resources are not found.
  • HYBRIDPLUGIN GUI will not be available.
<hr> <hr>
  • Warning: BLSURFPLUGIN GUI resources are not found.
  • BLSURFPLUGIN GUI will not be available.
<hr> <hr>
  • Warning: HexoticPLUGIN GUI resources are not found.
  • HexoticPLUGIN GUI will not be available.
<hr> <hr>
  • Warning: NETGENPLUGIN GUI resources are not found.
  • NETGENPLUGIN GUI will not be available.
<hr> <hr>
  • Warning: GHS3DPLUGIN GUI resources are not found.
  • GHS3DPLUGIN GUI will not be available.

m-pilia commented on 2018-03-10 11:46

Hello bodbod!

The warnings should be ok, there are some actual loops but they should not be a problem. However the error looks definitely weird, it is searching for the executable in the wrong place...

Could you check what happens if you try to run salome from the command line, with the AUR package installed, using the following command? (careful, it is a bit long and it may wrap here on the browser, but it is all a single line!)

PATH=/opt/salome_meca/V2017.0.2/prerequisites/Python-2710/bin/:$PATH LD_LIBRARY_PATH=$(find /opt/salome_meca/V2017.0.2/ -type d -name lib | tr '\n' ':' | sed 's/:$//'):$LD_LIBRARY_PATH /opt/salome_meca/appli_V2017.0.2/salome

Btw, this command should be the same contained in the launcher file /usr/share/applications/salome_meca.desktop if the installation went right.

bodbod commented on 2018-03-09 07:39

Hi m-pilia,

That is correct, I used yaourt previously. I tried using the makepkg method this time. It installed but didn't work. Here are warnings I encountered during the install:

==> Starting build()... Extracting installer... Building virtual application... Fixing references... grep: warning: /home/bo/Downloads/salome-meca-bin/src/salome_meca/V2017.0.2/modules/ASTERSTUDY_201702/lib/salome: recursive directory loop grep: warning: /home/bo/Downloads/salome-meca-bin/src/salome_meca/appli_V2017.0.2/lib/salome/lib/salome/lib: recursive directory loop Fixing symlinks... ==> Entering fakeroot environment...

And here is the error when I tried to run salome-meca: Failed to execute command "/home/bo/salome/appli_V8_3_0/salome %f". Failed to execute child process “/home/bo/salome/appli_V8_3_0/salome” (No such file or directory)

Thanks m-pilia!

All comments