Package Details: maya 2023.1-3

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 (galaxy0419, aquarius)
Last Packager: meepzh
Votes: 19
Popularity: 0.006552
First Submitted: 2016-07-25 19:14 (UTC)
Last Updated: 2022-07-03 04:26 (UTC)

Pinned Comments

meepzh commented on 2022-04-08 22:36 (UTC) (edited on 2022-07-03 04:38 (UTC) by meepzh)

Installation Instructions:

Many thanks to galaxy0419 for getting this set up and for writing these instructions originally.

Autodesk has updated the EULA for the Autodesk Education version. See here for more info.

To get the latest version of Maya, go to your account page and click "Products and Services" and download the Linux tgz file.

Extract the tgz file.

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. MayaConfig.pit for product activation
  2. Packages/adlmapps*.rpm to build adlmapps
  3. Packages/adsklicensing*.rpm to build adsklicensing
  4. Packages/Maya*.rpm to build this package
  5. Packages/package.zip to build maya-arnold
  6. Packages/Bifrost*.rpm to build maya-bifrost
  7. Packages/AdobeSubstance3DforMaya*.rpm to build maya-substance
  8. Packages/MayaUSD2023*.rpm to build maya-usd

Note: Packages 2 and 3 are required to use Maya and 6 to 9 are plugins that can be installed when needed.

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.

Launch Maya and log into your Autodesk account or enter your product serial to check out a license.

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

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

Cheers

Latest Comments

galaxy0419 commented on 2022-08-01 12:51 (UTC) (edited on 2022-08-01 12:58 (UTC) by galaxy0419)

After months of contacting developers, they finally added libtiff symbol versioning support

Submitted deletion request for libtiff-maya-git and will remove the dependency in the next release.

meepzh commented on 2022-07-03 04:28 (UTC)

@galaxy0419, thanks! I'm seeing no such issue however. I've logged out and logged back in several times without issues.

@Evz777, thanks for the feedback! I've added that package as an optional dependency. Thanks!

Evz777 commented on 2022-06-28 05:29 (UTC)

Thank you very much @meepzh, now everything is working. By the way, the problem of the libtiff library was also solved with the help of this package https://aur.archlinux.org/packages/libtiff-maya-git

galaxy0419 commented on 2022-06-28 04:48 (UTC)

@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?

meepzh commented on 2022-06-27 09:05 (UTC)

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!

meepzh commented on 2022-06-27 08:59 (UTC)

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.

meepzh commented on 2022-06-20 14:12 (UTC)

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.

galaxy0419 commented on 2022-06-20 06:35 (UTC)

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.

Evz777 commented on 2022-06-19 07:37 (UTC)

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

galaxy0419 commented on 2022-06-18 07:15 (UTC)

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.

aquarius commented on 2022-06-10 14:50 (UTC)

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

Redwolf commented on 2022-06-08 08:07 (UTC)

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

Evz777 commented on 2022-06-08 06:51 (UTC)

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.

meepzh commented on 2022-06-07 19:24 (UTC)

@Redwolf, this looks like it could be similar to the libmd discussion below us. I thought that I added a fix to the PKGBUILD. Do you see the following file: /usr/autodesk/maya2023/lib/libmd.so ? If not, does creating it (an empty file would do) resolve the issue?

@Evz777, please see the discussion with Redwolf, as it seems to be similar.

Thanks!

Evz777 commented on 2022-06-07 13:30 (UTC)

I have now managed to install the libpng15 package. Then I managed to launch the licensing window, where I entered the username and password for the autodesk account. Then the program gives this error:

/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) ./maya2023: line 203: 67786 Segmentation fault (core dumped) /usr/autodesk/maya2023/bin/maya.bin

Evz777 commented on 2022-06-06 11:20 (UTC)

Yes, you are one hundred percent right @meepzh, after your advice, I was also convinced of this. Libpng15 does not really conflict with version 1.6, but with versions that are younger. I also have libpng12 version 1.2.59 installed. But with this in mind, the problem has not been fixed yet. Since I can't delete version 12 either. The latest version of davinci-resolve uses this library for its work. Therefore, the question is still the same is there at least some way to install libpng15 in this case?

Redwolf commented on 2022-06-05 09:05 (UTC)

Thank you @meepzh for the answer.

This is what i'm currently getting as an output:

https://i.gyazo.com/6cdc6ed90c0f8a5e1151a0c75fb88982.png

here is also a stack trace in case you would need it.

https://pastebin.com/Ny2kjDEq

meepzh commented on 2022-06-05 07:17 (UTC)

@Redwolf, unfortunately that message isn't particularly informative. Could you try running Maya with GDB please? Perhaps you can find some more useful messages that way: https://knowledge.autodesk.com/support/maya/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-get-a-Stack-Trace-s.html I don't expect the nvidia version to be the cause as I have the same version, but you never know.

Redwolf commented on 2022-06-04 21:08 (UTC) (edited on 2022-06-04 21:13 (UTC) by Redwolf)

Hi, i'm running endeavourOS, i've installed maya2022 and it's running fine then i've tried to install maya2023 but when i try to run it, i'm getting:

line 203: 147474 Segmentation fault (core dumped) /usr/autodesk/maya2023/bin/maya.bin

could my nvidia driver version be the cause? I'm running the version 515.43.04

Thank you for your help.

meepzh commented on 2022-06-01 18:42 (UTC)

@Evz777, I've just gotten back to my Arch machine, and it seems like libpng and libpng15 should be able to coexist. libpng15's PKGBUILD indicates that it only conflicts with libpng packages with a version less than 1.6. It might be worth confirming that your Manjaro installation is compatible with those forms of exclusions. Hope this helps!

Evz777 commented on 2022-05-26 09:17 (UTC)

Thank you very much for @meepzh's answer, I'm sure it brings me closer to a solution. I'm a little afraid to delete the 1.6 package, since more than 20 programs depend on it, including blender, chromium, vlc, etc. I use all of them every day. Is it possible to install the libpng15 package in arch linux without removing the 1.6 package ? Or maybe there is a way to tell Maya to use package 1.6 ? Or is it now only up to the next version of the maya update?

