If you have access to another Linux installation and distro, you might check if Scribus will run without problems on that system.
You might check your current Linux installation for bugs.
I would be inclined to agree - except all other aspects of Scrubus, along with all other applications etc, work fine in both cases.
You might re-install Linux, GhostScript and Scribus (This is what I would consider first).
I would be inclined to agree, if I had any issues with Ghostscript or Scribus - except all other aspects of Ghostscript & Scribus work fine in both cases (remember the printing to
.ps above, that was Scribus sending to Ghostscript. So successfully that the very same
.ps file was used to import back into Scribus to enable me to save to PDF without crashing. So the options for where the fault exists are reducing fast...)
You might search for the string »signal 11« in the Search function in this forum — there are several hits, and maybe they can point you into the right direction.
I have done this, and I have not been able to find anything remotely like this issue so far.
For friends, I have installed and configured Scribus on Ubuntu and Debian systems and never experienced any issues.
Indeed, one system is Ubuntu based (Linux Mint), the other is Arch based (Manjaro) - neither are demonstrating issues with Scribus per se, except for this one file I have created with Scribus... the culprit here appears to be Scribus - whether anyone likes that or not is somewhat irrelevant and utterly unhelpful to boot.
Other than that, I don't have any ideas.
...and I wholeheartedly appreciate your feedback, but I am convinced it is a Scribus issue, more specifically, I believe it is a structure issue with the file itself, or how something about the file is NOT being handled properly by Scribus.
Narrowing down the cause of this issue is the challenge here, of which I am now a little closer!
I decided to make a copy (Save As...) of the original file - which still demonstrates the exact same behaviour, ie attempting to save to PDF causes Scribus to crash - and selectively delete content from it until I could successfully save to PDF.
Well now, when I deleted the content of the first text box, saved the file, then attempted to print to PDF - Scribus did NOT crash!
I then restored the content and went through it character by character (in Scribus) looking for oddities... there was one, where the font type changed at the end of the line.
I proceeded to remove all formatting and style from the text, but it made no difference. I even went through the process of deleting a character, saving the document, attempting to save as PDF, enduring the crash, restarting Scribus to delete another character, save, print, crash, repeat... until I no longer crashed when attempting to save to PDF.
This took a while, and I only succeeded to save to PDF when all text in the text box was removed.
The pre-flight check flagged 1 issue, and empty text box (surprise, surprise!) and I was able to save to PDF.
I then removed the text box, saved the file, and once again Scribus would crash instantly when attempting to save to PDF - as far as I can establish, this is definitely a Scribus issue, probably a file structure issue, or an error handling issue - or both.
Putting the text box back - a new one - allowed me to get to the pre-flight check okay, but as soon as I hit "Ignore errors" Boom! Scribus crashes.
So whilst I wholeheartedly appreciate all the feedback and the suggestions from you guys, I am less concerned with the issue being with the installation of Linux and the supporting applications, including Scribus, and more so with the function (or lack thereof) of Scribus when attempting to save to PDF.
If someone can tell me specifically what I can do with the installation of two machines - that for all other purposes including Scribus work just fine - that will fix this issue, then the problem certainly resides with Scribus for the time being.
Perhaps there is a better place for me to highlight this issue where a developer might have deeper insight into how Scribus is possibly failing - or whether indeed I am failing somehow!
Thanks.