On Sun, Feb 27, 2011 at 2:41 AM, Craig Bradney <span dir="ltr"><<a href="mailto:cbradney@zip.com.au" target="_blank">cbradney@zip.com.au</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On 2/27/11 12:21 AM, Owen wrote:<br>
>> On 26 Feb 2011 at 17:32, John Ghormley KJ4UFG wrote:<br>
>><br>
>>> What does Signal #6 refer to. I am doing my first real job with<br>
>>> 1.4.0 RC1<br>
>>> and I've had the system error out with that code twice in the last<br>
>>> twenty<br>
>>> minutes. I am very unaccustomed to seeing errors with 1.3.9 or<br>
>>> 1.3.9, both<br>
>>> of which i used for my last issue.<br>
>>><br>
>>> --<br>
>>> John Ghormley KJ4UFG<br>
>> After reading your note I tried doing some in frame text editing and<br>
>> after short time<br>
>> Scribus crashed with the error message "EXCEPTION_ACCESS_VIOLATION".<br>
>><br>
>> Remember, this is Beta software.<br>
><br>
> Not for much longer I believe !<br>
><br>
> If you use linux, man signal may (but probably may not) give you some<br>
> clues.<br>
><br>
> My guess is judging by the observation above, a memory allocation<br>
> error has occurred, the program called abort and the process died from<br>
> the abort, sig 6<br>
><br>
> I will try to crash it with my 1.4.0 (on linux), though I just<br>
> finished a pretty big job without any problems.<br>
><br>
><br>
><br>
><br>
</div>Maybe it related to this: <a href="http://bugs.scribus.net/view.php?id=9778" target="_blank">http://bugs.scribus.net/view.php?id=9778</a><br>
<br>
If you can build from svn, you will get this fix.<br>
<br>
Craig<br>
<br></blockquote><div><br> </div></div>Thanks, Craig. I am not familiar with the building svn versions, but I may try that. However, I completed the job using the Story Editor without any problems, whatsoever. That lends credibility to my assertion that in-frame editing is the problem. So, since I have, and do, use the Story Editor in several past versions without any difficulties and a great deal of ease, I think I will stay with it and see if there is an RC2 that fixes the in-frame editing problem, or a stable 1.4.0 release that may do the same. But, iMO, RC1 falls somewhat short of a releasable new stable version.<br>
-- <br>John Ghormley KJ4UFG<br>Editor, SERA <i>Repeater Journal</i><br>Walkertown, NC 27051 USA<br><a href="mailto:editor@sera.org" target="_blank">editor@sera.org</a><br><br>