View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005262 | Scribus | - | public | 2007-01-28 18:09 | 2008-01-14 23:02 |
| Reporter | sherwood | Assigned To | jghali | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Platform | Intel PC | OS | Fedora | OS Version | Core 6 |
| Product Version | 1.3.3.6 | ||||
| Summary | 0005262: Scribus crashes due to Signal 0000006 on printing | ||||
| Description | Scribus 1.3.3.6, under Fedora Core 6 I have a 64-page document. When I try to print, or print preview, a single page, after a long pause I get "Scribus Crash/Scribus crashes due to Signal 0000006". The page in question contains 1 text frame filled with ordinary text in a single font, and 1 image frame with a JPEG image. It is page 2 of the document. The page displays approximately correctly on the screen when the document is opened, and page is advanced from page 1 to page 2. There is a master page; the master has 1 line of text and the page number at the top of the page. At the time of the crash, the Printing File dialog contains Overall Progress: 75% Processing Master Pages: 66% Exporting Pages: 0% The printer is HP LaserJet 5000, connected via Windows network and Samba. It prints simple text documents OK. | ||||
| Additional Information | I would like to try to fix this bug myself. I will need some information on how to debug Scribus under Linux. Is that available anywhere? | ||||
| Tags | No tags attached. | ||||
| Patch | |||||
|
|
Smells like a broken image. Can you do File > Collect for output and attach it here to the bug. If you want you can make this bug private and only developers will have access. |
|
2007-01-28 23:09
|
|
|
2007-01-28 23:10
|
|
|
|
I have created a brief test file which exhibits the same crash. I have uploaded both the .sla file and the compressed version that was created by "Collect files...". The image in the file is the one I have previously made available. |
|
|
Don't have it anymore. May you upload it again? |
|
|
The image file is now available at http://rapidshare.com/files/13990098/1994_Apr_013.jpg.html |
|
|
I can't reproduce the crash here with 512Mo ram. The image size being quite important (something like 4000x6000), memory needed to just store it is around 96 Mo. More memory is in fact needed to allow decompression. |
|
|
Basically a duplicate of 0004189 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-01-28 18:09 | sherwood | New Issue | |
| 2007-01-28 21:49 |
|
Note Added: 0015029 | |
| 2007-01-28 23:09 | sherwood | File Added: Test.sla.gz | |
| 2007-01-28 23:10 | sherwood | File Added: Test.sla | |
| 2007-01-28 23:11 | sherwood | Note Added: 0015031 | |
| 2007-01-29 20:01 | jghali | Note Added: 0015037 | |
| 2007-01-29 20:37 | sherwood | Note Added: 0015038 | |
| 2007-01-31 23:04 | jghali | Note Added: 0015058 | |
| 2007-01-31 23:14 | jghali | Relationship added | related to 0002438 |
| 2008-01-14 23:02 | jghali | Relationship added | duplicate of 0004189 |
| 2008-01-14 23:02 | jghali | Duplicate ID | 0 => 4189 |
| 2008-01-14 23:02 | jghali | Status | new => resolved |
| 2008-01-14 23:02 | jghali | Resolution | open => duplicate |
| 2008-01-14 23:02 | jghali | Assigned To | => jghali |
| 2008-01-14 23:02 | jghali | Note Added: 0018585 | |
| 2008-01-14 23:02 | jghali | Status | resolved => closed |