meepzh commented on 2022-05-26 04:16 (UTC) (edited on 2022-05-26 04:22 (UTC) by meepzh)

Hey @Evz777! I'm not particularly familiar with Manjaro, but I would expect that libpng 1.5 conflicts with libpng 1.6 because they are the same package. Is there any way to install libpng 1.5 regardless, like removing libpng 1.6? Do you have packages that require libpng 1.6? I'm not able to investigate much further for the next few days without a Linux box, but hopefully that sends you down the right direction. Also please reserve use of the out-of-date flag for when Maya itself has an update. Thanks!

Evz777 commented on 2022-05-25 10:08 (UTC) (edited on 2022-05-25 10:08 (UTC) by Evz777)

Hello! Thank You for the package. I am installing the maya 2023 program on linux manjaro latest version. I know that to run the program, the libpng15 1.5.30-1 library must be installed because the program will not work without it. However, libpng version 1.6.31 is already installed on my linux version and I cannot install the previous version because it conflicts with the newer version. What ways can help me run the program under these conditions? Now it refuses to start giving out a message:

❯ cd /usr/autodesk/maya2023/bin ❯ ./maya2023 /usr/autodesk/maya2023/bin/maya.bin: error while loading shared libraries: libpng15.so.15: cannot open shared object file: No such file or directory ❯

galaxy0419 commented on 2022-04-13 05:13 (UTC)

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.

meepzh commented on 2022-04-08 22:36 (UTC) (edited on 2022-07-03 04:38 (UTC) by meepzh)

Installation Instructions:

Many thanks to galaxy0419 for getting this set up and for writing these instructions originally.

Autodesk has updated the EULA for the Autodesk Education version. See here for more info.

To get the latest version of Maya, go to your account page and click "Products and Services" and download the Linux tgz file.

Extract the tgz file.

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. MayaConfig.pit for product activation
  2. Packages/adlmapps*.rpm to build adlmapps
  3. Packages/adsklicensing*.rpm to build adsklicensing
  4. Packages/Maya*.rpm to build this package
  5. Packages/package.zip to build maya-arnold
  6. Packages/Bifrost*.rpm to build maya-bifrost
  7. Packages/AdobeSubstance3DforMaya*.rpm to build maya-substance
  8. Packages/MayaUSD2023*.rpm to build maya-usd

Note: Packages 2 and 3 are required to use Maya and 6 to 9 are plugins that can be installed when needed.

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.

Launch Maya and log into your Autodesk account or enter your product serial to check out a license.

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

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

Cheers

oljik commented on 2022-03-20 10:29 (UTC)

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.

meepzh commented on 2022-03-11 15:30 (UTC)

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

okamidash commented on 2022-03-07 23:20 (UTC)

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.

meepzh commented on 2022-01-29 07:24 (UTC)

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

Tanghe commented on 2021-12-02 09:05 (UTC) (edited on 2021-12-02 09:35 (UTC) by Tanghe)

@starget A symlink from where ?

starget commented on 2021-10-13 12:00 (UTC) (edited on 2021-12-13 16:34 (UTC) by starget)

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

ozzy1202 commented on 2021-09-20 08:11 (UTC) (edited on 2021-09-20 08:22 (UTC) by ozzy1202)

@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?

Cuissedemouche commented on 2021-09-19 11:36 (UTC)

@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.

Mo6eB commented on 2021-09-17 11:23 (UTC)

I have figured out why Maya is crashing. It sees that /usr/lib/libmd.so is present and tries to initialise IRIX's MIDI interface, fails to find the required symbols and calls a null pointer. Simply delete the /usr/lib/libmd.so symlink and Maya will start working again.

I am not sure if an issue should be filed to rename libmd (which is a library of message digest routines, nothing to do with MIDI) to something else, as other software might get similarly confused.

theMaizeOfficial commented on 2021-09-14 11:59 (UTC)

@Cuissedemouche i can see that the libtiff problem has been solved, as in my last comment, it was just a question, a "no i haven't solved it yet" would have sufficed. if you want to install 2022.1 you need to use the pkgbuild given for 2022 with the following changes.

change in pkg build: (does not rectify the issue of segfaults but does update you to 2022.1)

pkgver=2022.1 source=('manual://Maya2022_64-2022.1-579.x86_64.rpm') sha256sums=('a7932fdaf15b52b19908314c6b575f2ca4037871f26c3feaf907b091ba493817')

I have yet to get a pkg build for 2022.2 to work.

Cuissedemouche commented on 2021-09-14 10:07 (UTC)

@theMaizeOfficial As I said, I still have the segfautl problem, but it was already mention that the libtiff.so.5 wasn't the one causing the segfault. The segfault is cause while the maya.bin is executed, so I really don't know what's the problem.

theMaizeOfficial commented on 2021-09-14 04:00 (UTC)

Maya 2022.2 has been released !

theMaizeOfficial commented on 2021-09-12 05:47 (UTC)

@Cuissedemouche did you get past the Segfault? i have successfully folowed your instructions and the libtiff issue is solved. how did you get past the faulting?

Cuissedemouche commented on 2021-09-11 13:10 (UTC) (edited on 2021-09-11 13:30 (UTC) by Cuissedemouche)

I solved the libtiff.so.5 problem by compiling it by myself but I still have the segfault problem.

If you want to solve the libtiff issue before it got solved by Arch, you can just go download the last libtiff release on the official website, and compiling it with the symbol flag: ./configure --enable-ld-version-script make make install

Also by default it install it under /usr/local/lib*, so you have to create a link to /usr/lib/

