Created attachment 150578 [details] Screenshot of badness Durgapriyanka noticed this in bug 123682. 1. Open attachment 149554 [details] (on Windows) 2. Start presentation This is not seen on Linux. This is not seen in the newest commit of win32-5.4 bibisect repo, but is already in the oldest of win32-6.0. This is seen in 5.4.2. The old behaviour is worse - whole lines are cut off. If others get the same result, we can remove the bibisect request and add notBibisectable. Version: 6.3.0.0.alpha0+ (x64) Build ID: 9956cf0692058414ef3efdb0e8058fbb0b39f6bc CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-04-04_02:20:31 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
I can't reproduce it in Versión: 6.2.2.2 Id. de compilación: 2b840030fec2aae0fd2658d8d4f9548af4e3518d Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded nor in Version: 6.3.0.0.alpha0+ Build ID: d31d77b7199ecc9a7edc899d9703e9da52d5cbd1 CPU threads: 1; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-04-01_00:04:09 Locale: es-ES (es_ES); UI-Language: en-US Calc: threaded Putting it back to UNCONFIRMED see if other people can reproduce it...
Putting this back to NEW, because it was seen by two different people. Re-confirmed in Safe mode just now.
Marco confirmed this on IRC with 6.2.2 on Win 10
Good news is that this anomaly is not seen with Skia in a fresh master build.
Repro 7.1+ Win GDI.
Dear Buovjaga, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still repro Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 6834fda784f3066a89838cd6cda4fe945f4c7904 CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded Jumbo