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

@meepzh Thanks for the article, patched with --single-process. However, it seems the option make the adlmapp unable to load the login screen, could you confirm that?

Sorry for the double comment. I just happened upon this article which says:

Note: In Maya 2022.1 and later releases, Maya Application Home may appear blank when running Maya from a network share or in Thin Client mode. To work around this, run Maya with the --single-process command line flag when using those configurations. Alternatively, Application Home can be disabled with the environment variable MAYA_NO_HOME=1.

Either of these seems to resolve the issue for me. Hope this helps!

For fonts, I ran xlsfonts and was unable to see any fonts in the VM. I installed xorg-mkfontscale, ran mkfontscale; mkfontdir; xset fp rehash in /usr/share/fonts, and Helvetica was showing up in xlsfonts as well as Maya. I deleted the fonts.scale and fonts.dir files and rehashed and the fonts still showed up. I think I'll have to recreate the VM and see what's up that's holding up the system from recognizing the fonts. I'm also curious to know if both of the locales are necessary. Hopefully that's helpful for now at least.

As for the main window not appearing, it does seem like there may be something up with licensing like what Brent suggested in the forum post. I see the licensing process consuming a bit of CPU time. But, as expected, it's a bit hard to introspect that to see what's causing issues.

I'd finally gotten around to setting up a barebones VM over the weekend, and I'm seeing the same thing @galaxy0419. I do see the event loop running without strace, so it's a mystery to me as well.. Thanks for updating the package and pinging the forum. Oddly enough, I have Maya 2023.1 working just fine on my personal machine. I am still experiencing the font errors in the VM in spite of the fixes posted below, so hopefully I can make headway on that for this next weekend.

Okay, I found a way to open the app (at least for me), if I run the maya.bin file with "strace -f", somehow the window can be open, but not without the -f option. I created a post on maya forum. Hope someone from the developer team can help with this issue.

Hi @galaxy0419, I haven't found any solutions yet either

Hi guys, have you solved the issue? I tried to update the package to 2023.1 The splash screen stuck at "Showing application home" and disappeared.

Guys, could you add me back to the co-mantaners and authors. I was launched (at 2016) this package and now returned to development.

Hi, thank you for the first fix! So right now i'm facing the same issue as @Evz777, maya splash screen opens without errors in the console but when the splash screen closes the actual software won't open itself and the console won't give any output.

https://www.toptal.com/developers/hastebin/aqihocuxil.yaml

This file was not in the directory. I tried to create an empty one libmd.so , now the initial splash screen starts to run. (https://i.imgur.com/JcwEetE.png) Some preliminary modules are being loaded. (https://i.imgur.com/iK4nP1E.png) But when it comes to the start of the program, nothing happens. (https://i.imgur.com/VqG9Jzi.png) https://www.toptal.com/developers/hastebin/xomeqedomi.yaml

The libtiff error still persists /usr/autodesk/maya2023/bin/maya.bin: /usr/lib/libtiff.so.5: no version information available (required by /usr/autodesk/maya2023/lib/libOpenImageIOMaya.so.2.3) Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.