Autodesk Maya 2014 Signal: 11 (Unknown Signal)

Hi everyone.

 This morning my opensuse 12.3 box began updating and after a restart I launched Maya 2014 and guess what? It didn’t launched. 

So what did I do? I made a backup of everything, erased the whole drive, install OpenSuse 12.3 ( The DVD Version ), Open Yast and do an online update along with the community nvidia repositories and let the system finished. Just that, and installed my primary software, Maya 2014 and got the same error.

Here’s a snapshot of it : https://www.dropbox.com/s/qwxjbfqflz05fyt/snapshot1.png

I tried to ran maya as a normal user and root but failed.

michael@linux-t3s0:~> su -
Password: 
linux-t3s0:~ # maya


maya encountered a fatal error

Signal: 11 (Unknown Signal)
Fatal Error. Attempting to save in /usr/tmp/root.20130630.1542.ma
QWidget::setWindowModified: The window title does not contain a '
[li]' placeholder[/li]linux-t3s0:~ # exit
logout
michael@linux-t3s0:~> maya


maya encountered a fatal error

Signal: 11 (Unknown Signal)
Fatal Error. Attempting to save in /tmp/michael.20130630.1543.ma
QWidget::setWindowModified: The window title does not contain a '
[li]' placeholder[/li]michael@linux-t3s0:~> maya


maya encountered a fatal error

Signal: 11 (Unknown Signal)
Fatal Error. Attempting to save in /tmp/michael.20130630.1544.ma
QWidget::setWindowModified: The window title does not contain a '
[li]' placeholder[/li]

There’s only Autodesk Maya 2014 installed and libraries needed to get it running.
I had another post about library problems in the past but it was resolved and adding the user to the video group solved the signal 11 issue by that time but the issue came back like a "Freddy Krueger Nightmare’!

Here’s The Link to the past post : https://forums.opensuse.org/english/get-technical-help-here/applications/487219-autodesk-maya-2014-libssl-so-10-error.html

Machine Specifications :

Asrock H55M-LE
Core i7 870
8GB DDR3 1600mhz
Nvidia GTX 550 ti

Just in-case, I already did a Memory Test and Tried on another PC with different motherboards, CPU’s and 2 different Nvidia GPU’s ( GTX 550 ti & GTX 660 ).

It was working so **** awesome.

Hi, I remember the thread, plus that you got it running.
This looks like something is not OK in /tmp. Could it be it’s full? Did you check the permissions of /tmp ?

Another thing: could this be a kernel update where the NVIDIA driver wasn’t updated?

To check whether the nvidia driver is working correctly, please install the package “Mesa-demo-x” if not installed, and post the output of:

glxinfo | grep render

Snapshot of the output : https://www.dropbox.com/s/gvztf3k700kgng9/snapshot3.png

michael@linux-t3s0:~> glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: GeForce GTX 550 Ti/PCIe/SSE2
    GL_NV_blend_square, GL_NV_compute_program5, GL_NV_conditional_render, 
    GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
    GL_NVX_conditional_render, GL_NVX_gpu_memory_info, 
michael@linux-t3s0:~> 


I went Yast and clicked on Software management and searched for Mesa-demo-x and installed it.

Here are some info that might help :’(

https://www.dropbox.com/s/tjqkau2bofidwaw/snapshot6.png

https://www.dropbox.com/s/nd3mcr06zbdez3p/snapshot5.png

Well, that looks perfectly fine.
So it doesn’t seem to be the video driver’s fault this time…

What were the updates you installed, after which it wasn’t working anymore?
You can list all packages in the order they were installed (latest ones on top) like that:

rpm -qa --last | less

(you can scroll with the cursor keys and <page up>/<page down> f.e., press ‘h’ for a help screen and ‘q’ to quit)

And another user had strange problems watching videos lately, disabling plymouth (the bootsplash) fixes it for him (but he has a hybrid video system).
I’m not at all sure that this would help you as well, but since your earlier crash seemed to have been video driver related, why not just try it?
Just add “plymouth.enable=0” to the boot options. AFAICS you’re using grub, so you can just enter that at the boot menu, before pressing enter to boot the selected entry.
Then check with “cat /proc/cmdline” if that option is there (if not you must have done something wrong), and then try to start Maya.
(if you specify the option this way it isn’t saved, so on next boot you will have the standard boot options again)

I got so mad I wiped the whole drive.

I can install without no updates, and even with the updates, try on a another computer and it does the same thing. I’m trying everything!!! jaja, All I can do is laugh of the sadness jaja

I was reading these 2 post but since I’m not a debian user and don’t want to be, I want to stick to suse, then maybe this could help some how.

Ubuntu 11.04: libGL crashes - Autodesk Discussion Groups

Maya 2012 and Maya 2013 Issues

I did what the first post suggested to get information, see if you guys can figure something out:

michael@linux-t3s0:~> maya -d gdb / r / bt
Executing: gdb  /usr/autodesk/maya2014-x64/bin/maya.bin
Maya args:  '/' 'r' '/' 'bt'
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>:<exec_prefix>]
ImportError: No module named site
michael@linux-t3s0:~> 


