[scribus] Scribus Crashes due to Signal #6 (or #11)

William Bader williambader at hotmail.com
Tue Jul 11 11:59:31 UTC 2017

From: xemoth at gmx.com <xemoth at gmx.com>

Sent: Tuesday, July 11, 2017 4:20 AM
To: scribus at lists.scribus.net
Subject: Re: [scribus] Scribus Crashes due to Signal #6 (or #11)

> > I run Scribus 1.5.2 on Linux Kubuntu 16.04
> >
> > Scribus crashes randomly with the message "Scribus Crashes due to Signal
> > #6" (or Signal #11)
> > This happens about once a day -- not much, but very irritating.
> >
> > If I restart Scribus it reopens with no problem and everything is fine,
> > nothing out of place or deleted.
> >
> > I cannot identify any single keystroke or set of keystrokes that trigger
> > the crashes.
> >
> > What does Signal #6 or #11 actually indicate?
> >
> > How can I fix this?

To find out what signals mean, you can use "man 7 signal" or "kill -l".  Signal 6 SIGABRT can mean that the application failed an internal test and decided to terminate itself by calling abort(). Signal 11 SIGSEGV (segmentation violation) means that the application made an invalid memory reference and the Linux kernel killed it.

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.

Here is an example,
Start scribus under gdb. (If you want to pass options to scribus, look at the gdb "set args" command.)

$ gdb /usr/local/bin/scribus
GNU gdb (GDB) Fedora 7.12.1-48.fc25
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.

Then use the "run" command at the (gdb) prompt.

(gdb) r
Starting program: /usr/local/bin/scribus

If Scribus crashes, you will get another (gdb) prompt, and you can type "bt" to get the stack backtrace.
(gdb) bt
#0  0x00007ffff06cfecd in poll () at /lib64/libc.so.6
#1  0x00007fffec9a7166 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007fffec9a727c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007ffff14d66eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#4  0x00007ffff148768a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007ffff1eb80c7 in QDialog::exec() () at /lib64/libQt5Widgets.so.5
#6  0x0000000000ef675f in ScribusMainWindow::startUpDialog() (this=0x1f05730) at /var/tmp/scribus15/scribus/scribus.cpp:2108

Use "quit" to exit gdb.
(gdb) quit


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20170711/e875ed87/attachment.html>

More information about the scribus mailing list