Spriter incompatible with tiling window managers?

[som-one]

Hi,

I tried to launch Spriter on my archlinux system but got an error.

 segmentation fault (core dumped)  ./Spriter

Running ldd showed nothing unusual and it worked in a lubuntu vm. Gdb told me the error was caused by some qt code.

I found another post with, what looks like the same problem: https://www.scirra.com/forum/spriter-early-adopter-sale-tools_p851923?&sid=216adbd35567c46a162b0a6a9930ee42#p851923.

After searching around I found that it is most likely caused because I'm using http://i3wm.org/. After switching to gnome-session, Spriter worked.

This looks like a general problem and not related to B11.

It would be awesome if a dev could try to launch Spriter in a i3wm session and see if this causes the application to crash.

Is anyone else using i3 and is able to run Spriter?

thanks

edit: I tried running Spriter in an active https://github.com/baskerville/bspwm session and got the same error (looks the same)

edit2: tried the same using http://dwm.suckless.org/ and got the same error

edit3: I changed the title from i3wm to tiling window managers because it looks like a general problem with these.

[som-one]

I tried to run Spriter with other WMs today:

- http://xmonad.org/ crashes

- http://awesome.naquadah.org/ works

- https://opensource.conformal.com/wiki/spectrwm works

- http://herbstluftwm.org/ crashes

- https://code.google.com/p/wmii/ crashes

All of these were in the same lubuntu vm without changing anything except for the active login session.

From https://faq.i3wm.org/question/3430/how- ... st-id-3462 it could be that the crash is caused because Spriter tries to do something with window related properties.

[som-one]

I collected some gdb stacktraces:

simple backtrace:

http://pastebin.com/QNu8CeZP

Here's the recursive part of the trace:

http://pastebin.com/p7KiADSL

Here's a trace for the beginning:

http://pastebin.com/REvTD7r7

If I can provide you something you need to fix this issue I'd love to do that.

[lucid]

Thank you for all the thorough information.  I will have to look into this further now that all the website and Steam launch stuff is taken care of.

[som-one]

Any news/update on this issue? Is there anything I can do to help you with fixing this?

 

Thanks

[lucid]

I apologize for the slow responses, and thanks for the offer to help, but I'm extremely busy with getting the documentation/api stuff done at the moment.  Looking into it will be an involved process, as I don't have several versions of Linux installed to test across, and I won't have time to look into it until I finish all the more urgent matters.  In the meantime, I'm glad that you have working alternatives to use Spriter Pro for now.

 

In general, getting Spriter to work on every flavor of Linux cannot be the highest priority - of the Linux users we have, everyone seems to be able to get it working.   So this means that we'd be spending a disproportionate amount of time that could be used on new (large) features, bug fixes, and getting Spriter supported on as many authoring system as possible (which is our current highest priority).  All of these would benefit all users, including all Linux users.

[som-one]

Thanks for your response. I can understand that you don't want to waste time on a system with such a low user share.

 

It's just weird, that Spriter is the first QT application that doesn't work on a multitude of tiling window managers (for me). I tried to see if there's something they have in common, but from the ones I tested there wasn't really anything ( see https://wiki.archlinux.org/index.php/Comparison_of_Tiling_Window_Managers#Comparison_table).

 

 

Maybe you're trying to do something with the QT application window that should be done by the window manager instead, like resizing. This could lead to an endless loop because it triggers a resize event and your code tries to correct/manipulate the window size, which in effect, triggers the same event again.

If something like this exists in your code, maybe it should be better to avoid that, because it could lead to weird behavior on other systems too.

 

Anyways, thanks for developing Spriter.

 

Edit: I ran

valgrind --leak-check=full ./Spriter

on Spriter and got this: https://paste.ee/p/HIxxA