And thanks for reporting the issue (https://bugs.archlinux.org/index.php?do=details&action=details.addvote&task_id=71330)

Tanghe commented on 2021-09-10 10:19 (UTC)

im going to install redhat 8.2 via the develpers program.

ozzy1202 commented on 2021-09-10 08:16 (UTC)

No, no solution found as of now as far as I can tell. I don't use maya as my main software, I just use it every now and then, so I am dualbooting for now and running maya somewhere else

theMaizeOfficial commented on 2021-09-10 03:18 (UTC) (edited on 2021-09-10 03:19 (UTC) by theMaizeOfficial)

@ozzy1202 Is there a fix for the seg fault yet? or a work around? and my appologies the width of my terminal was small and i did not see that they were actually separated errors until i expanded it.

ozzy1202 commented on 2021-09-09 10:05 (UTC)

@theMaizeOfficial segfault is not libtiff issue as @costashatz already mentioned. Fixing the libtiff is already mentioned in galaxy0419 feature request for archlinux compilation of libtiff (you can probably compile it yourself to have the fix included if you really wish) but the segfaulting part is different issue altogether. My maya 2016 install that I had doesn't mention any libtiff issue (as I think it probably didn't use openimageio that is throwing this libtiff message) and it still segfaults exactly the same with the same gdb results that finish readable backtrace at TinputDeviceManager::createDeviceList() () from /usr/autodesk/maya2020/lib/libExtensionLayer.so

theMaizeOfficial commented on 2021-09-08 14:51 (UTC)

@costashatz https://help.autodesk.com/view/MAYAUL/2018/ENU/?guid=GUID-D2B5433C-E0D2-421B-9BD8-24FED217FD7F

I think this might help, i saw some one here was posting on the autodesk forum about the libiff but this has all the other info if you need it. its for 2018 but im sure if there is is this one there will be a 2022 version of this link some where, if this helps id like to know the results and process. cheers

theMaizeOfficial commented on 2021-09-06 12:59 (UTC)

i think i just accidentally deleted my comment, for me its coming to a screaming halt searching for libtiff.so.5 then displaying Segfault (a bunch of crap only aliens can read) (Core Dumped). so to me it seems like those two issues are going hand in hand together. i am just trying to solve it because i need this system to be up and running with maya... like yesterday lol

costashatz commented on 2021-09-06 05:01 (UTC)

@theMaizeOfficial the libtiff issue is different from the segfault. Check here: https://bugs.archlinux.org/task/71330?project=1&string=libtiff. Also the libtiff issue does not prevent you from using Maya.

costashatz commented on 2021-09-05 17:40 (UTC)

@ozzy1202 I am getting exactly the same behavior here... Now not even Maya 2018 or 2020 that were working before are working, no matter what I try. With strace I managed to fix a few issues with locale (that could possibly create some issue), but never got rid of the segfault. For me this is either GPU-related, Qt-related or Adsklicensing related. But as you, I have ran out of ideas.

ozzy1202 commented on 2021-09-05 17:15 (UTC) (edited on 2021-09-05 17:16 (UTC) by ozzy1202)

I tried gdb maya 2020 and 2016 that were working before,

#0  0x0000000000000000 in ?? ()
#1  0x00007fffec8dca0c in TinputDeviceManager::createDeviceList() () from /usr/autodesk/maya2020/lib/libExtensionLayer.so
#2  0x00007fffec65c758 in Tapplication::create(bool) () from /usr/autodesk/maya2020/lib/libExtensionLayer.so
#3  0x000000000040f35e in TmayaApp::create() ()
#4  0x000000000040eea1 in appmain() ()
#5  0x000000000040d476 in main ()

These are the results (in both of them they look similar), but I can't find a solution based on that.

ozzy1202 commented on 2021-09-05 15:21 (UTC)

@costashatz no, I didn't. I tired a lot, even downgraded all packages that I have in my system effectively bringing it back to what it was some time ago when everything worked and it still segfaulted this time... I tired to follow it with strace but I am not skilled enough to figure it out that way. I kind of gave up on it for now because I run out of ideas. It is extremely strange issue, especially as it seems like it happens to just some people and seems to not affect others on the same OS... I also tested mayapy as you mentioned it works for you, it also works for me.

costashatz commented on 2021-09-04 22:46 (UTC)

@ozzy1202 @Tanghe did you figure out the segmentation fault? Maya was working fine until I updated a few days ago and now I am getting a seg fault. mayapy works ok. So it should be a Qt-ish issue that I cannot find (but I am not 100% sure). @galaxy0419 any ideas on what can be wrong with Qt or something else?

ozzy1202 commented on 2021-08-26 16:45 (UTC)

@Tanghe did you figure out the segmentation fault? I experience it too and I don't know how to get over it and I kind of need to run maya. I even tried it on maya 2020 that was working last month and it is also segfaulting now even old install of maya 2016 was segfautling. After some googling I also found someone on manjaro forums that has encountered segfault with maya 2018 4 days ago after update. I know manjaro is not arch, but maybe his case might be somehow related to mine and yours?

galaxy0419 commented on 2021-08-14 12:19 (UTC) (edited on 2021-08-14 12:20 (UTC) by galaxy0419)

@Tanghe Please make sure you follow the instructions in the pinned comment. if you want to start Maya in the command line please use the start script in the same folder instead of the binary directly. This version works fine on my intel machine.

Tanghe commented on 2021-08-14 11:21 (UTC)

@galaxy0419

I can`t seem 2 log in over there.

Also does this mean noone can install maya at this point ?

Or is the segmentation fault possibly caused by something else ?

galaxy0419 commented on 2021-08-14 05:38 (UTC) (edited on 2021-08-14 05:38 (UTC) by galaxy0419)

@Tanghe The libtiff package does not have symbol version enabled. I've created a feature request, you can vote it up there.

Tanghe commented on 2021-08-13 13:17 (UTC) (edited on 2021-08-14 11:18 (UTC) by Tanghe)

Hmm now i get the erro that

./maya.bin: /usr/lib/libtiff.so.5: no version information available (required by /usr/autodesk/maya2022/bin/../lib/libmayaOpenImageIO.so.2.0)

zsh: segmentation fault (core dumped)  ./maya.bin

Libtiff is installed though

Tanghe commented on 2021-07-19 23:56 (UTC) (edited on 2021-07-20 01:10 (UTC) by Tanghe)

Edit: Missing package was lib32-nvidia-cg-toolkit

I followed the instructions and now i also can not start maya 2022 after rebooting.

I was also never promted to enter my credentials can annyone help me troubleshoot this ?

The command Maya isn't even found. But the program does show up in my launcher. (pressing it does nothing, though.)

Executing maya.bin returns cannot open shared object file libCg.so.

what provides this ? (installing glibc 2.33-5 did not fix)

when i run ldd following are missing.

    libCg.so => not found
    libCgGL.so => not found
    libssl.so.10 => not found
    libcrypto.so.10 => not found
    libXp.so.6 => not found

If i search for the libs i have some of them.

EDIT: After some pamac i`ve got it down to just

    libCg.so => not found
    libCgGL.so => not found

