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 licensing issues for Maya 2025+.

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. You will also need the 1.15 update to the Autodesk Identity Manager found under 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.

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

It seems like jimmy_christensenMSURY was able to get Maya 2026 working on Ubuntu in the forum thread here: https://forums.autodesk.com/t5/maya-forum/can-t-login-with-autodesk-id-sso-on-linux/m-p/13445338#M103026 though the forum is down for maintenance this weekend. It involves a fake RPM for webkit2gtk3 and /etc/pki/tls/certs/ca-bundle.crt. I'll try and reproduce his work for Arch.

edit: I am able to get it working. Will update the packages...

To reiterate what jimmy_christensenMSURY has found, it appears that the licensing software uses the rpm command to check for webkit2gtk3. I haven't confirmed if it specifically needs webkit2gtk3, but I do know that the version number of webkit2gtk3 is not checked because a 1.0.0 dummy package satisfies the requirements. The adsklicensing package installs a dummy version of this rpm package for you. The Arch version of webkit2gtk is used by the identity manager, so it is a real requirement. Upon accomplishing that, the licensing software will search for /etc/pki/tls/certs/ca-bundle.crt. As jimmy_christensenMSURY described, symlinking the operating system's crt file satisfies this requirement. I also found that the identity manager crashes until version 1.15, which as Autodesk describes, updates dependencies, which likely aligns with Arch's versions. If I recall correctly, much of this information is relayed by the logs from Maya CLM. And that is sufficient to get Maya licensing working again.

Maya 2026 released! maya2025 may be stable now!

Anyway, could the adsklicensing not working and the SSO(login) not working be two different problems ?

To clarify further my post earlier:

• I manage several workstations and servers for visual FX. I use Maya almost daily. I have servers/workstations with redhat/ubuntu/arch/windows/Mac and a couple of other more esoteric environments. Have installed Maya on all for years. My favorite environment is Arch :)

As of March 2025, I believe Maya for linux, whether 2025 or earlier, only works out of the box in redhat. Autodesk has published how-tos to install maya in Ubuntu, sure, they have done it for years. It used to work for Maya 2024 in ubuntu, but not anymore. How do I know? Because they have the same errors we Arch peeps are having:

https://forums.autodesk.com/t5/maya-forum/installing-maya-on-ubuntu-20-04-6-lts/td-p/13013969

I reproduced the above issues and came to the same solution, just use redhat if you really need Maya up and running in linux.

I think I can summarize it as this: Autodesk is trying to enforce continuous updated licensing (probably to combat fraud/piracy) and support tools, even for 2024 or earlier versions, which breaks them if the underlying environment doesn't have all the libraries that are quite old now. I have run into this many times over the years. Usually fonts are broken, or character sets, or ssl sockets, but now, I think a library or libraries needed by licensing are not working outside of redhat.

Here, this is usually what people encounter:

https://forums.autodesk.com/t5/maya-forum/installing-maya-2025-2-on-ubuntu-22-04/td-p/12937606

My post jumped over the above details to kind of argue that (one of) the culprit(s) maybe glibc. I think as long as Autodesk, doesn't make Autodesk licensing work with newer libraries, we will be stuck in this. This is really my only point. That Autodesk has issues with library compatibilities that are newer than what they are deploying and targeting for.

To clarify my earlier post - I was specifically investigating why Maya 2024 stopped working on Arch Linux after a glibc 2.41 update.

Its not so simple because maya2024 was working untill some weeks ago. Plus maya2025 works on ubuntu it seems, look my link below.

After reading X3bz's comment, I also decided to give it a go, as I have several testing environments and machines to check this.

I suspect he is right, and any possible tests or solutions are going to be probably harder or slower performance than outright installing a VM or another distro.

In the same arch machine I have, I have redhat9 and I was bothered of why maya 2025 just works in redhat. Well, redhat ships with glibc-2.34 and only applies security updates to it, that is it (well along with earlier versions of openssl and icu, which we haven't even mentioned). So I am assuming any autodesk binaries and libraries assume that all those versioned libraries are there.

Warning for whoever is reading this, you should not even contemplate attempting this: Any fiddling with glibc will bring down your system. I am comfortable trashing my arch partition, so I tried rolling back glibc just to see if it would bring maya back, after all, it was working in arch at some point. As I did, systemd did not work anymore, which you can imagine what that entails: a borked system. However, maya did attempt to launch, but as systemd did not work anymore, it was kind of moot, as most services were broken now. I had to bring my system back with an arch install image. Next step would be rolling back systemd and other dependencies. However, I don't think that is advisable on a rolling distro.

I posted the above because of this: Anyone who wants to test this, probably needs an image of Arch as of last year before it broke, probably December 2024 at the latest. However, if you are going to do that, you will not be able to have any security updates or functional updates. And at that point, might as well have a Long Term distro not a rolling releases one, and as far as I know, from the long term ones only redhat works with maya 2025. Fedora, rocky, ubuntu, all do not launch maya 2025, probably because of the new libraries or newer kernels or both.

So if you really need maya 2025, I think the best you can do is install another partition of redhat9, as rocky or fedora will not cut it. Your other options are probably, doing a Virtual Machine with an old arch image of 2024 ( to work with maya 2024, because if you want maya 2025, you probably will have to attempt to replicate redhat9 library versions with arch) or maybe a container that has glibc (ideally glibc-2.34), and other old libraries as needed, but even if you pull it off, you will be missing redhat's security/bug enhancements to them.

I don't like this more than you do, but I do think the best approach is to install redhat 9 for full performance. Hopefully maya 2026 will address this, but I would not hold my breath.

I did some investigation on this while my Maya license was active, memory might be a bit fuzzy and not on that specific computer. What I found out was that it's related to the glibc 2.41 update which caused issues for other software aswell. Can be verified by downgrading it and launching Maya. Would not recommend leaving it as who knows what else will break.

Some things I tried to resolve it was:

1. Tried unpacking the older glibc into a dir and launch Maya with LD_PRELOAD
2. Tried patchelf --clear-execstack on all executable files for Maya and AdskLicensing and ADLM
3. Compile openssl-1.0.1 and replace it where used in AdskLicensing, ADLM and Maya

First and second approaches didn't lead anywhere but compiling openssl got me further, I could manually register Maya and such the the first hurdle was over. I ran into some other problem making Maya unable to launch. Didn't get past the next hurdle before my Maya license expired.

Hopefully someone can pick it up from here and figure it out or maybe Maya 2026 which should launch soon will work.

Maya 2024 did stop working for me as well, and Maya 2025 had never worked on Arch Linux due to the licensing software, as far as I'm aware. There are some links at the top of the pinned comment. I'll try to get some time to test tonight or this weekend.