This bug was filed from the crash reporting server and is br-e65424d1-2cc7-4ab6-a56d-85b4573bc66f. =========================================
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
Created attachment 134599 [details] SVG file
Comment on attachment 134599 [details] SVG file Scalable Vector Graphics file downloaded from: https://upload.wikimedia.org/wikipedia/commons/e/e0/FAA_Phonetic_and_Morse_Chart2.svg?download
After opening file "FAA_Phonetic_and_Morse_Chart2.svg" in Draw, as soon as I exported it as a PDF document, the application crashed. The PDF was nevertheless successfully created. Update: The above sequence of events was my experience 2 days ago (July 10, 2017) and also yesterday when replicating the crash. Today, July 12 2017, the application does not crash after the creation of the PDF document. Perhaps when you attempt to reproduce the problem by creating a PDF from the SVG file, you too may not have the experience of the application suddenly crashing. I have no explanation for the difference in outcomes since no settings in the 'PDF Options' dialog box were changed, except one (see below: 'Submit format') The settings were 'default': JPEG compression: 90%; Reduce image resolution set to 300 DPI and the check box ticked; Create PDF form box ticked; Submit format: FDF (initially) / on subsequent conversions, changed to: PDF Export bookmarks box ticked; (Changing 'Submit format' from FDF to PDF did not seem to have any effect on the PDF output.)
I can't reproduce it in Version: 6.0.0.0.alpha0+ Build ID: ddadcb4f4a2bc6538c219a0a577bdf5999015150 CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group nor Version: 6.0.0.0.alpha0+ Build ID: cb37c5f0f3de7b545231a53d46a5271058af76ad CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-23_06:55:41 Locale: es-ES (es_ES); Calc: group
I acknowledge your feedback. I suspected that the problem would not occur again although you attempted to reproduce it. (As mentioned previously, after the first day I too have not experienced the problem of the program crashing.) Thanks for your input and assistance anyway. It's much appreciated.
Hello, Have you been able to reproduce it again? I would suggest to leave this bug in NEEDINFO until further information on how to reproduce it is available, otherwise, there isn't much we can do about it. Regards
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180129
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180302