cant seem to find where 2 find though

SionSavior commented on 2021-07-13 10:30 (UTC) (edited on 2021-07-13 10:32 (UTC) by SionSavior)

Yo thanks for the reply "galaxy0419". However, I have found another solution. My problem was that not all dependencies were fulfilled.

I followed another tutorial and with this one it worked right on the 1st try.

Instruction 1. https://www.reddit.com/r/ManjaroLinux/comments/k3jz5a/how_to_install_maya_2020_renderman_23_on_manjaro/ Instruction 2. https://gist.github.com/mortenbh/38b8b30c4d7c190b9731fcd0e4497e47

I basically followed the 1 tutorial on Reddit. However, I used the shortcuts from the 2nd guide on Github.

Now all dependencies were fulfilled and it worked right away even with Arnold and Bifrost. I have not installed Renderman (just as a side note).

Maybe someone could make a nice script out of it so that there is no confusion all the time. ;)

PSS.: Note that some packages require a GPG key. The old servers used in the instructions etc. do not work. You have to look for an alternative. I used the GPG servers from Ubuntu (with sudo (for the user)). Just as a hint.

galaxy0419 commented on 2021-07-12 16:30 (UTC)

@SionSavior, please read the instructions to make sure every required packages are installed (adlmapps, adsklicensing and Maya at least). BTW, you need to start adsklicensing system service before starting Maya.

SionSavior commented on 2021-07-12 15:22 (UTC)

Yo, Today i tried to install Maya. I used this script: https://github.com/filmmakerto/arch-installmaya from filmmakerto. Everything works fine, but ... Maya doesn't start.

I mean i registered everything sudo /opt/Autodesk/AdskLicensing/11.0.0.4854/helper/AdskLicensingInstHelper register -pk 657N1 -pv 2022.0.0.F -el EN_US -cf path/to/mayaConfig.pit

Reboot And i tried to start maya.. but nothing .. not even a background process....

Maybe someone have a idea

filmmakerto commented on 2021-05-14 21:30 (UTC) (edited on 2021-05-14 21:31 (UTC) by filmmakerto)

Thanks @galaxy0419 for the installation instructions -- they pointed me in the right direction, but they didn't immediately make it clear to me what I have to do to install the package.

But I figured it out, and since I suspect there may be some other users who have the same problem, I wrote a little installation script: https://github.com/filmmakerto/arch-installmaya

Maybe it will help some people. Cheers

libreliu commented on 2021-03-20 16:55 (UTC) (edited on 2021-03-20 17:26 (UTC) by libreliu)

Oops, AdskLicensingInstHelper register actually requires root, as is described in AdskLicensingInstHelper -h. The problem solved as I uses sudo.

Hope this helps anyone who have fallen into the same pit lol


Following the instructions on the pinned message, I've got this when I tried to activate the product:

[libreliu@Legion-R7k aur]$ /opt/Autodesk/AdskLicensing/9.2.1.2399/helper/AdskLicensingInstHelper register -pk 657L1 -pv 2020.0.0.F -el EN_US -cf ./Autodesk_Maya_2020_4_ML_Linux_64bit/MayaConfig.pit 
Native call error in adlmPITSetProductInformation_2 28: Failed to Encrypt the PIT file

I've tried starting the adsklicensing service, but that doesn't help.

Running maya will result in the following error before starting the adsklicensing service:

/usr/autodesk/maya2020/bin/maya.bin: /usr/lib/libtiff.so.5: no version information available (required by /usr/autodesk/maya2020/lib/libmayaOpenImageIO.so.2.0)
maya: Autodesk Maya 2020
A licensing error occurred that Autodesk systems were not able to handle for you. Please contact Autodesk Customer Support for help in resolving this error.
adlsdkAuthorize returned with error code: ADLSDK_STATUS_ADLS_NOT_FOUND
The default location for log files to help diagnose the issue is: /usr/tmp

and after:

/usr/autodesk/maya2020/bin/maya.bin: /usr/lib/libtiff.so.5: no version information available (required by /usr/autodesk/maya2020/lib/libmayaOpenImageIO.so.2.0)
maya: Autodesk Maya 2020
A licensing error occurred that Autodesk systems were not able to handle for you. Please contact Autodesk Customer Support for help in resolving this error.
adlsdkAuthorize returned with error code: ADLSDK_STATUS_LICENSE_CHECKOUT_ERROR
The default location for log files to help diagnose the issue is: /usr/tmp

I've installed all the packages except RokokoMotionLibrary, and I put my pacman log here in case I've forgotten something:

[2021-03-21T00:14:23+0800] [ALPM] installed adlmapps (17.0.49-1)
[2021-03-21T00:14:55+0800] [ALPM] installed adsklicensing (9.2.1.2399-1)
[2021-03-21T00:15:24+0800] [ALPM] installed adlmflexnetclient (17.0.49-1)
[2021-03-21T00:15:49+0800] [ALPM] installed adlmflexnetserver-ipv6 (17.0.50-1)
[2021-03-21T00:16:42+0800] [ALPM] installed libjpeg6-turbo (1.5.3-2)
[2021-03-21T00:16:42+0800] [ALPM] installed libxp (1.0.3-4)
[2021-03-21T00:16:42+0800] [ALPM] installed xorg-fonts-alias-75dpi (1.0.4-1)
[2021-03-21T00:16:43+0800] [ALPM] installed xorg-fonts-75dpi (1.0.3-7)
[2021-03-21T00:16:43+0800] [ALPM] installed xorg-fonts-alias-100dpi (1.0.4-1)
[2021-03-21T00:16:43+0800] [ALPM] installed xorg-fonts-100dpi (1.0.3-7)
[2021-03-21T00:18:01+0800] [ALPM] installed libpng15 (1.5.30-1)
[2021-03-21T00:37:18+0800] [ALPM] installed maya (2020.4-1)
[2021-03-21T00:38:48+0800] [ALPM] installed maya-bifrost (2.2.0.0-1)
[2021-03-21T00:39:02+0800] [ALPM] installed maya-substance (2.1.7-1)
[2021-03-21T00:40:40+0800] [ALPM] installed maya-arnold (4.1.1-1)

