Description: When using LibO to deliver presentations, so that one has a laptop and a projector attached to it, LibO nicely differentiates the outputs between the two. The projector displays the current slide, while the laptop screen provides the presenter's screen that includes notes, a timer, a view of the current slide and a view of the next slide. The presenter's screen is invaluable in helping the presenter deliver a high quality presentation. Unfortunately, with the current LibO the two views of the current and the next slide have issues that hinder the value of the presenter's screen. Specifically, when a slide contains a lineart drawing with thin lines, these are not rendered at all in the presenter's screen. If a slide contains only a drawing with thin lines, the view of the current slide on the presenter's screen becomes completely useless. Steps to Reproduce: 1. Create a presentation with a slide containing a drawing with thin lines (e.g. 0.2 mm in width). 2. Run the presentation with an external screen attached to the computer, so that LibO shows the presenter's screen 3. See that the current slide (or the next slide) view in the presenter's screen misses part of the drawing. The issue should be quite easy to reproduce. If needed, I can provide a sample case. Actual Results: Lines are missing in the slide views in the presenter's screen Expected Results: The slide should be scaled down preserving its features, i.e., without parts of it disappearing completely. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: PresentationDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
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-20180731
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-20180903