Running kick in Ubuntu?

[BrianHanke]

I'm messing around with virtual PCs here and I've got Ubuntu, Maya 2020 and Arnold installed on both Azure and AWS instances. XFCE desktop. Arnold works great in Maya, but if I try to do a test render of cornell.ass using kick I get a segmentation fault. The funny this is that yesterday I fixed this somehow randomly with permissions (I think) but it got unfixed today. Thanks in advance for any advice!

[thiago.ize]

Can you paste the complete stack trace that arnold printed out when it crashed? It's possible that could contain clues on what the error might be.

[BrianHanke]

Thanks Thiago. How do I get a stack trace? Right now this is the extent of the error message:

[thiago.ize]

shoot, that crashed so quickly it never got a chance to output a message. You could try running it under a debugger and outputting a stack trace if you know how to do that. Otherwise, it's hard to say why it's crashing at startup.

I don't believe we test Arnold on Ubuntu, so can't vouch for whether it should work there. CentOS 7 is currently the recommended distro.

[BrianHanke]

Ha, well I rebooted the instance one more time and tried again first thing after the desktop came up and now it's working. Who knows! This is Ubuntu 20.04 running on Azure via Remote Desktop. Haven't done complete testing but so far Arnold in Maya 2020 seems to work perfectly and as far as I can tell kick works too (or maybe just when it's the mood).

[thiago.ize]

Good to hear a reboot fixed it.

[BrianHanke]

It's back to not working, so there's definitely something not right. I put together this output with strace and attached as a text file. Does this help you narrow down the problem at all? I also got the following warning when running via SSH command line only (the render finished fine): WARNING | unable to load dynamic library ./libai_renderview.so: libQt5X11Extras.so.5: cannot open shared object file: No such file or directory

dump.txt

[thiago.ize]

I can't spot anything in the dump that would explain the crash. The only suggestion I have is to either generate a minidump and post it here or run kick in gdb and report the stack trace here, but both of those options are not "user friendly". Apologies I can't be of more help.

[BrianHanke]

I appreciate your time! It seems to be an issue after the desktop loads. It works 100% of the time from the console before loading the desktop, and works most of the time at least from the desktop. That's good enough for my purposes.

[Jan_Walter]

You can try to change the permissions to 755 for the kick executable:

chmod 755 kick

It's also worth to double check that the executable can find all of it's shared libraries:

ldd kick

[BrianHanke]

Thanks! I'm using Windows VMs now just to make life easier, but I'll make a note of this to try next time I'm in Linux.