Anyway, could the adsklicensing not working and the SSO(login) not working be two different problems ?
Search Criteria
Package Details: maya 2024.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/maya.git (read-only, click to copy) |
---|---|
Package Base: | maya |
Description: | Autodesk Maya 3D Animation, Modelling, Simulation and Rendering Software |
Upstream URL: | http://www.autodesk.com/products/maya/overview |
Keywords: | 3d Autodesk Maya |
Licenses: | custom |
Submitter: | aquarius |
Maintainer: | meepzh (ttc0419, aquarius) |
Last Packager: | meepzh |
Votes: | 20 |
Popularity: | 0.000121 |
First Submitted: | 2016-07-25 19:14 (UTC) |
Last Updated: | 2023-12-26 22:01 (UTC) |
Dependencies (20)
- adsklicensingAUR
- audiofile (audiofile-gitAUR)
- glu (glu-gitAUR)
- gst-plugins-base-libs (gst-plugins-base-libs-gitAUR)
- gtk2 (gtk2-patched-filechooser-icon-viewAUR)
- libffi6AUR
- libjpeg6-turbo
- libpng15AUR
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libtiff5AUR (libtiff5-hylafaxplusAUR)
- libtool (libtool-gitAUR)
- libxaw (xawmAUR)
- libxcrypt-compat
- libxp
- libxtst
- ncurses5-compat-libsAUR
- nss (nss-hgAUR)
- xorg-fonts-100dpi
- xorg-fonts-75dpi
- opencl-driver (opencl-nvidia-410xxAUR, amdapp-sdkAUR, opencl-nvidia-440xxAUR, vc4cl-gitAUR, opencl-nvidia-430xxAUR, beignetAUR, beignet-gitAUR, intel-openclAUR, clvk-gitAUR, mesa-wsl2-gitAUR, intel-compute-runtime-legacy-binAUR, opencl-nvidia-340xxAUR, intel-compute-runtime-gitAUR, intel-compute-runtime-legacyAUR, opencl-nvidia-550xxAUR, opencl-legacy-amdgpu-proAUR, mesa-gitAUR, opencl-nvidia-390xxAUR, opencl-amdAUR, opencl-nvidia-470xxAUR, opencl-nvidia-525xxAUR, opencl-510xx-nvidiaAUR, opencl-nvidia-535xxAUR, opencl-nvidia-teslaAUR, opencl-rusticl-mesa-minimal-gitAUR, intel-compute-runtime-binAUR, amdonly-gaming-opencl-rusticl-mesa-gitAUR, opencl-nvidia-vulkanAUR, opencl-nvidia-betaAUR, intel-compute-runtime, intel-oneapi-compiler-shared-runtime, opencl-clover-mesa, opencl-nvidia, opencl-rusticl-mesa, rocm-opencl-runtime) (optional) – OpenCL support
Required by (13)
Sources (2)
jackar commented on 2025-03-18 19:50 (UTC)
mac666er commented on 2025-03-18 18:38 (UTC)
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.
X3bz commented on 2025-03-18 14:20 (UTC)
To clarify my earlier post - I was specifically investigating why Maya 2024 stopped working on Arch Linux after a glibc 2.41 update.
jackar commented on 2025-03-18 00:09 (UTC)
Its not so simple because maya2024 was working untill some weeks ago. Plus maya2025 works on ubuntu it seems, look my link below.
mac666er commented on 2025-03-17 19:38 (UTC) (edited on 2025-03-17 19:40 (UTC) by mac666er)
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.
X3bz commented on 2025-03-16 23:50 (UTC)
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:
- Tried unpacking the older glibc into a dir and launch Maya with LD_PRELOAD
- Tried patchelf --clear-execstack on all executable files for Maya and AdskLicensing and ADLM
- 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.
meepzh commented on 2025-03-13 22:12 (UTC)
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.
jackar commented on 2025-03-13 20:49 (UTC) (edited on 2025-03-14 01:18 (UTC) by jackar)
Maya 2025.3 is out, does it help ?
On Fedora look like it worked, can this help ?
https://forums.autodesk.com/t5/maya-forum/can-t-login-with-autodesk-id-sso-on-linux/td-p/12696079
https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/5ZZjP3R0R7hzPyhDYkd8IS.html
Is it confirmed that 2024 stoped working like Asatu says ?
Edit: the autodesk guy says it fail to find the browser?
Edit2: https://help.autodesk.com/view/MAYAUL/2025/ENU/?guid=GUID-3E0A3A36-B1C2-4B91-994B-731C672D9694
AsaTU commented on 2025-03-11 23:34 (UTC) (edited on 2025-03-11 23:35 (UTC) by AsaTU)
Hi, Maya 2024 was working for around 2 months, then I started getting licensing errors. I decided to reinstall adsklicensing, but now the service doesn't start.
sudo /opt/Autodesk/AdskLicensing/13.3.1.9694/helper/AdskLicensingInstHelper register -pk 657P1 -pv 2024.0.0.F -el EN_US -cf /var/opt/Autodesk/Adlm/Maya2024/MayaConfig.pit
adsklicensing.service - Autodesk Licensing Service
Loaded: loaded (/usr/lib/systemd/system/adsklicensing.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2025-03-12 00:12:59 CET; 18min ago
Duration: 35ms
Invocation: f3bbbdd905cb4beeb3ce6803eab8c1c9
Main PID: 943 (code=exited, status=1/FAILURE)
mar 12 00:12:59 asapc systemd[1]: adsklicensing.service: Scheduled restart job, restart counter is at 5.
mar 12 00:12:59 asapc systemd[1]: adsklicensing.service: Start request repeated too quickly.
mar 12 00:12:59 asapc systemd[1]: adsklicensing.service: Failed with result 'exit-code'.
mar 12 00:12:59 asapc systemd[1]: Failed to start Autodesk Licensing Service.
After manually trying to register maya, I get this error:
Post "http://127.0.0.1:46795/api/v1/feature": dial tcp 127.0.0.1:46795: connect: connection refused
I tried killing my firewalld service, thinking it might block it, but it did not work. It came out of the blue and I'm not sure what caused all this. Also tried setting up maya in an Ubuntu distrobox, and while it had other issues this weird "connection refused" error didn't appear. Any ideas?
meepzh commented on 2024-09-05 08:36 (UTC) (edited on 2024-12-13 07:27 (UTC) by meepzh)
I've tested with Maya 2025.2 and adsklicensing-14.4.0.11537, and it doesn't seem like the licensing software is crashing anymore, but there's still no luck unfortunately...
2024/09/05 01:27:12.371 [W,2159] Unable to set host window handle to IDSDK. But continue trying Login
2024/09/05 01:27:12.681 [W,2159] IdsdkEngine::onLogin IDSDK login return error 3070 . callId ( 1908981241 )
edit: Same with adsklicensing-15.0.0.12136 and 15.1.0.12339.
Pinned Comments
meepzh commented on 2022-04-08 22:36 (UTC) (edited on 2024-11-09 17:44 (UTC) by meepzh)
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:
Packages/adlmapps*.rpm
to build adlmappsPackages/adsklicensing*.rpm
to build adsklicensingPackages/Maya*.rpm
to build this packagePackages/package.zip
to build maya-arnoldPackages/Bifrost*.rpm
to build maya-bifrostPackages/AdobeSubstance3DforMaya*.rpm
to build maya-substance, if you don't want to download directly from AdobePackages/MayaUSD*.rpm
to build maya-usd-bin, if you don't want to download directly from GitHubPackages/LookdevX.rpm
to build maya-lookdevxPackages 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.(source)
If you are still seeing font errors, you can try one or more of the following:
xorg-mkfontscale
and runmkfontscale
in/usr/share/fonts
. Then re-run thexset
commands above.xset
commands with superuser permissions.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