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 Products and Services page and save the Linux tgz file. You will also need v1.15+ of the Autodesk Identity Manager from Product Updates.

Extract the tgz files.

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/AdpSdk/adp-desktop-sdk.zip to build adp-desktop-sdk
2. (required) Packages/AdskIdentityManager/adskidentitymanager*.rpm to build adskidentitymanager
3. (required) Packages/Licensing/adsklicensing*.rpm to build adsklicensing
4. (required) Packages/Maya*.rpm to build this package
5. (optional) Packages/package.tgz 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 to 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

Hi jackar, since the PKGBUILDs are stored in git, you can revert to an older version of all of these packages, and they should work just as well. You would not need AdpSdk, but from what I see, AdpSdk is provided by Maya 2026.3, which is the only version that the Autodesk website allows me to download. You can also install the latest version of adsklicensing, adskidentitymanager, and adp-desktop-sdk and use that with the older Maya packages.

@meepzh Can u make a little guide to install 2026 ? what are the differences ? is AdpSdk required there ? will these installer packages works ? Im normally happy that the last version works, but many uses the former.

Thanks for flagging, Mo6eB. That symlink is handled by the adsklicensing package. Are you seeing it missing with that package installed?

In order to use user licenses, AdskIdentityManager needs to connect over HTTPS to Autodesk's servers. It looks for the root CA certificate bundle in the RHEL standard path /etc/pki/tls/certs/ca-bundle.crt , but on Arch Linux it is in /etc/ssl/certs/ca-bundle.crt . You need to make a symlink at the RHEL path.

Otherwise AdskIdentityManager shows as a black window and an error along the lines of

"CurlInfoResponseCode" : 77

is written to the log file with no other details.

Looks like latest 2027 from autodesk has slightly different rpm. e34435c600c56ed73bdf1259bb2bcc387acea30fc172b8e7c8f39bc53183712dbf1a1d4adf2c380afe98dc1055bb5f992c63a19d193f56096a5e707284232475 Maya2027_64-2027.0-16168.x86_64.rpm

Thanks meepzh. Tried fresh install today (CachyOS), so am using both of those. I get an x11 window prompting acccount login, but never opens a secondary browser, only the fail window.

checking ~/.local/share/Autodesk/Identity Services/Log/IdServices.log

I do wonder about these...

2026-03-26T10:39:49.871Z [AdskLicensingAgent:26522, 140009822746304] [IdSDKPlugin INFO] Preparing to send request Login
2026-03-26T10:39:49.871Z [AdskLicensingAgent:26522, 140009822746304] [IdSDKPlugin INFO] IPC use the timed mutex, the timeout duration is: 3000ms
2026-03-26T10:39:49.872Z [AdskLicensingAgent:26522, 140009822746304] [IdSDKPlugin INFO] Sending request Login with 24855d:3h:14m:7s timeout
2026-03-26T10:39:49.912Z [AdskIdentityManager:26538, 140532001007296] [IdIPCServer INFO] Request Login received from product AdskLicensingAgent::26522:-6891075876065460223
2026-03-26T10:39:49.912Z [AdskIdentityManager:26538, 140532001007296] [IdIPCServer INFO] Handling request Login asynchronously from product AdskLicensingAgent::26522:-6891075876065460223
 {
    "LoginMode" : 0,
    "ParentWindow" : 0,
    "ShowDialogAsModeless" : true
}
2026-03-26T10:39:49.912Z [AdskIdentityManager:26538, 140532001007296] [IdIPCServer INFO] Posting asynchronous request Login from product AdskLicensingAgent::26522:-6891075876065460223 to execute in main thread
2026-03-26T10:39:49.912Z [AdskIdentityManager:26538, 140533324844224] [IdIPCServer INFO] Executing asynchronous request Login from product AdskLicensingAgent::26522:-6891075876065460223 in main thread
2026-03-26T10:39:49.912Z [AdskIdentityManager:26538, 140533324844224] [IdIPCServer INFO] LoginMode is set: 0
2026-03-26T10:39:49.912Z [AdskIdentityManager:26538, 140533324844224] [IdIPCServer INFO] Finished executing asynchronous request Login from product AdskLicensingAgent::26522:-6891075876065460223 in main thread
2026-03-26T10:39:49.927Z [AdskIdentityManager:26538, 140532001007296] [IdIPCServer INFO] Request Login finished from product AdskLicensingAgent::26522:-6891075876065460223
2026-03-26T10:39:49.927Z [AdskIdentityManager:26538, 140532001007296] [IdServicesCore.Proxy INFO] Database init successful.
2026-03-26T10:39:49.928Z [AdskIdentityManager:26538, 140532001007296] [IdServicesCore.Proxy WARN] Proxy information data is NOT restored. detail: 3046
2026-03-26T10:39:49.928Z [AdskIdentityManager:26538, 140532001007296] [IdServicesCore.ADP INFO] Preparing to call ADP track event for Command Track Event [AdskLicensingAgent] for Login.
2026-03-26T10:39:49.928Z [AdskIdentityManager:26538, 140532001007296] [IdServicesCore.ADP WARN] Journey-id is empty, JourneyId attribute will not be set for ADP component event
2026-03-26T10:39:49.968Z [AdskLicensingAgent:26522, 140009822746304] [IdSDKPlugin INFO] Finished request Login. Result from server: Failed, status = 3029

I was having the same sign in issue just now when there was a mismatch between Autodesk Licensing and Autodesk Identity Manager. I was testing Autodesk Identity Manager 1.18.1.2 while still using Autodesk Licensing 16.0.3.14414. It was only when I updated to 16.2.5.15199 and restarted the Autodesk Licensing service that the sign in process worked again. It might be worthwhile to check those versions and restart that service just to be safe.

@tasmiley did you ever find out the cause of this? I have the same, currently beating my head against the wall...

Gets to 'Sign in with your Autodesk ID' in x11 window, but then does not open a browser window, and fails.

Regarding Maya running on Wayland. I have found a compromise solution to this problem and would like to share it with you. This solution works for me for Maya 2025.3 on Distrobox Rocky 9.

Switch Viewport rendering from Viewport 2.0 to Legacy. To do this, add the following line to the Maya.env file: MAYA_ENABLE_DEPRECATED_VIEWPORT=1. Legacy is hidden option in Maya you can't find it in Preferences without this code line.

To ensure that Legacy Viewport starts automatically when Maya launches, make sure you have the following settings:

1. Windows -> Preferences -> Display -> Viewport 2.0 -> Rendering engine -> OpenGL - Core Profile (Compatibility).

2. Windows -> Preferences -> Display -> Viewport 2.0 -> Default viewport -> Legacy Default Viewport.

3. Viewport -> Renderer -> Legacy Default Viewport.

4. Exit the program for the settings to be saved.

For those who create animations, you may encounter freezes in the viewport playback. To make animations in the viewport smoother, check the box here:

Windows -> Preferences -> Cached Playback -> Cache smooth meshes. Additionally, you can experiment with other settings that may help you.

This solves the black screen problem, but the UV editor is still black. I haven't found a solution to this problem yet. I tested Rigging, Animations, and Arnold Rendering — everything works fine. After 1-2 hours of operation, the Viewport starts to lag due to cache accumulation. Restarting the program solves this problem and the viewport becomes smooth again.

Hm, I'm not sure what to make of those messages, sorry. Just taking some guesses, maybe there's a browser issue or misplaced configuration file or maybe some websites aren't accessible, though all config files should be coming in where they should be automatically.