[Solved] Issue to run Julia from snap: symbol lookup error: /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE

If you installed Julia from snap, and tried to run it from Python3, probably you get the following issue.

from julia.api import Julia
jl = Julia(compiled_modules=False)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.10/dist-packages/julia/core.py", line 472, in __init__
    self.api = LibJulia.from_juliainfo(jlinfo)
  File "/usr/local/lib/python3.10/dist-packages/julia/libjulia.py", line 203, in from_juliainfo
    return cls(
  File "/usr/local/lib/python3.10/dist-packages/julia/libjulia.py", line 226, in __init__
    self.libjulia = ctypes.PyDLL(libjulia_path, ctypes.RTLD_GLOBAL)
  File "/usr/lib/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE

Appears to be a core18 error, but I can't remove it, because other packages are installed and are using it.
If you add Julia to your PATH, at the terminal startup you will see:

mkdir: symbol lookup error: /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE
mv: symbol lookup error: /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE

I tried downgrade Julia from version 1.8.1 to 1.6.7, with:

snap info julia
sudo snap refresh julia --channel=lts/stable

However the issue its persistent.

To solve it, just download Julia package from github:

wget https://julialang-s3.julialang.org/bin/linux/x64/1.8/julia-1.8.1-linux-x86_64.tar.gz
tar xzvf julia-1.8.1-linux-x86_64.tar.gz
cd julia-1.8.1
pwd

Now, add this directory to your PATH in ~/.bashrc

export JULIA="~/julia-1.8.1"
export PATH="${PATH}:${JULIA}/bin"
export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${JULIA}/lib"

Now, execute Julia in Python3:

from julia.api import Julia
>>> jl = Julia(compiled_modules=False)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.10/dist-packages/julia/core.py", line 513, in __init__
    self._call("const PyCall = Base.require({0})".format(PYCALL_PKGID))
  File "/usr/local/lib/python3.10/dist-packages/julia/core.py", line 549, in _call
    self.check_exception(src)
  File "/usr/local/lib/python3.10/dist-packages/julia/core.py", line 603, in check_exception
    raise JuliaError(u'Exception \'{}\' occurred while calling julia code:\n{}'
julia.core.JuliaError: Exception 'ArgumentError' occurred while calling julia code:
const PyCall = Base.require(Base.PkgId(Base.UUID("438e738f-606a-5dbb-bf0a-cddfbfd45ab0"), "PyCall"))

To run PyCall, go to Julia REPL and add the package "PyCall".

Pkg.add("PyCall")
ERROR: UndefVarError: Pkg not defined

Before call Pkg, remeber use Pkg:

using Pkg
Pkg.add("PyCall")

Now, all its ok. Enjoy!


Comments

Post a Comment

Popular posts from this blog

How to install Matlab without GUI

If you want to install Matlab in a server, probably you don't have a GUI. To run the installer you need previosly configurate silent mode: ./install -mode silent Preparing installation files ... Installing ... (Nov 03, 2016 10:53:02) ################################################################## (Nov 03, 2016 10:53:02) (Nov 03, 2016 10:53:03) When running the installer with an input file, you must accept the license agreement by setting the agreeToLicense option to yes. (Nov 03, 2016 10:53:03) Exiting with status -2 (Nov 03, 2016 10:53:07) End - Unsuccessful. The previous error is because we need configurate all options, like if you are agree with the license agreement, enter the licence key, etc. To do this, you need to edit  installer_input.txt and  activate.ini files: In activate.ini these are the lines that you need configurate: isSilent=true activateCommand=activateOffline licenseFile=/root/Matlab_R2016a_glnxa64.lic In installer_input.txt these ...
Read more

How to fix Android when developer options are not available for this user

Image
I have an Android One with Oreo version and suddenly my Android rebooted and after that it started to behave strangely: 1) Notification section doesn't work. I can't see notifications from my apps and the arrow and the screw icon to settings access don't work. 2) As I can't access to the notification area, I can't enable Use USB to Transfer Files to access to my phone memory. 3) I can't access to developer mode (I before active it with a lot of taps over Build number). Clicking on developer options just shows developer options are not available to this user. 4) I can't update or install the apps on google play. They freeze on Download pending... message 5) Home and Switch buttons don't work. They light up and vibrate when I tap them but they do nothing. This issue is apparently related to a deconfiguration of user accounts. To fix it, you need re-setup the users. As you can't access to the user manager (you are in guest mode ...
Read more

Exception: Could not find a default OpenFlow controller in Mininet

If you try to run a mininet script like this  , maybe you will get this problem if you are under Ubuntu. Exception: Could not find a default OpenFlow controller  This is trigger because your system don't find a default controller . To enable it just add the first line and add the controller argument to net variable like the second line: from mininet.node import OVSController net = Mininet(topo=topo,host=CPULimitedHost, link=TCLink,controller = OVSController) Now, you will get the following error: c0 Cannot find required executable ovs-controller. Please make sure that it is installed and available in your $PATH: (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin) ovs-controller is a legacy name. You need to be sure that you has it. sudo apt-get install openvswitch-testcontroller sudo cp /usr/bin/ovs-testcontroller /usr/bin/ovs-controller If you run it again, you should kill ovs-testcontroller first to avoid this: Exception: Please s...
Read more