Description: When inserting some large text into a slide, some of the text has line-shaped holes in it. They seem to have a fixed position on the screen. Here are some screenshots: https://hub.sealcode.org/file/data/ptdfj4oni2d5cliqhzxo/PHID-FILE-wnvvgjrl74d4u4rra7xc/2020-01-28_21-46.png https://hub.sealcode.org/file/data/53pvn6upyfpup7hv6tem/PHID-FILE-va3gitecduo6zygppck3/2020-01-28_21-47.png Disabling Hardware acceleration solves the problem. Steps to Reproduce: 0. Enable Hardware Acceleration in settings 1. Insert some large text (32pt is enough to see the result) 2. It looks ok while editing the slide 3. Start the presentation Actual Results: The text has line-shaped holes in it Expected Results: Text should not have line-shaped holes in it Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 6.2.8.2 Build ID: 6.2.8-4 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.utf8); UI-Language: en-US Calc: threaded
6.2 is pretty old. Maybe try with a more recent version. An appimage is an easy method: https://libreoffice.soluzioniopen.com/ Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
I've just checked 6.4 and could not reproduce the problem.
I've just checked in 7.0.0.3 and the problem is back. The lines appear when the hardware acceleration is on, and disappear when the accelerations is off
Do they also appear, if you launch from the command line with SAL_USE_VCLPLUGIN=gen libreoffice
With this flag the UI looks very oldschool, but the white lines are gone. Both with hardware acceleration on and off
Thanks, it must be somehow hardware-specific, sadly. I am not seeing the lines. Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: 2db30aa0206ca3d9d5a665d550820d8fcbcff4b9 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 3 September 2020
Hello Kuba, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Kuba Orlik, 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
Dear Kuba Orlik, 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-FollowUp