Arch Linux User Repository

We still investigating Maya 2025+. The licensing does not run [1] [2] [3].

Many thanks to ttc0419 for getting this set up and for writing these instructions originally.

Installation Instructions:

To download the latest version of Maya, go to your Autodesk account Products and Services and save the Linux tgz file to any location of your choice.

Extract the tgz file to any location of your choice.

Maya is now split into several packages as it is for the official rpm installation. You will need the following files from the extracted tgz file to build some other packages as well:

1. (required) Packages/adlmapps*.rpm to build adlmapps
2. (required) Packages/adsklicensing*.rpm to build adsklicensing
3. (required) Packages/Maya*.rpm to build this package
4. (optional) Packages/package.zip to build maya-arnold
5. (optional) Packages/Bifrost*.rpm to build maya-bifrost
6. (optional) Packages/AdobeSubstance3DforMaya*.rpm to build maya-substance, if you don't want to download directly from Adobe
7. (optional) Packages/MayaUSD*.rpm to build maya-usd-bin, if you don't want to download directly from GitHub
8. (optional) Packages/LookdevX.rpm to build maya-lookdevx

Packages 1 and 2 are required to use Maya and 4 to 8 are plugins that can be installed when needed.

You will need to move the rpm files to the directory containing the corresponding package's PKGBUILD file. Please refer to the AUR wiki for further installation details, since AUR helpers may or may not work with this package.

After installation, you may wish to enable the Autodesk Licensing service with systemctl enable adsklicensing.service. This service is started automatically one time when installing and removing this package.

Note that the install file will automatically register and deregister Maya with the licensing service if you are using the adsklicensing package. You may need to restart the adsklicensing service and reinstall Maya if adsklicensing was upgraded and running at the same time.

Launch Maya and log into your Autodesk account or enter your product serial to check out a license. Note that Wayland is currently not supported by the licensing software.

Please note that the Maya executable is patched to launch with the --single-process flag to address launch issues with the Application Home. You may try to opt out of this patch if this does not present an issue for you.

Troubleshooting:

If you are having the following font error, Failed trying to load font : -*-helvetica-bold-r-normal-*-11-*-*-*-*-*-iso8859-1 //, first try the Autodesk recommended commands with your normal permissions.

xset +fp /usr/share/fonts/100dpi
xset +fp /usr/share/fonts/75dpi
xset fp rehash

(source)

If you are still seeing font errors, you can try one or more of the following:

1. Install xorg-mkfontscale and run mkfontscale in /usr/share/fonts. Then re-run the xset commands above.
2. Try running the xset commands with superuser permissions.
3. Try enabling and generating the following locales: en_GB ISO-8859-1 en_US ISO-8859-1

If you are having licensing errors, you can refer to this comment/forum post by mac666er recommending you to only use the en_US.UTF-8 locale or this comment by TheSunCat recommending you to disable Wayland.

If your launch process hangs at the OpenCL initialization, you may wish to check for OpenCL conflicts as mentioned in this comment by TheSunCat. You may also need to rename/delete the intel-openapi icd file in /etc/OpenCL/vendors as mentioned here.

Cheers

I have figured out why Maya is crashing. It sees that /usr/lib/libmd.so is present and tries to initialise IRIX's MIDI interface, fails to find the required symbols and calls a null pointer. Simply delete the /usr/lib/libmd.so symlink and Maya will start working again.

I am not sure if an issue should be filed to rename libmd (which is a library of message digest routines, nothing to do with MIDI) to something else, as other software might get similarly confused.

@Cuissedemouche i can see that the libtiff problem has been solved, as in my last comment, it was just a question, a "no i haven't solved it yet" would have sufficed. if you want to install 2022.1 you need to use the pkgbuild given for 2022 with the following changes.

change in pkg build: (does not rectify the issue of segfaults but does update you to 2022.1)

pkgver=2022.1 source=('manual://Maya2022_64-2022.1-579.x86_64.rpm') sha256sums=('a7932fdaf15b52b19908314c6b575f2ca4037871f26c3feaf907b091ba493817')

I have yet to get a pkg build for 2022.2 to work.

@theMaizeOfficial As I said, I still have the segfautl problem, but it was already mention that the libtiff.so.5 wasn't the one causing the segfault. The segfault is cause while the maya.bin is executed, so I really don't know what's the problem.

Maya 2022.2 has been released !

@Cuissedemouche did you get past the Segfault? i have successfully folowed your instructions and the libtiff issue is solved. how did you get past the faulting?

I solved the libtiff.so.5 problem by compiling it by myself but I still have the segfault problem.

If you want to solve the libtiff issue before it got solved by Arch, you can just go download the last libtiff release on the official website, and compiling it with the symbol flag: ./configure --enable-ld-version-script make make install

Also by default it install it under /usr/local/lib*, so you have to create a link to /usr/lib/

And thanks for reporting the issue (https://bugs.archlinux.org/index.php?do=details&action=details.addvote&task_id=71330)

im going to install redhat 8.2 via the develpers program.

No, no solution found as of now as far as I can tell. I don't use maya as my main software, I just use it every now and then, so I am dualbooting for now and running maya somewhere else

@ozzy1202 Is there a fix for the seg fault yet? or a work around? and my appologies the width of my terminal was small and i did not see that they were actually separated errors until i expanded it.

@theMaizeOfficial segfault is not libtiff issue as @costashatz already mentioned. Fixing the libtiff is already mentioned in galaxy0419 feature request for archlinux compilation of libtiff (you can probably compile it yourself to have the fix included if you really wish) but the segfaulting part is different issue altogether. My maya 2016 install that I had doesn't mention any libtiff issue (as I think it probably didn't use openimageio that is throwing this libtiff message) and it still segfaults exactly the same with the same gdb results that finish readable backtrace at TinputDeviceManager::createDeviceList() () from /usr/autodesk/maya2020/lib/libExtensionLayer.so