Scribus crashes due to signal #6

[Georgetoon]

Well, then, I'll defer to whatever parnote and Georgetoon decide.

Actually, on second thought,  Paul makes a good point.  We've both figured out a work-a-round.  Maybe just leave well enough alone for the time being.  Paul  does a mountain of work on the magazine.

[gseaman]

How about 1.4.1 goes into a semi-permanent testing status? That way those that want to test and monitor the newer version can enable testing, install, then disable testing. Others, like Paul and Georgetoon, can continue with 1.3.9 without disruption. Then, when the main development has reached a point where it is worth it to update (whether it's 1.4.2 or 1.5.1 ), it gets moved to main.

Galen

[JohnW_57]

How about 1.4.1 goes into a semi-permanent testing status? That way those that want to test and monitor the newer version can enable testing, install, then disable testing. Others, like Paul and Georgetoon, can continue with 1.3.9 without disruption. Then, when the main development has reached a point where it is worth it to update (whether it's 1.4.2 or 1.5.1 ), it gets moved to main.

Galen

Or in special section?

JohnW

[Georgetoon]

Ya know, Paul really does a great job with the magazine. I still can't figure out how he assembles all the pages.  For instance, I layout my page with its art, text, and links.  I export as a PDF to show him how it should look. I then zip up all the files and email to him.  He now has the Scribus file and all elements. So, in order for him to drop things in place, I assume he and I need to be running the same version.

I'll follow his lead and preference.

[parnote]

How about 1.4.1 goes into a semi-permanent testing status? That way those that want to test and monitor the newer version can enable testing, install, then disable testing. Others, like Paul and Georgetoon, can continue with 1.3.9 without disruption. Then, when the main development has reached a point where it is worth it to update (whether it's 1.4.2 or 1.5.1 ), it gets moved to main.

Galen

I can definitely agree with that. Mind you that I am reluctant to mess with something that's already working, only to have to deal with a whole new set of issues. With it in testing (as long as it stays there), it will give me, Meemaw, ms_meme and georgetoon a chance to feel our way around and see what new issues it brings along. Personally, I can install it from testing on a computer that isn't used for the final production of the magazine, and feel safe running the newer version through its paces without it borking my production environment that I rely on every month.

Then, if all works out well, we can move it from testing and into the main repos.

How does that sound?

parnote

[parnote]

Ya know, Paul really does a great job with the magazine. I still can't figure out how he assembles all the pages.  For instance, I layout my page with its art, text, and links.  I export as a PDF to show him how it should look. I then zip up all the files and email to him.  He now has the Scribus file and all elements. So, in order for him to drop things in place, I assume he and I need to be running the same version.

I'll follow his lead and preference.

Thanks, georgetoon (and djohnston).

In the past, Scribus did some modifications to their file format when moving from 1.3.3 to 1.3.4. Insuring that the files from 1.3.9 still work properly on 1.4.1 is definitely something to evaluate.

If either of you have a non-critical computer you can install and test on, I'm all for 1.4.1 appearing in testing.

parnote

[gseaman]

I'll let Neal know what you guys want (just in case he isn't following this thread) and it'll likely go into testing. I hope it is clear that I am not pushing for that, I'm just trying to help. I don't even use the program.

Galen

[parnote]

I'll let Neal know what you guys want (just in case he isn't following this thread) and it'll likely go into testing. I hope it is clear that I am not pushing for that, I'm just trying to help. I don't even use the program.

Galen

Crystal clear ... and I appreciate your input in helping find a solution.

parnote

[Georgetoon]

How about 1.4.1 goes into a semi-permanent testing status? That way those that want to test and monitor the newer version can enable testing, install, then disable testing. Others, like Paul and Georgetoon, can continue with 1.3.9 without disruption. Then, when the main development has reached a point where it is worth it to update (whether it's 1.4.2 or 1.5.1 ), it gets moved to main.

Galen

I can definitely agree with that. Mind you that I am reluctant to mess with something that's already working, only to have to deal with a whole new set of issues. With it in testing (as long as it stays there), it will give me, Meemaw, ms_meme and georgetoon a chance to feel our way around and see what new issues it brings along. Personally, I can install it from testing on a computer that isn't used for the final production of the magazine, and feel safe running the newer version through its paces without it borking my production environment that I rely on every month.

Then, if all works out well, we can move it from testing and into the main repos.

How does that sound?

parnote

I would assume that 1.4.1 would be backwards compatible with 1.3.9.  if so, I have a laptop that I can install from testing (or wherever you guys place it).  i can even build my pages for comic feature and magazine and see if thing work. Then, transfer to main system, open, and see if things still click. 

Laptop has a bad, cracked hinge.  So far, display still works.  It's beyond the duct tape fix.  Sounds like a good testing machine to me!:)

[Neal ManBear]

Yes, I'm following this. I'm putting 1.4.1 in testing (32bit) and test (64bit). Galen, if you would post in Testing and ask for others to test also, maybe we can get some helpful info.