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

Hi @meepzh. Thanks for updating the package, I've added you to all my packages. Could you add me back to the maya package as comaintainer? I will still update the package when I'm free.

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

I am trying to install 2022.3. Fixed libtiff and libmd by methods suggested below. Maya opens blank screen without anything. Luckily found that Ctrl+n opens new project with working UI. I had to install libffi6 from aur to get rid of error from maya script console. However, all of the methods below for fixing font problem doesn't work for me.

libxcrypt-compat seems to be a dependency now since the glibc-2.35-2 update. This resolves the error:

maya.bin: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

I spent a long time debugging a missing font issue.

If you're still running into issues like

Failed trying to load font : -*-helvetica-bold-r-normal-*-11-*-*-*-*-*-iso8859-1 // 

Make sure you've got the correct locales enabled! For me it was the following (in /etc/locale.gen)

en_GB ISO-8859-1
en_US ISO-8859-1

Afterwards, run sudo locale-gen and reboot.

Hope this helps.

For the Helvetica font errors, I ran the xset commands with superuser permissions and that seemed to resolve the issue. All documentation seems to not require that permission level, so I'd be keen to know what might have gone on there...

xset +fp /usr/share/fonts/100dpi
xset +fp /usr/share/fonts/75dpi
xset fp rehash

@starget A symlink from where ?

So i managed to install maya 2022.2 the installation when as intended thanks to the fix provided by ozzy and Mo6eb. The only thing that keeps bugging me is a constant error at the scrip editor

// Error: Failed trying to load font : --helvetica-bold-r-normal--11-----*-iso8859-1 //

This seems strange to me because i had installed xorg-fonts-100dpi, 75dpi xorg-fonts-misc xorg-fonts gsfonts adobe-source-code-pro-fonts xorg-xlsfonts and xorg-fonts-type1. Maybe this happened because i installed xorg-fonts-100dpi,and 75dpi packages after installing maya itself but i am not really sure.

Ended discovering people in damn old forums with the same problem, but in debian and ubuntu unfortunately the workarounds that they provide didn't help.

Does someone have the same problem as me? if so maybe there is a workaround for it in arch?

EDIT: Making a symlink to my /usr/bin/ directory solved this issue

EDIT 2: Symlink from /usr/autodesk/maya2022/bin/maya2022. Thanks to @Tangue for pointing that i didn't specify the symlink source lol

@Mo6eB thanks for the info! That is great, but the fix I tested is even better, you can just create empty libmd.so file in /usr/autodesk/maya<version>/lib/ directory doing it by touch command and it also works then because maya reads these libs earlier than system libs and when the libmd is empty, it doesn't crash.

sudo touch /usr/autodesk/maya2022/lib/libmd.so

Maybe it is good idea to add that touch command to PKGBUILD?

@Mo6eB Thanks for letting us now, yes while removing the simlink libmd.so it's working great. But libmd.so is requiere for several applications like wacom drivers, mpd, smbclient, a lot of KDE apps (including dolphin). So I wonder what problem it could create.

Also, @theMaizeOfficial, sorry if the way I wrote seems offensive, I didn't mean it that way.