Possibly Sure there are more bugs. The idea is to kill as much as possible the more nasty and crashing bugs possible and leave the more soft for a revision release.
In order to download ftp://download.tuxfamily.org/synfig/pac … _amd64.deb, i have used “right click” / “save link as” (cause direct click redirect me on ftp[…]synfigstudio_0.63.05-20130420.master.8_amd64.deb/ and even accessing directly the directory)
Now (after i have downloaded right clicking), it’s working normaly … very rare …
I’m sorry but I don’t know how to fix that. If your distribution doesn’t have Cairo >= 1.12 it will crash.
It shouldn’t let you install in that case but the package script needs corrections.
I’m sorry, it’s my responsibility to fix that. I am a little bit sick at the moment, recovering from my trip. Will fix that as soon as I get on my foots. ^___^ Cheers!
Strangely, if I go to “Setup” option and check “Use Cairo renderer on Navigation” option, then opening any file crashes for me too… And I’m running Ubuntu 12.10…
Any file??? Really??
Any message from the terminal?
I would like to have one of those files to make tests.
Also, I’ll test the binaries on a fresh Ubuntu 12.10 installation to see what happen.
-G
Okay, I just tested. Not just “any” file (because it doesn’t seem to crash on “new” files I create), but those I’ve been working on before, such as my Polar Detective work files…
Here’s the log (including creating a new file at the very first attempt):
Ok, one clue at last.
OVERLAY method seems to crash immediately. Possibly an illegal instruction. I’ll review the code for OVERLAY method.
It is likely that other methods could trigger that crash so please be patient.
-G
The following blend methods crashes immediately in Linux package mode (tested 64 bits please help with 32 bits):
OVERLAY
DIVIDE
ADD
SUBTRACT
DIFFERENCE
BRIGHTEN
DARKEN
COLOR
ALPHA BRIGHTEN
ALPHA DARKEN
I’ve made some tests on my Linux Mint virtual machine. After clone the repository and create a build environment, I’ve found:
In debug mode and not optimized the crashes doesn’t happen.
In debug mode with optimization enabled (–enable-optimization=2) the crashes doesn’t happen.
In non debug mode with optimization enabled (–enable-optimization=2) crashes happens.
So the situation is not easy.
I would test the following combinations later:
4) No debug but optimized.
5) Same 2) 3) and 4) but in OSX. If the behavior is similar I would continue working with OSX. If in OSX the behavior is not crash then I would continue digging in Linux.
I’ll dig if there is any configuration option to trigger problematic code that might deliver crashes when optimized or when not in debug mode. If anyone has an idea on that I’m all ears.
-G