Arch Linux User Repository

Many thanks to ttc0419 for getting this set up and for writing these instructions originally. Many thanks to jimmy_christensenMSURY for fixing the Maya 2025+ licensing.

Installation Instructions:

Go to your Autodesk account Products and Services and save the Linux tgz file to any location of your choice. You will also need v1.15 of the Autodesk Identity Manager from Product Updates.

Extract the tgz files 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 files to build some other packages as well:

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

Packages 1 and 3 are required to use Maya and 5 to 9 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 you may need to set a different default browser as Tellik experienced.

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.

If you see a black screen, check that Wayland is disabled: https://forums.autodesk.com/t5/maya-forum/maya-2025-2026-on-linux/td-p/13617041

Cheers

@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

@costashatz https://help.autodesk.com/view/MAYAUL/2018/ENU/?guid=GUID-D2B5433C-E0D2-421B-9BD8-24FED217FD7F

I think this might help, i saw some one here was posting on the autodesk forum about the libiff but this has all the other info if you need it. its for 2018 but im sure if there is is this one there will be a 2022 version of this link some where, if this helps id like to know the results and process. cheers

i think i just accidentally deleted my comment, for me its coming to a screaming halt searching for libtiff.so.5 then displaying Segfault (a bunch of crap only aliens can read) (Core Dumped). so to me it seems like those two issues are going hand in hand together. i am just trying to solve it because i need this system to be up and running with maya... like yesterday lol

@theMaizeOfficial the libtiff issue is different from the segfault. Check here: https://bugs.archlinux.org/task/71330?project=1&string=libtiff. Also the libtiff issue does not prevent you from using Maya.