<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><b style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> Richard Sharman <rsharman@pobox.com></span><br>
</p>
<div style="color: rgb(0, 0, 0);">
<div>
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Sent:</b> Tuesday, September 13, 2016 1:27 AM<br>
<b>To:</b> scribus@lists.scribus.net<br>
<b>Subject:</b> [scribus] Scribus 1.5..1 and 1.5.2 crash on Macos 10.11.6 when editing default character style or creating new char style</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">This is on a mac os 10.11.6 (El Capitan). With both 1.5.1 and 1.5.2 if I do<br>
New document, choose single sided, press OK<br>
Edit / Styles / Default Character Style then press Edit<br>
I get a popup “Scribus crashes due to Signal #11”<br>
<br>
A similar thing happens if I replaced step 2 with trying to create a new character style from the default. The Style Manager shows the Default Character Style as Family Arial. With version 1.4.5 I do not get the crash, and the Style Manager shows the Default
Character as Family Times.<br>
<br>
In February I was able to use Scribus 1.5.1 but I was running a much older version of Macos (10.6 I think).<br>
<br>
Preferences / Fonts shows that Arial font is available.<br>
<br>
...<br>
#20 0x00007fff88cd55af in _BlockUntilNextEventMatchingListInModeWithFilter ()<br>
#21 0x00007fff91517df6 in _DPSNextEvent ()<br>
#22 0x00007fff91517226 in -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] ()<br>
#23 0x00007fff9150bd80 in -[NSApplication run] ()<br>
#24 0x000000010532237f in qt_plugin_instance ()<br>
#25 0x00000001033737a1 in QEventLoop::exec ()<br>
#26 0x0000000103377a65 in QCoreApplication::exec ()<br>
#27 0x0000000100e593ef in mainApp ()<br>
#28 0x00007fff944fa5ad in start ()<br>
(gdb) <br>
<br>
Any help would be appreciated!<br>
Thanks,<br>
Richard<br>
<br>
<br>
</div>
<div class="PlainText">----</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">Could you try doing a debug build so that the gdb backtrace shows line numbers?</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">I think that you can do it by starting a clean build and adding <span>-DCMAKE_BUILD_TYPE=Debug <span>-DWANT_DEBUG=1 to the cmake command line.</span></span></div>
<div class="PlainText"><span><span><br>
</span></span></div>
<div class="PlainText"><span><span>If you can get valgrind <a href="http://valgrind.org/" class="OWAAutoLink" id="LPlnk732575">http://valgrind.org/</a> for MacOS, that might help also.</span><br>
</span></div>
<div class="PlainText"><span><span><br>
</span></span></div>
<div class="PlainText"><span><span>Regards, William</span></span></div>
<div class="PlainText"><span><span><br>
</span></span></div>
</span></font></div>
</div>
</body>
</html>