Here are the links if you want to try Autodesk Maya 2014 SP1 :

http://download.autodesk.com/us/maya/service_packs/Autodesk_Maya_2014_SP1_English_Linux_64bit.tgz

To get a free license head over here :

https://students.autodesk.com/?nd=register_v2

Libraries Needed :

https://docs.google.com/file/d/0B-CK43cIim3pTXk0bWFpcXc5M1E/edit?usp=sharing

How do I check the permissions of /tmp ?

Sorry, that is useless.
You have to call Maya like this I guess:

maya -d gdb

Then type ‘r’ and press enter.
Then after it crashes, type ‘bt’ and press enter.

Then post the output.

ls -ld /tmp

And to see if it is full:

df -h /tmp

But as I said before in the other thread, I don’t think that error is because writing to /tmp failed. IMHO it’s a notice that a Fatal Error occured and informations HAVE BEEN written to /tmp.
Do you have any files like /tmp/michael.20130630.1543.ma after such a crash?
Check with:

ls -lh /tmp/michael.*.ma

I did but maya does not run at all. If I do the normal

maya

It would launch.

But if I do maya -d gdb I get this :

michael@linux-t3s0:~> maya -d gdb
Executing: gdb  /usr/autodesk/maya2014-x64/bin/maya.bin
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>:<exec_prefix>]
ImportError: No module named site
michael@linux-t3s0:~> 


Great!! I Just Love To Play with Linux! jaja!!!

here’s what i got with /tmp

michael@linux-t3s0:~> ls -ld /tmp
drwxrwxrwt 42 root root 4096 Jun 30 19:33 /tmp
michael@linux-t3s0:~> df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1      1008G  7.7G 1000G   1% /
michael@linux-t3s0:~> ls -lh /tmp/michael.*.ma
-rw-r--r-- 1 michael users 69K Jun 30 15:42 /tmp/michael.20130630.1542.ma
-rw-r--r-- 1 michael users 69K Jun 30 15:43 /tmp/michael.20130630.1543.ma
-rw-r--r-- 1 michael users 69K Jun 30 18:45 /tmp/michael.20130630.1845.ma
michael@linux-t3s0:~> 


Let me see if I’m getting this, Maya is supposed to have permission to write to /temp noir root or the users have permissions to write to it?
Or is it a video nvidia / nouveau problem?

I went inside with

 kdesu dolphin 

and went to /tmp and uploaded the files if you want to look them up :

https://www.dropbox.com/sh/udfxbpuf7h0xh6q/2Z65_uQzHy

:\ what do you think it could be?

On 2013-07-01 01:46, mjapox wrote:
>
> wolfi323;2568626 Wrote:

> here’s what i got with /tmp
>
>


> --------------------
>     michael@linux-t3s0:~> ls -ld /tmp
>   drwxrwxrwt 42 root root 4096 Jun 30 19:33 /tmp

That is correct, everybody can write there.

>   michael@linux-t3s0:~> df -h /tmp
>   Filesystem      Size  Used Avail Use% Mounted on
>   /dev/sda1      1008G  7.7G 1000G   1% /

Plenty of space, so that's not the problem.

>   michael@linux-t3s0:~> ls -lh /tmp/michael.*.ma
>   -rw-r--r-- 1 michael users 69K Jun 30 15:42 /tmp/michael.20130630.1542.ma
>   -rw-r--r-- 1 michael users 69K Jun 30 15:43 /tmp/michael.20130630.1543.ma
>   -rw-r--r-- 1 michael users 69K Jun 30 18:45 /tmp/michael.20130630.1845.ma
>   michael@linux-t3s0:~>
> --------------------

If wolfi323 is correct, those files would contain useful information, so
look inside them.

By the way, signal 11 is not unknown, it is “SIGSEGV”. That is the fatal
error, and then it says that it is going to save info into
/tmp/michael.20130630.1543.ma - and it does so. So look inside, it
probably is a text file.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

On 2013-07-01 00:56, mjapox wrote:
> But if I do maya -d gdb I get this :

You would need to have installed the debug packages of the entire
app/lib chain for that to succeed, I think.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Can you guys download the software and get it installed on your systems and tell me how it works?

I’d posted the link to download the software ( Autodesk Maya 2014 SP1 ), the registering site for a free license and the libraries needed for it to run.

