Running problem

Quote from Ashok Arya on September 8, 2020, 11:39 amWhile running ovito, I get the message
symbol lookup error: /lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b
I have OPENSSL version 1.1.1g installed on Fedora 32
While running ovito, I get the message
symbol lookup error: /lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b
I have OPENSSL version 1.1.1g installed on Fedora 32

Quote from Alexander Stukowski on September 8, 2020, 11:52 amIt looks like similar problems have been reported for other software on Fedora 32:
https://bugzilla.redhat.com/show_bug.cgi?id=1829790
I am looking for a solution...
It looks like similar problems have been reported for other software on Fedora 32:
https://bugzilla.redhat.com/show_bug.cgi?id=1829790
I am looking for a solution...

Quote from Alexander Stukowski on September 8, 2020, 12:19 pmIt may help to remove the copy of
libcrypto
shipping with OVITO and replace it with the system's version of that library. But I couldn't verify that so far, because I do not have a Fedora 32 installation at hand. So, could you please try the following?cd ovito-pro-3.2.1-x86_64 rm lib/ovito/libcrypto.so.1.1 ln -s /lib64/libcrypto.so.1.1 lib/ovito/libcrypto.so.1.1Please check if the file
/lib64/libcrypto.so.1.1
actually exists on your system. It may have a different name. Thank you.
It may help to remove the copy of libcrypto
shipping with OVITO and replace it with the system's version of that library. But I couldn't verify that so far, because I do not have a Fedora 32 installation at hand. So, could you please try the following?
cd ovito-pro-3.2.1-x86_64 rm lib/ovito/libcrypto.so.1.1 ln -s /lib64/libcrypto.so.1.1 lib/ovito/libcrypto.so.1.1
Please check if the file /lib64/libcrypto.so.1.1
actually exists on your system. It may have a different name. Thank you.

Quote from Ashok Arya on September 8, 2020, 2:27 pmThanks a lot, it worked. In fact, libcrypto.so.1.1 is again a link to libcrypto.so.1.1g in /lib64/
Thanks a lot, it worked. In fact, libcrypto.so.1.1 is again a link to libcrypto.so.1.1g in /lib64/