Ubuntu
scribus-ng package

Scribus crashes due to Signal #6

Bug #239227 reported by BHowell
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Scribus
Fix Released
Unknown
scribus-ng (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: scribus-ng

Ubuntu 8.04 amd64 with latest updates

package: 1.3.4.dfsg+svn20071115-1ubuntu1

In the "Story Editor" selecting text will randomly trigger "Scribus crashes due to Signal #6". This bug makes scribus almost unusable for me as it is so unstable. This should take a high priority.

One random theory is that this is an amd64 bug related to casting an int for the selected text length.

The only debug output I have is here:

scribus-ng: /build/buildd/scribus-ng-1.3.4.dfsg+svn20071115/scribus/text/storytext.cpp:406: QChar StoryText::text(int) const: Assertion `pos < length()' failed.
Scribus Crash
-------------
Scribus crashes due to Signal #6
Calling Emergency Save

Revision history for this message
Łukasz Jernaś (deejay1) wrote :

Does this happen with the latest stable version? (1.3.3.11)
Please do not use 1.3.4* as it is an abandoned development version!

Revision history for this message
joonasl (joonas-lyytinen) wrote :

I have exactly the same problem which makes using Scribus extremely problematic. On top of crashing all the time, the text editor also randomly messes up text when updating the text frame and makes me do and re-do the work I have done again and again.

I am using version 1.3.3.11 of Scribus on Ubuntu 8.04

This is very urgent, since it's making me miss deadlines!

Revision history for this message
Jan Sander (jan-sander) wrote :

I have the same "Signal 6" problem. Using UBUNTU 9.10 on AMD 64 bit system and Scribus version 1.3.5. Is there a solution or work around? In its current state Scribus is barely usable for any serious work.

Revision history for this message
bowman (tereshkosg) wrote :

I had same ("Signal 6" ) problem with one of my files when tried to open it. I am using 1.3.5.1 on 64bit machines AMD and Intel.

The way I "fixed" it .... opened .fla file in a text editor. Started deleting xml nodes one by one and found that when I deleted one of the <FRAMEOBJECT ... file opened. Then I started looking inside of this node and found <ITEXT CH="{some weird character here}" COBJ="2"/>. Replaced that character with something and file opened. Not exactly sure what this tag means - it did not seem to change anything in the layout. May be I just did not notice ....

In my opinion it is a horrible fix ... and this bug must be looked into by the developers.

Bug Watch Updater (bug-watch-updater)
Changed in scribus:
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in scribus:
status: New → Invalid
Revision history for this message
James King (jlking3) wrote :

I'm not sure why this bug is now on an "invalid" status as of May 8. I'm having issues with this bug too, although I'm not as good as the previous people as far as trying to trace it. When the crash happens to me, it happens when I'm selecting text to be removed or changed. The text usually has a diacritic mark on it that I had copied and pasted from another source, but not always.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

It is not really on "invalid" status, unfortunately launchpad misses the feature to detect the duplicate status in upstream bug trackers. I fixed the link to the upstream bug tracker - the correct bug says it is fixed upstream.

Changed in scribus:
status: Invalid → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in scribus:
status: Unknown → Fix Released
Revision history for this message
Hendrik Cornelius de Beer (mosesdebeer) wrote :

I received a "Scribus crashes due to Signal #6" while using Scribus 1.3.8 and Ubuntu 10.04 Lucid Lynx. This happened when I went into the text editor, clicked on the style of one of the paragraphes, clicked to edit the styles, selected a paragraph style and said "CLONE". I had to close Scribus. I opened it again and did the same on a different text column on a different page. It worked (Nothing happened I did not receive the error again). Though I must say it is very sad that I had to close scribus.

Although this is a bug report I just want to tell the developers: Keep up the good work! What you are doing means amazing things. Profesional DTP on a low budget changes the world! Save a tree. Buy something with no box!!

Revision history for this message
Tristan Rily Borque (tris8923) wrote :

I have had scribus crash so many times on me it sucks it happens every time i Need someone to figure this out. I use version 1.3.8 please tell me who to get out of this! I have been working on projects that need to be brocheres but IT keeps crashing dus to signals 6 and 11. please fix!

Revision history for this message
gd_ab (gd-ab) wrote :

I use Scribus 1.3.8 on Ubuntu 10.10 and it crashes for some reasons, I don't know.
Please fix it ASAP, I cannot edit my work.

Revision history for this message
Philip Muškovac (yofel) wrote :

For those with crashes, can you please edit /etc/default/apport so enabled is set to 1, reboot, and then please file a crash report using apport when this happens again? Without a stacktrace or exact, detailed steps how to reproduce the crash nothing can be done.

You can also try to install a newer scribus-ng version by following http://wiki.scribus.net/canvas/Debian

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

You can also enable apport temporarily without any reboot, just run
  sudo service apport start force_start=1
in a terminal.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in scribus-ng (Ubuntu):
status: New → Confirmed
Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

It seems to be a privilegies problem...

Workaround:

* Open a terminal
* gksu scribus

It works!

Ubuntu 12.04 up-to-date (32 & 64 bits)

Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

Another workaround, not requiring superuser privilegies:

https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/891681

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.