galaxy0419 commented on 2020-12-05 15:26 (UTC) (edited on 2020-12-05 15:29 (UTC) by galaxy0419)

@kalani Try to build the package using makepkg -si manually. AUR helpers does not support this package. You need to copy the rpms in AUR packages' build folders mentioned in the pinned comments respectively (e.g. copy Packages/adlmapps17-17.0.49-0.x86_64.rpm to adlmapps's build folder).

kalani commented on 2020-12-05 11:46 (UTC)

Where should I be placing the Packages/*.rpm files so they can be picked up and installed?

I have confirmed the filenames and checksums match. I then tried running "pacaur -S maya" from the working directory with the *.rpm files, which failed being unable to locate them. I then tried copying the RPM files to ~/.cache/pacaur/("adlmapps","adsklicensing","maya")/src/ directories, and to /tmp, each had no change in behavior.

galaxy0419 commented on 2020-11-30 03:34 (UTC) (edited on 2021-06-24 10:15 (UTC) by galaxy0419)

Installation Instructions:
Autodesk Maya has updated the EULA for education version, see here for more info.

To get the latest version of maya, go to your account page and click "Product Updates" and download the linux tgz file.

Extract the tgz file into a folder.

Remove maya if you have version older than 2020.3 installed.

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. MayaConfig.pit for product activation
2. Packages/adlmapps*.rpm to build adlmapps
3. Packages/adsklicensing*.rpm to build adsklicensing
4. Packages/adlmflexnetclient-*.rpm to build adlmflexnetclient (for network deployment only, most of you won't need this)
5. Packages/adlmflexnetserverIPV6-*.rpm to build adlmflexnetserver-ipv6 (for network deployment only, most of you won't need this)
6. Packages/Maya*.rpm to build this package
7. Packages/package.zip to build maya-arnold
8. Packages/Bifrost*.rpm to build maya-bifrost
9. Packages/RokokoMotionLibraryMaya*.rpm to build maya-rokoko-motion-library
10. Packages/SubstanceInMaya*.rpm to build maya-substance
11. Packages/MayaUSD2022*.rpm to build maya-usd

Note: Package 2 and 3 are required to use maya and 7 to 11 are plugins which can be installed when needed.

Activate the product using command with root /opt/Autodesk/AdskLicensing/11.0.0.4854/helper/AdskLicensingInstHelper register -pk 657N1 -pv 2022.0.0.F -el EN_US -cf /path/to/MayaConfig.pit

Start Autodesk licensing service on boot using systemctl enable adsklicensing.service or start the service before using maya using command systemctl start adsklicensing.service

Reboot

Enter your Autodesk account the first time you open it.

Cheers

galaxy0419 commented on 2020-11-30 02:32 (UTC) (edited on 2020-11-30 02:43 (UTC) by galaxy0419)

@Dzordzu Yes, The previous version of maya include all components in one package. It is expected to have some conflicts. Please remove the old package before installing the new one.

Dzordzu commented on 2020-11-29 03:23 (UTC) (edited on 2020-11-29 03:30 (UTC) by Dzordzu)

@galaxy0419 I've tried to use your PKGBUILD, but it does not do well with an existing maya installation. There are loads of file conflicts (exists in filesystem (owned by maya))

Locations of the conflicts: opt/Autodesk/AdskLicensing/9.2.1.2399

Seems to be a problem with the pre_remove hook

galaxy0419 commented on 2020-11-19 13:34 (UTC)

@aquarius There is no need to unpack rpms as it will be extracted by bsdtar automatically. Could you test it on your side to see if it's working?

aquarius commented on 2020-11-19 11:25 (UTC)

@galaxy0419 not too elegant. It is necessary to append instructions for unpacking rpms in PKGBUILD

aquarius commented on 2020-11-18 10:42 (UTC)

@galaxy0419 now you are co-maintainer

galaxy0419 commented on 2020-11-13 11:18 (UTC)

@aquarius Hi, do you plan to continue to support it? I'm happy to be the maintainer. I have a working PKGBUILD for Maya 2020.3.

filmmakerto commented on 2020-11-02 17:42 (UTC)

in case anyone has the same problem as i described below: it's working for me now after a reinstall. i'm not sure if the reinstall is what fixed it or the switching between linux and linux-lts kernel.

filmmakerto commented on 2020-10-30 22:23 (UTC)

i'm not sure if i'm missing something here, but i can't get maya to run.

i managed to set up the education license by logging in to my autodesk account, downloading the installation files from there, finding my serial number in the downloaded files under Autodesk_Maya_2020_ML_Linux_64bit/manifest/deployment_maya.xml and running sudo /opt/Autodesk/AdskLicensing/9.2.1.2399/helper/AdskLicensingInstHelper register --pk 657L1 --pv 2020.0.0.F --cf /var/opt/Autodesk/Adlm/Maya2020/MayaConfig.pit --el en --sn [MYSERIAL]

then i was able to fix some startup errors by replacing _ssl.so and _hashlib.sso in /usr/autodesk/maya2020/lib/python2.7/lib-dynload with the respective files from /usr/lib/python2.7/lib-dynload/

but now, when i run maya2020, i still get an error:

/usr/autodesk/maya2020/bin/maya.bin: /usr/lib/libtiff.so.5: no version information available (required by /usr/autodesk/maya2020/lib/libmayaOpenImageIO.so.2.0)

does anyone have a fix for this? or is this just an out of date issue?

altaf commented on 2020-08-23 16:43 (UTC)

@kokokoshka yeah I got that file the maya is working thanks but this is a problem I get a error of some colour transformation error

kokokoshka commented on 2020-08-22 13:34 (UTC)

altaf, GPG keys for libpng15 is expired. Add a new one, or just skip verifying. More info in the libpng15 package comments.

altaf commented on 2020-08-15 09:16 (UTC)

With this new maya update i get this error

==> Validating source files with sha256sums... libpng-1.5.30.tar.xz ... Passed libpng-1.5.30.tar.xz.asc ... Skipped libpng-1.5.30-apng.patch.gz ... Passed ==> Verifying source file signatures with gpg... libpng-1.5.30.tar.xz ... FAILED (unknown public key F54984BFA16C640F) ==> ERROR: One or more PGP signatures could not be verified! Failed to build libpng15

lucyCole commented on 2020-06-10 16:27 (UTC)

Hi there on a fresh sync of Arch I just updated to the Maya 2020 push and now I get this error when liscensing

sudo /opt/Autodesk/AdskLicensing/9.2.1.2399/helper/AdskLicensingInstHelper register --pk 657L1 --pv 2020.0.0.F --cf /var/opt/Autodesk/Adlm/Maya2020/MayaConfig.pit --el en --sn MY_SERIAL_NUM [sudo] password for lucy: reading configuration file /var/opt/Autodesk/AdskLicensingService/AdskLicensingService.data failed: open /var/opt/Autodesk/AdskLicensingService/AdskLicensingService.data: no such file or directory

Maya previously worked on my system before this update

altaf commented on 2020-06-01 12:30 (UTC)

@wilaze it was maya 2017 i did install it as a rpm package method

aquarius commented on 2020-06-01 10:53 (UTC)

@kokokoshka sure! Do you want update Maya version?

kokokoshka commented on 2020-05-31 16:13 (UTC)

Can you make me co-maintainer? I want to update package.

wilaze commented on 2020-01-04 04:35 (UTC)

@sid350 what i know is Maya only support Fedora and RHEL/CentOS with rpm. But days ago i tried to install it on my Fedora 31, via official installer and it says like yours "OS is not supported". I dunno how to install it on Fedora anymore. There is no new article about how to do it. I still hope i can install Maya 2020 in my EndeavourOS via this AUR :( still waiting

sid350 commented on 2020-01-03 00:44 (UTC)

What about Maya 2020? When I try to install it via official installer it says OS is not supported :(

wilaze commented on 2019-12-24 01:38 (UTC)

@aquarius Awesome! i really want Maya on my EndeavourOS. I'll wait. btw Maya 2019 or 2020?

aquarius commented on 2019-12-23 10:08 (UTC)

Sorry, for long wait. I will update package soon!

wilaze commented on 2019-12-23 05:12 (UTC)

@altaf What you mean? What Maya version that work in your machine using this package? 2017 or 2019? Not work for me

FireBlackHat commented on 2019-07-22 06:40 (UTC)

Can you give me access as co-maintainer? I would gladly accept it :)

FireBlackHat commented on 2019-07-13 18:06 (UTC) (edited on 2019-07-13 18:08 (UTC) by FireBlackHat)

Maya 2019 is now supported for Linux. https://linuxhint.com/install_autodesk_maya2019_ubuntu/

Time to update the installer...

aquarius commented on 2018-09-29 22:38 (UTC)

@joksim

post your update, i update script

joksim commented on 2018-09-29 20:10 (UTC)

You can obtain Maya 2018 for Linux using the student method as described here:

https://knowledge.autodesk.com/customer-service/account-management/education-program/create-education-account/create-account-students-educators

The script needs to be updated accordingly (hashes, filenames, etc.) and can be run as a local package build (using makepkg....) I can post my adapted script if needed...

z3ntu commented on 2018-08-27 13:29 (UTC)

@luciferHasa It seems that Maya 2018 isn't available for "normal users" on Linux anymore.

Requires a multi-user license, not supported with single-user license.

Source: https://knowledge.autodesk.com/support/maya/troubleshooting/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Maya-2018.html

luciferHasa commented on 2018-08-25 06:08 (UTC)

hello will this be upgraded to maya version 2018.1 soon? :)

z3ntu commented on 2017-11-11 15:47 (UTC)

@oljik: Just upload the pkgbuild to pastebin and I'll have a look at it. If it's good (and working), I can replace it and give you co-maintainer rights.

Airbar commented on 2017-11-11 14:52 (UTC)

@oljik Hey, i would really love to get your PKGBUILD for Maya. Would be nice if you could upload it here on AUR.

oljik commented on 2017-11-08 19:12 (UTC)

I have built my own PKGBUILD 2 years ago, by reading houdini and many PKGBUILDs. However, I didn't have time to upload it. Then I went to windows. Now I am back and will upload them soon. You can delete this package. I have better packaged one. It can be used for all maya version to install seperately and Adlmapps, FlexnetServer/Client have seperate pkgbuild with systemd service files for selective install. I didn't add maya-setup like you. Does someone need it? I think adlmapps is working fine for registration.

Shadowlabs commented on 2017-09-22 13:53 (UTC)

yup, @z3ntu, i put in my licence and it still gives me maya: Autodesk Maya 2017Licensing ErrorA licensing error occurred that Autodesk systems were not able to handle for you. Please contact Autodesk Customer Support for help in resolving this error.GetFeatureAuthorizationStatus 1 (Failure)

z3ntu commented on 2017-09-22 08:58 (UTC)

@Shadowlabs: So you ran the installer first (sudo /opt/maya-setup/setup) and entered your license there? I can't really help you with the issue as I have problems with the software myself but I took over maintainer status as I updated the application to a newer version.

Shadowlabs commented on 2017-09-21 20:42 (UTC)

@z3ntu it still isnt verified despite me putting my licence in the installer... what does it say when it works for you? because if i launch it from terminal i get [lotus@Lotus-Hackintosh ~]$ maya2017 maya: Autodesk Maya 2017Licensing ErrorA licensing error occurred that Autodesk systems were not able to handle for you. Please contact Autodesk Customer Support for help in resolving this error.GetFeatureAuthorizationStatus 1 (Failure)

z3ntu commented on 2017-09-19 12:36 (UTC)

@Shadowlabs: The /opt/maya-setup/setup application will show you "installation failed" but this error is expected (as the setup application activates maya so you can use it normally)

z3ntu commented on 2017-09-19 12:35 (UTC) (edited on 2017-09-19 12:37 (UTC) by z3ntu)

If anyone wants to take over this package (or become co-maintainer) I'll gladly give it to you.

Shadowlabs commented on 2017-09-19 12:12 (UTC)

i Cant seem to install the package, I'm stuck at the "Can not launch RPM Executable" error, im pretty new to this, how can i fix it?

naelstrof commented on 2017-08-17 21:20 (UTC)

The PKGBUILD needs QT4 added as a dependency, also for those of you who get an error like this while running the setup: X Error: BadAccess (attempt to access private resource denied) 10 Extension: 130 (MIT-SHM) Minor opcode: 1 (X_ShmAttach) Resource id: 0x145 You can run the setup like this to fix it: sudo QT_X11_NO_MITSHM=1 /opt/maya-setup/setup

t-ask commented on 2017-07-26 12:52 (UTC) (edited on 2017-07-26 12:54 (UTC) by t-ask)

Please add/move the licence of this package to "${pkgdir}/usr/share/licenses/${pkgname}/".

sanya_rnd commented on 2017-06-04 00:26 (UTC) (edited on 2017-06-06 06:51 (UTC) by sanya_rnd)

These bugs can be easily fixed: echo "MAYA_DISABLE_CIP=1" >> ~/maya/2017/Maya.env # w/o it maya segfaults echo "LC_ALL=C" >> ~/maya/2017/Maya.env # w/o it maya gives singular matrix error Also you need this to prevent constant Helvetica package errors: xset +fp /usr/share/fonts/100dpi/ xset +fp /usr/share/fonts/75dpi/ xset fp rehash After that, Bifrost will be telling about missing lib: // Error: line 1: Unable to dynamically load : /usr/autodesk/maya2017/plug-ins/bifrost/plug-ins/bifrostshellnode.so libtinfo.so.5: cannot open shared object file: No such file or directory // // Error: line 1: libtinfo.so.5: cannot open shared object file: No such file or directory (bifrostshellnode) // To fix that, install aur/libtinfo (symlink package to ncurses) and after that: sudo ln -s /usr/lib/libtinfo.so.6 /usr/autodesk/maya2017/lib/libtinfo.so.5

z3ntu commented on 2017-05-04 07:42 (UTC)

More error messages: Error: Singular matrix, no inverse exists root : ERROR : code for hash md5 was not found. Traceback (most recent call last): File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type md5 root : ERROR : code for hash sha1 was not found. Traceback (most recent call last): File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha1 root : ERROR : code for hash sha224 was not found. Traceback (most recent call last): File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha224 root : ERROR : code for hash sha256 was not found. Traceback (most recent call last): File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha256 root : ERROR : code for hash sha384 was not found. Traceback (most recent call last): File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha384 root : ERROR : code for hash sha512 was not found. Traceback (most recent call last): File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/autodesk/maya2017/lib/python27.zip/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha512 Graphic device does not support OpenGL Core Profile, fallback to OpenGL renderer. VP2 Error : Failed to initialize graphics device.

z3ntu commented on 2017-05-04 07:39 (UTC)

There are some python<->openssl issues that are probably caused by the update to openssl 1.1. I haven't managed to get many things working since.

YAOMTC commented on 2017-04-13 21:42 (UTC)

I fixed my problem (albeit on CentOS) by disabling consistent network device naming, and reverting to the old style of eth0.

z3ntu commented on 2017-04-06 06:40 (UTC) (edited on 2017-04-06 06:53 (UTC) by z3ntu)

Running the setup and choosing the default options destroyed pacman... "pacman: symbol lookup error: /usr/lib/libssh2.so.1: undefined symbol: EVP_rc4" EDIT: ugh sorry, the LD_LIBARY_PATH linked pacman to the autodesk openssl libs... EDIT2: Another problem: lrwxrwxrwx 1 root root 63 6. Apr 08:32 /usr/bin/maya2017 -> /home/luca/aur/maya/pkg/maya/usr/autodesk/maya2017/bin/maya2017 But that file doesn't exist. EDIT3: The following patch fixes the issue from EDIT2: diff --git a/PKGBUILD b/PKGBUILD index ef168b0..be1bd92 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -49,7 +49,7 @@ package() { mkdir -p "$pkgdir"/usr/bin/ chmod 755 "$pkgdir"/usr/bin/ - ln -s "$pkgdir"/usr/autodesk/maya2017/bin/maya2017 "$pkgdir"/usr/bin/maya2017 + ln -s /usr/autodesk/maya2017/bin/maya2017 "$pkgdir"/usr/bin/maya2017 mkdir -p "$pkgdir"/usr/share/applications/ chmod 755 "$pkgdir"/usr/share/applications/

YAOMTC commented on 2017-03-26 03:05 (UTC) (edited on 2017-03-26 17:40 (UTC) by YAOMTC)

I can't get this to work. I just get "command not found" for maya. I built the package, installed it, ran "export LD_LIBRARY_PATH=/opt/Autodesk/Adlm/R12/lib64/", sudo ./setup, it fails (as expected?) with the "Could not launch rpm executable", and then... what next? EDIT: The command for Maya 2017 is "maya2017" not "maya". However I get a new error now - "AdlmInt Error: The AUTODESK_ADLM_THINCLIENT_ENV XML file could not be loaded maya: Autodesk Maya 2017Licensing ErrorA licensing error occurred that Autodesk systems were not able to handle for you. Please contact Autodesk Customer Support for help in resolving this error.GetFeatureAuthorizationStatus 6 (Initialization Error)"

QuartzDragon commented on 2016-11-25 23:46 (UTC)

@aquarius Perhaps so, however, Maya 2017 can also be acquired for free via a student licence, which, as far as I know, as no limits.

aquarius commented on 2016-11-25 22:14 (UTC) (edited on 2016-11-25 22:17 (UTC) by aquarius)

Hello everybody! We need an explanation. 1) maya developers(Autodesk) provide free educational license (full functional) only for 2016. 2) Not everything can be done in the PKGBUILD. Because user need to obtain a personal license key to register. Then put it into console license installer. 3) Register any licenses (for 2016 or 2017) also required to run GUI applications that can not be done from the PKGBUILD I was looking for ways how to simplify (real arch way) the installation of an educational (one-seat) license in 2016, but did not really find it.

Scimmia commented on 2016-11-24 06:30 (UTC)

QuartzDragon, yeah, the rpm is inside the tgz in this case. You need to extract it manually, but you can do that with bsdtar instead of pulling in a useless makedep on rpmextract.

QuartzDragon commented on 2016-11-22 04:59 (UTC) (edited on 2016-11-22 05:05 (UTC) by QuartzDragon)

@Scimmia Good to know! I'll fix it up. :) Edit: Without rpmextract, the RPMs never get extracted, though... :/

Scimmia commented on 2016-11-22 03:07 (UTC)

QuartzDragon, also, all of the copying and linking you're doing in the install script should be done in the PKGBUILD. These files need to be tracked by pacman.

Scimmia commented on 2016-11-22 03:05 (UTC)

QuartzDragon, your PKGBUILD looks much better, but please get rid of rpmextract. makepkg already uses bsdtar, and it will extract rpms just fine without the useless wrapper script (rpmextact.sh just calls bsdtar anyway).

HashFall commented on 2016-11-20 15:07 (UTC) (edited on 2016-11-20 17:33 (UTC) by HashFall)

Thanks @QuartzDragon and @csaez, it's working with the 2017 version. I had to add this to work: LC_ALL=C // Fixes the "Singular matrix, no inverse" Error MAYA_DISABLE_CIP=1 Updated .desktop file: [Desktop Entry] Name=Autodesk Maya 2017 GenericName=Maya Comment=3D modeling, animation, rendering and post-production Keywords=3d;cg;modeling;animation;painting;sculpting;texturing;rendering;render engine;python; Exec=/usr/bin/env LC_ALL=C /usr/bin/maya # Setting LC_ALL=C Icon=/usr/autodesk/maya2017/icons/mayaico.png Terminal=true # Terminal=false was causing my maya to crash on splash Type=Application Categories=Graphics;3DGraphics;

csaez commented on 2016-11-18 15:27 (UTC)

@QuartzDragon MAYA_DISABLE_CIP=1 disables the Customer Involvement Program (aka telemetry), I've no idea why it crashes on me but I saw a comment warning about it a few messages back and it totally fixed it. My desktop file looks like this, it refers to maya 2017 but you can adjust the paths to whatever makes sense (/usr/share/applications/maya.desktop). [Desktop Entry] Name=Autodesk Maya 2017 GenericName=Maya Comment=3D modeling, animation, rendering and post-production Keywords=3d;cg;modeling;animation;painting;sculpting;texturing;rendering;render engine;python; Exec=/usr/autodesk/maya2017/bin/maya Icon=/usr/autodesk/maya2017/icons/mayaico.png Terminal=false Type=Application Categories=Graphics;3DGraphics; Cheers!

QuartzDragon commented on 2016-11-18 06:11 (UTC) (edited on 2016-11-18 06:11 (UTC) by QuartzDragon)

@csaes Odd, I don't have to set the variable for Maya to run. What does it do? Also, can share the .desktop file you created?

csaez commented on 2016-11-18 02:29 (UTC) (edited on 2016-11-18 04:08 (UTC) by csaez)

Thanks QuartzDragon! It worked great, I had to install a few extra things in order to run it, but your package handled most of the installation. Missing system dependencies: - gamin - audiofile - e2fsprogs-libs More on this here: https://knowledge.autodesk.com/support/maya/troubleshooting/caas/CloudHelp/cloudhelp/2016/ENU/Installation-Maya/files/GUID-D2B5433C-E0D2-421B-9BD8-24FED217FD7F-htm.html Fonts (msfonts alternatives) - xorg-fonts-75dpi - xorg-fonts-100dpi - xorg-fonts-misc I also had to set MAYA_DISABLE_CIP=1 in order to run it (otherwise it segfaults on the splash screen) and I added a .desktop file for convenience. I hope this helps someone else trying to get Maya working on arch, Cheers!

QuartzDragon commented on 2016-11-10 12:09 (UTC) (edited on 2016-11-13 00:33 (UTC) by QuartzDragon)

For those of you waiting for an update to this package, and want a working and extensively tested PKGBUILD for Maya 2017 Update 1 that just works out of the box without much configuration, in the meanwhile, use these: PKGBUILD: https://paste.kde.org/peeik3fxd maya.install: https://paste.kde.org/pbro1vkcc Please tell me if anything needs fixing. :)

MD5HashBrowns commented on 2016-10-30 00:19 (UTC)

@th3od0re If I comment out those lines, it builds fine. But I can't figure out how you activated Maya. There's no /opt/Autodesk/MayaSetup without those lines of code. I don't know another way to activate besides running ./MayaSetup. So how did you manage to start Maya without "Segmentation Fault (core dumped)"?

commented on 2016-10-18 20:14 (UTC)

After commenting out # install "$pkgdir"/opt/Autodesk/MayaSetup # rsync -av --exclude='*.rpm' ./ "$pkgdir"/opt/Autodesk/MayaSetup i changed(line 31): mv "$pkgdir"/usr/local/bin/maya "$pkgdir"/usr/local/bin/oriMaya to: mv "$pkgdir"/usr/autodesk/maya2016/bin/maya2016 "$pkgdir"/usr/autodesk/maya2016/bin/oriMaya and(line 33) cp "$srcdir"/maya_start.sh "$pkgdir"/usr/local/bin/maya to: cp "$srcdir"/maya_start.sh "$pkgdir"/usr/autodesk/maya2016/bin/maya and it worked

renaudll commented on 2016-09-24 23:55 (UTC)

I was able to make it work by commenting the following line in PKGBUILD install "$pkgdir"/opt/Autodesk/MayaSetup rsync -av --exclude='*.rpm' ./ "$pkgdir"/opt/Autodesk/MayaSetup And using the instruction here for activating. https://fredrikaverpil.github.io/2015/09/10/installing-maya-2016-on-ubuntu-14-04-trusty/ I also had to set MAYA_DISABLE_CIP=1 to prevent a crash on loading.

sid350 commented on 2016-08-09 15:30 (UTC)

Can't install it. ... ==> Entering fakeroot environment... ==> Starting package()... install: missing destination file operand after '/tmp/yaourt-tmp-propellers/aur-maya/pkg/maya/opt/Autodesk/MayaSetup' Try 'install —help' for more information. ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build maya. Any advices?