<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;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p><b style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> xemoth@gmx.com <xemoth@gmx.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, July 11, 2017 4:20 AM<br>
<b>To:</b> scribus@lists.scribus.net<br>
<b>Subject:</b> Re: [scribus] Scribus Crashes due to Signal #6 (or #11)</font>
<div><br>
</div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
> > I run Scribus 1.5.2 on Linux Kubuntu 16.04<br>
> ><br>
> > Scribus crashes randomly with the message "Scribus Crashes due to Signal<br>
> > #6" (or Signal #11)<br>
> > This happens about once a day -- not much, but very irritating.<br>
> ><br>
> > If I restart Scribus it reopens with no problem and everything is fine,<br>
> > nothing out of place or deleted.<br>
> ><br>
> > I cannot identify any single keystroke or set of keystrokes that trigger<br>
> > the crashes.<br>
> ><br>
> > What does Signal #6 or #11 actually indicate?<br>
> ><br>
> > How can I fix this?<br>
<br>
To find out what signals mean, you can use "<span>man 7 signal" or "kill -l". Signal 6 <span>SIGABRT can mean that the application failed an internal test and decided to terminate itself by calling abort(). Signal 11 <span>SIGSEGV (segmentation violation) means
that the application made an invalid memory reference and the Linux kernel killed it.</span></span></span></div>
<div class="PlainText"><br>
</div>
<div class="PlainText">Since you are on Linux, if you can run scribus from a command line, try running it through a debugger like "gdb". It will run at full speed, but if it crashes, it will drop into the debugger, and you can sometimes get a stack trace, which
might be useful.</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">Here is an example,</div>
<div class="PlainText">Start scribus under gdb. (If you want to pass options to scribus, look at the gdb "set args" command.)</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">
<div>$ gdb /usr/local/bin/scribus </div>
<div>GNU gdb (GDB) Fedora 7.12.1-48.fc25</div>
<div>Copyright (C) 2017 Free Software Foundation, Inc.</div>
<div>License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html></div>
<div>This is free software: you are free to change and redistribute it.</div>
<div>There is NO WARRANTY, to the extent permitted by law. Type "show copying"</div>
<div>and "show warranty" for details.</div>
<div>...</div>
<div><br>
</div>
<div>Then use the "run" command at the (gdb) prompt.</div>
<div><br>
</div>
<div></div>
<div>(gdb) r</div>
<div>Starting program: /usr/local/bin/scribus </div>
...</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">If Scribus crashes, you will get another (gdb) prompt, and you can type "bt" to get the stack backtrace.</div>
<div class="PlainText">
<div>(gdb) bt</div>
<div>#0 0x00007ffff06cfecd in poll () at /lib64/libc.so.6</div>
<div>#1 0x00007fffec9a7166 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0</div>
<div>#2 0x00007fffec9a727c in g_main_context_iteration () at /lib64/libglib-2.0.so.0</div>
<div>#3 0x00007ffff14d66eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5</div>
<div>#4 0x00007ffff148768a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5</div>
<div>#5 0x00007ffff1eb80c7 in QDialog::exec() () at /lib64/libQt5Widgets.so.5</div>
<div>#6 0x0000000000ef675f in ScribusMainWindow::startUpDialog() (this=0x1f05730) at /var/tmp/scribus15/scribus/scribus.cpp:2108</div>
<br>
</div>
<div class="PlainText">Use "quit" to exit gdb.</div>
<div class="PlainText"><span>(gdb) quit</span><br>
</div>
<div class="PlainText"><span><br>
</span></div>
<div class="PlainText"><span>Regards,</span></div>
<div class="PlainText"><span>William</span></div>
<div class="PlainText"><br>
</div>
</span></font></div>
</div>
</body>
</html>