Skip to content

camotics: error while loading shared libraries: libv8.so.3.14.5 #438

Open

Description

@reset12

Had the same error camotics: error while loading shared libraries: libv8.so.3.14.5 on Ubuntu 24.04 and 24.10.
It seems an old error that is more than once reported. Is there a chance to repair that ?

Activity

  1. hesperaux commented on Jun 22, 2025

    @hesperaux

    See my comment on #215

    It's a hack but it will get it to run. It looks like the developers are not going to fix this issue.

  2. SirGeekALot commented on Jul 9, 2025

    @SirGeekALot

    I'm getting the exact same error on Ubuntu 25.04. I tried the link hack you posted and it didn't work.

    I'm seriously bummed out. CAMotics has been my go-to CAM simulation app since it was called OpenSCAM. I quit Windows and moved to Linux about a month or two ago. I was using Ubuntu, then tried Fedora to see if it would fix a NVidia GPU crash I had. It didn't (so I pulled the card out). I was really missing .deb support, and when I could not find an rpm for camotics (except on some shady .ru domain) that was the last straw. I paved my SSD and put Ubuntu 25.04 back.

    But now it seems I simply cannot get camotics to run. I has a sad. :-(

  3. hesperaux commented on Jul 9, 2025

    @hesperaux

    I'm getting the exact same error on Ubuntu 25.04. I tried the link hack you posted and it didn't work.

    I'm seriously bummed out. CAMotics has been my go-to CAM simulation app since it was called OpenSCAM. I quit Windows and moved to Linux about a month or two ago. I was using Ubuntu, then tried Fedora to see if it would fix a NVidia GPU crash I had. It didn't (so I pulled the card out). I was really missing .deb support, and when I could not find an rpm for camotics (except on some shady .ru domain) that was the last straw. I paved my SSD and put Ubuntu 25.04 back.

    But now it seems I simply cannot get camotics to run. I has a sad. :-(

    You installed libnode-dev (or the Ubuntu equivalent) right? The symlimk only works if you actually have the library installed. Libnode now provides the libv8 functions in recent release which is why this is happening, iirc.

    Happy to help you further but I might need more info if you already have libnode.

  4. SirGeekALot commented on Jul 10, 2025

    @SirGeekALot

    Thanks for the reply. I tried again, doing the following:

    sudo apt remove camotics
    (successfully removed)

    sudo apt install libnode-dev

    Response:
    libnode-dev is already the newest version (20.18.1+dfsg-1ubuntu2).

    sudo dpkg -i camotics_1.2.0_amd64.deb
    (successfully installed)

    cd /usr/bin
    ./camotics

    camotics: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

    EDIT: wait. forgot to link...

    sudo ln -s libv8.so libv8.so.3.14.5

    ./camotics

    same error:
    camotics: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

  5. hesperaux commented on Jul 11, 2025

    @hesperaux

    Thanks for the reply. I tried again, doing the following:

    sudo apt remove camotics
    (successfully removed)

    sudo apt install libnode-dev

    Response:
    libnode-dev is already the newest version (20.18.1+dfsg-1ubuntu2).

    sudo dpkg -i camotics_1.2.0_amd64.deb
    (successfully installed)

    cd /usr/bin
    ./camotics

    camotics: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

    EDIT: wait. forgot to link...

    sudo ln -s libv8.so libv8.so.3.14.5

    ./camotics

    same error:
    camotics: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

    Oh it's just missing openssl. You probably have openssl3 installed, but check for openssl1 and install that.
    The package is probably called openssl-1 or libopenssl-1 or similar (apt search openssl).

    If you already have it installed, you might have another version of openssl 1.x. In that case you can use the same kind of hack to point libssl.so.1.1 to libopenssl.so.1.

  6. SirGeekALot commented on Jul 12, 2025

    @SirGeekALot

    Oh it's just missing openssl. You probably have openssl3 installed, but check for openssl1 and install that. The package is probably called openssl-1 or libopenssl-1 or similar (apt search openssl).

    If you already have it installed, you might have another version of openssl 1.x. In that case you can use the same kind of hack to point libssl.so.1.1 to libopenssl.so.1.

    I didn't see the ones you mentioned, but apt search openssl turned up a lot, so I don't know which (if any) would be the right one.

    Attaching the search result.

    openssl.txt

  7. bombela commented on Jul 17, 2025

    @bombela

    For what platform this deb package is built for? I symlinked libv8, libssl, and libcrypto.

    Image

    Ubuntu 24.04.2 LTS. And libssl is v3, no other choice.

  8. SirGeekALot commented on Jul 17, 2025

    @SirGeekALot
    cd /usr/bin
    ls -l openssl
    -rwxr-xr-x 1 root root 1132096 Apr  3 01:48 openssl
    
    openssl -v
    OpenSSL 3.4.1 11 Feb 2025 (Library: OpenSSL 3.4.1 11 Feb 2025)
    
    

    I definitely have openssl installed. I just don't know what ln (link) command I should use. Help?

  9. hesperaux commented on Jul 18, 2025

    @hesperaux

    Most likely it's built for debian (that's what I'm using).
    Unfortunately if your package manager doesn't have openssl1 you will have to build it yourself or risk it with a .deb from the internet. You could try taking the deb from debian 12 but it may cause conflicts.

    The best solution would be to compile openssl v1 from source, then manually install a symlink. Sounds like a good question for chatgpt at this point! 😅

    You can also build the so file and put it into the same directory as the executable. This usually works too (instead of making a symlink in system directories).

  10. bombela commented on Jul 18, 2025

    @bombela
  11. hesperaux commented on Jul 18, 2025

    @hesperaux

    Well now I am wondering why it works in my machine... 🤔
    And you're right about the rest of course. If it wasn't being used in a networkless cam sim I would be skeptical.
    Actually, what IS openssl used for in this software?

    I am on debian 12.11 and I only have libsslv3 available. I don't think
    opensslv1 is easily available, probably because it's most often used
    over the network and it isn't safe. But I could be mistaken.

    On Thu, 17 Jul 2025 at 17:14, David @.***> wrote:

    hesperaux left a comment (#438)

    Most likely it's built for debian (that's what I'm using).
    Unfortunately if your package manager doesn't have openssl1 you will have to build it yourself or risk it with a .deb from the internet. You could try taking the deb from debian 12 but it may cause conflicts.

    The best solution would be to compile openssl v1 from source, then manually install a symlink. Sounds like a good question for chatgpt at this point! 😅

    You can also build the so file and put it into the same directory as the executable. This usually works too (instead of making a symlink in system directories).

    —
    Reply to this email directly, view it on GitHub, or unsubscribe.
    You are receiving this because you commented.Message ID: @.***>

  12. SirGeekALot commented on Jul 21, 2025

    @SirGeekALot

    Actually, what IS openssl used for in this software?

    That is a very good question. It seems like it should not need this if it only opens local files!

    Nefarious reasons? (reaches for tinfoil hat)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions