Bug 113447 - Crash in: RTSPaperPage::update()
Summary: Crash in: RTSPaperPage::update()
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-25 14:32 UTC by Peter Maunder
Modified: 2017-10-29 17:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["RTSPaperPage::update()"]


Attachments
Writer Document caused the crash on Brother Duplex Laser printer (32.76 KB, application/vnd.oasis.opendocument.text)
2017-10-25 14:37 UTC, Peter Maunder
Details
gdbtrace.log from crash as requested (29.82 KB, text/x-log)
2017-10-27 16:39 UTC, Peter Maunder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Maunder 2017-10-25 14:32:05 UTC
This bug was filed from the crash reporting server and is br-b1d8fef8-447f-4a4f-9876-b26cedb5074e.
=========================================
Imported a .docx 6 page document. Saved as .odt, changed the page size using points as the measurement, happened with and without footer. Change font from Calibre 11 pt to Franklin Gothic Book 12 point. Page simplex to duplex, crashed trying to print.
Comment 1 Peter Maunder 2017-10-25 14:37:55 UTC
Created attachment 137285 [details]
Writer Document caused the crash on Brother Duplex Laser printer

See bug 113447
Comment 2 Xisco Faulí 2017-10-25 14:44:55 UTC
Hi Peter,
Do you reproduce it if you print it to a file?
You just change the Duplex option to Long edge, right ?
Comment 3 Peter Maunder 2017-10-25 14:58:15 UTC
Hi Xisco Faulí,

1 Yes I changed the printing from SIMPLEX to Duplex Long Edged (default).

2 I can print to a a file  (.pdf) without problems.

Thank you for such a speedy comment.
Comment 4 Xisco Faulí 2017-10-25 20:48:21 UTC
Could you please download a debug build from here: http://dev-builds.libreoffice.org/daily/master/ ( the ones with -dbg at the end ), and get a backtrace as explain here: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace ?
Comment 5 Peter Maunder 2017-10-27 16:39:21 UTC
Created attachment 137326 [details]
gdbtrace.log from crash as requested
Comment 6 Jean-Baptiste Faure 2017-10-27 20:53:06 UTC
set version from crash report.

Best regards. JBF
Comment 7 Xisco Faulí 2017-10-28 18:14:40 UTC Comment hidden (obsolete)
Comment 8 Peter Maunder 2017-10-29 16:36:44 UTC
Hi Xisco,

I tried the daily/master build as you requested. I am pleased to say the problem does NOT occur with the daily/master build. I have therefore left the status as 'NEEDINFO' as you suggested. 

Thank you for your help... Peter
Comment 9 Xisco Faulí 2017-10-29 17:09:12 UTC
Thanks for testing it again. Closing as RESOLVED WORKSFORME