I really need to get it running so I can continue on the project with the other guys.

We are doing a multiplayer game for Linux with the Unreal Engine so we hope to make it really great.
If you have ever played Gears OF War, you would know what I mean :wink:

Even if it means for you guy’s to get inside my computer remotely

  • My Wacom Tablet is dying to get on modeling those characters!

Your /tmp is ok. ALL users have read and write access to it. (See “man chmod” to understand the “rwxrwxrwxt” output)
And there’s 1000GB free, that should be plenty. (My whole harddisk isn’t that big… ;))

I went inside with

 kdesu dolphin 

and went to /tmp and uploaded the files if you want to look them up :

Dropbox - Error - Simplify your life

The files are read- and writable by you and readable by all users, so you wouldn’t have to do that as root.
Those files are some kind of log, but unfortunately they don’t contain any clue about the crash.

Or is it a video nvidia / nouveau problem?

:\ what do you think it could be?

You said you wiped your harddisk and did a fresh install?
Did you install the nvidia driver then? Is it working? (“glxinfo | grep render”)
What libraries did you install/symlink to and how? Maybe you messed that up?

Well, the first time you called it with “maya -d gdb / r / bt” and that was incorrect. So I hoped it would work with just “maya -d gdb”…
But in the AutoDesk openSUSE discussion you linked to in the other thread you were proposed this:

Setting environment variable MAYA_DEBUG_ENABLE_CRASH_REPORTING=1 in you Maya.env file or before launching Maya should give a stack trace of the crash. Least gives some idea of where the problem is

Or while the crash dialog is up, use gdb to attach to the maya.bin process and get the stack trace of all the threads

gdb maya.bin PID

Where PID is the process ID of maya.bin

Else run maya under the debugger. maya -d gdb

gdb command for thread back trace

thread apply all bt

So try that to get a backtrace of the crash.

Well, I might. But I’m not sure if it will work here. I only have a quite old Radeon 9600 card…
How big is the download?
Do you have to do anything special to provoke the crash, or does it just crash right after start?

Sorry, I can’t.
I downloaded this thing (815 MB, yeah! :sarcastic:), registered, but when I want to get a serial I only get this:

The Education Community is temporarily unavailable while we undergo maintenance.

So I have to try later again…:stuck_out_tongue:

But I had a look again at your libraries list.
Some annotations again:

  • libpng12, libjpeg62, libjpeg62-32bit: Don’t install those specific RPMs! Just install the versions included in openSUSE 12.3 with YaST or zypper! There have been updates since then, you know… (And your libjpeg62 and libjpeg62-32bit have differing revisions anyway, something like that is always asking for trouble)
  • libcrypto.so.10: I mentioned that one before (in the other thread). Don’t use libcrypto_compat! Where did you get that from anyway?
    libcrypto is part of libopenssl1_0_0 as well, so symlink it the same as libssl (they might depend on each other’s exact version, since they are in the same package):
sudo ln -s /lib64/libcrypto.so.1.0.0 /lib64/libcrypto.so.10

As I already said before a few times: Mixing versions can lead to trouble! Spurious Signal 11s (Segmentation Fault) for example… :wink:

You don’t have to do anything special. Once you start the setup from the terminal with ./setup it will ask you for some libraries. I used these libraries :

https://docs.google.com/file/d/0B-CK43cIim3pTXk0bWFpcXc5M1E/edit?usp=sharing

But you can search for the libraries yourself from the opensuse package site.

To confirm the /tmp space, you are right. I have a 2TB sata hard drive ( 1TB for the / and another 1TB for the home partition )

The Autodesk Maya 2014 SP1 size is 816MB : http://download.autodesk.com/us/maya/service_packs/Autodesk_Maya_2014_SP1_English_Linux_64bit.tgz

You need to make an account and get a free license from their website : https://students.autodesk.com/?nd=register_v2

  • Maya runs, it activates, it even opens up but with a dialog box and soon after you click continue or cancel it sends the signal error on the terminal :

Maya runs on any GPU so don’t worry. Maybe on that type of GPU you could end up making indie games or not so high quality movies.

  • Everything else works great. We use also these other software for realtime effects, texturing, sculpting and video editing :

Houdini : Home - Side Effects Software Inc. ( Go to the bottom of the page to see video demo )

RealFLow : RealFlow Home

3DCoat : http://3d-coat.com/ ( Go to the bottom of the page to see video demo )

OpenShot : http://www.openshotvideo.com/

Cinellera : http://cinelerra.org/

  • Before all this Signal 11 issue happened on my Box, I was running all of my software so great, that I had to record my computer and post it at YouTube :

Gaming & Modeling On Linux - YouTube

  • Please help me. I’m sort of dying on the inside.

I will work on that right away then.