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

Just as a small, quick update, Autodesk released Identity Manager 1.16.3 on October 27. Part of the release notes (down at the moment) said that it fixed SSO on other linux distros. So decided to test it. I don't see any major change in Arch though, (in redhat it was an intermittent issue).

In my particular case, I work with maya 2025 had to install it in a new Arch machine and it did work, just not on Wayland (maya or SSO) Once I launched it in X11 both worked (I imagine just as it had before).

If anyone is reviewing these notes, note that legacy libraries have to be modified to work with older versions of maya in Arch. For example, to launch maya 2025, you have to not only install libtiff5, but you have to re-do the package to recompile with debug symbols, otherwise maya will crash.

As noted, maya 2025 and 2026 show a black screen in the viewport in Wayland but in X11 they do work.

Hey meepzh,

I'm still new to Arch and the AUR, so apologies about my confusion. I've gotten Maya installed now, thank you :)

Hi voidspacecat, please first download the PKGBUILD for adlmapps and install it using the adlmapps31-31.0.4-0.x86_64.rpm file in the same directory. This package is required by adsklicensing.

Then, download the PKGBUILD for adskidentitymanager and install it using the adskidentitymanager1.15.3.5-1.x86_64.rpm file in the same directory. This package is also required by adsklicensing.

Then, download the PKGBUILD for adsklicensing using git. However, for this package, since you have an older version of adsklicensing, please run git reset --hard HEAD~4 as described on the package web page. This will allow you to install the older version, and the package is required by maya.

Finally, you can install this maya package as you just tried.

If you have any further questions, please reach out to me at the email address on my profile page!

Trying to run 'makepkg' but I keep getting the following error:

[user@hostname-Linux Maya_AUR]$ makepkg ==> Making package: maya 2026.2-1 (Mon 18 Aug 2025 21:09:17 BST) ==> Checking runtime dependencies... ==> Missing dependencies: -> adsklicensing>=15.1.0.12339 ==> Checking buildtime dependencies... ==> ERROR: Could not resolve all dependencies.

I have all of the dependencies in the folder though, here are the files in the folder: adlmapps31-31.0.4-0.x86_64.rpm Maya2026_64-2026.2-2565.x86_64.rpm adskidentitymanager1.15.3.5-1.x86_64.rpm maya.install adsklicensing15.1.0.12339-0-0.x86_64.rpm MayaUSD2026-202507022244-1cbb7f7-0.33.0-1.x86_64.rpm application-home-workaround.patch package.zip LookdevX-1.9.0-2026.el8.x86_64.rpm PKGBUILD

Why is this happening? I can't figure it out.

It seems that Maya now provides its own copy of libffi6 in usr/autodesk/maya2026/lib/el9/libffi.so.6, so the libffi6 AUR package is not required anymore. Sorry for not catching this sooner. I've reviewed the dependencies and updated them.

just me or is libffi6 currently broken? Currently failing the checks shown here: https://aur.archlinux.org/packages/libffi6#comment-1028195

I see, apologies. I must have misremembered how the licensing login was triggered. After logging out of my Autodesk account through Maya, I saw the same webkit issue that you had seen. I've added the dummy rpm back to pkgrel 2 of adsklicensing.

@meepzh

Ultimately I installed the 15.5 version of the adsk licensing, which I believe is the same version as the preJune update. (The only different version of something I attempted in my testing was adlmapps.)

Fortunately, after you sign in once it appears that it caches everything and just works from then on out.

I didn't ever get it to work with Vivaldi. The logs would say that it was working, but it would never hook into an existing instance of the browser or launch the browser itself.

I'm actually looking through the build files/scripts and I can't see where it creates the dummy RPM.

@Tellik, that's strange. Did you install the 15.5 version or the 15.4 version of adsklicensing? I don't seem to have issues with either, but I did notice that Autodesk flagged a missing dependency fix as part of their patch notes, and I didn't have any issues removing the webkit2gtk3 RPM package, so I removed it. Instead, it seems like they introduced a dependency on openssl-1.1. But perhaps I was mistaken in removing the dummy RPM.

Thank you for the note about Vivaldi, I'll add it to the pinned comment.

I noticed that this package was updated recently, and while it worked flawlessly before the June 2026 update, it is now breaking.

When clicking on Sign in with account, it gives a Licensing error:

2025-06-08 22:03:11: ====== BEGIN MAYA CLM LICENSE DIAGNOSTICS (level 2) ====== 2025-06-08 22:03:11: INFO: MAYA VERSION: Autodesk MAYA 2026.1 2025-06-08 22:03:11: INFO: Desktop Licensing Runtime Version: 9.5.0.53 2025-06-08 22:03:11: INFO: Desktop Licensing API version in Maya: 9.5.0.53 2025-06-08 22:03:11: INFO: initialize: GetInstance (Success) 2025-06-08 22:12:52: INFO: Received LicenseUpdateCallback for Maya 2026 (ADLSDK_UPDATE_REASON_LICENSE_UPDATE): NOT Authorized 2025-06-08 22:12:52: ERROR: Error Information: Maya 2026 : [IDSDK] 3073: The PC has not installed WebKitGTK yet, please install WebKitGTK. 2025-06-08 22:12:52: ERROR: adlsdkAuthorize returned with error code: ADLSDK_STATUS_LICENSE_CHECKOUT_ERROR 2025-06-08 22:12:52: ERROR: checkinLicense: unable to release authentication handle 2025-06-08 22:12:52: INFO: shutdown: normal exit

At first I thought this was due to a version error with adlmapps, but that didn't fix it. It's on a clean install, one of the first things I've attempted to install on a fresh system. I know that it has a post script that creates a dummy webkit2gtk3 RPM package, but rpm-tools aren't a dependency. I installed this and reattempted to install, but that failed again.

Instead, I had to manually create the WebKitGTK dummy RPM and install it using a script I found. This allows it to launch and open up firefox to allow a login. I'm thinking that something in the build script is breaking that prevents the dummy RPM from being created.

One other thing of note, is that normally I use Vivaldi browser, and when that is set to default I have issues with it launching/connecting to the browser to sign in and launch.