Sudo ln -s /opt/Autodesk/Adlm/R14/lib64/libcrypto.so.1.0.2 /usr/autodesk/maya2019/lib/libcrypto.so.10 after i installed maya, i do some link job like this as often : I use rocky linux 8.7,and install maya 2019 20,every of them porfect ruuning on my system, so i think the rocky linux 8.7 is not the point of problem. Hi, I think the problem is updating 8.6 to 8.7 break the file link,for example libssl.so.10 libcrypto.so.10 libpcre16.so.0, by default maya use these files provided by system path /usr/lib64/, the updating action maybe update these files too, so maya2023 start crash happen.

That way you force Maya to use it’s own lib directory first without it searching in /usr/lib and finding the system-wide conflict.

What you can also do, is add a library path to Maya, so let’s assume Maya has /usr/autodesk/maya2023/lib directory, you could do: LD_LIBRARY_PATH=/usr/autodesk/maya2023/lib /usr/autodesk/maya2023/bin/maya I would expect since libmd shows as being part of EPEL that your KDE install has pulled this in, which means your KDE desktop relies on it and might now be unstable due to you renaming the library. If it wants to remove half of your installed system as well, then that is a much bigger problem. If it removes itself, then at least the library is removed and doesn’t exist on your system. You should open a bug or report it to Autodesk to get them to fix their app properly.Īlternatively, attempt to remove it: dnf remove libmdĪnd see if it’s going to uninstall just itself or a whole load of other apps to find out what kind of severity you are facing. Not a good idea, since anything else on your system that relies on that will now be broken because you just renamed a system-wide library. So I renamed libmd.so.0.0.5 to libmd.so.0.0.5-0000 and Maya 2023 started as normal.

Install maya 2022 linux