Created attachment 123023 [details] Impress display defect in Presentation mode. Environment: LO 5.1.0.3 (x64) on Microsoft Surface Pro 4 i7/8GB/256GB running Windows 10 64-bit This bug is related/similar to bug ID: 98182 and 97943. In Presentation mode, screen content split vertically (see screen capture). Enable OpenGL rendering option (Tools-Options-LibreOffice-View) would fix the display defect. However, Impress would crash consistently in no more than 3 advances of the slides.
Created attachment 123024 [details] Impress in Edit mode. Everything's a'ok.
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
Created attachment 123036 [details] Sample ODP document No specific sample document is required to reproduce this bug. Simply start up Impress, a new blank presentation document will be displayed. No need to enter any Title or text on the screen. Press F5 to display this slide in presentation mode. You will see the display defect similar to the earlier screen capture attachment filed here titled "Impress display defect in Presentation mode". Here's a sample .ODP file if you insist. The problem does not lie within the .ODP. In fact, any .ODP file would trigger the same issue.
This display defect could be occurring on specific hardware configurations only. I suspect those machines with HiDPI displays. Bug 98182 reported the same issue, on a Lenovo Yoga 900, Windows 10 Home and built in graphics Intel HD graphics 520. The Yoga 900 comes with 13.3-inch 3200x1800 resolution display. I am seeing this issue on a Surface Pro 4 i7/8GB/256GB with 6th Gen 2.2-GHz Intel Core i7-6650U processor with Intel Iris graphics 540. The Surface Pro 4 comes with 12.3-inch 2736x1824 resolution display.
I have just tested LO 5.1.0.3 (x64) on Windows 10 with a 24-inch 1920x1080 resolution display. Presentation mode worked flawlessly. So this further indicates that only those with HiDPI machines would encounter this bug. BTW. OpenGL rendering option (Tools-Options-LibreOffice-View) must be disabled on this machine. Otherwise Impress would crash in no more than 3 advances of the slide deck in presentation mode. Is this a separate OpenGL bug/issue?
Please close this bug report. Problem fixed by (DISABLING Graphics hardware acceleration) AND (Do not use OpenGL for rendering). These options are in Tools-Options-LibreOffice-View.
(In reply to KB Lee from comment #6) > Please close this bug report. > > Problem fixed by (DISABLING Graphics hardware acceleration) AND (Do not use > OpenGL for rendering). These options are in Tools-Options-LibreOffice-View. It is still a bug, though. Please give us the contents of this file in your Surface Pro 4: C:\Users\User\AppData\Roaming\LibreOffice\4\cache\opengl_device.log You can also try 5.1.1 after it is released next week. It has a lot of OGL fixes.
Created attachment 123067 [details] opengl_device.log from Surface Pro 4 i7/8GB/256GB Here's the opengl_device.log for your reference.
Would be really good to re-test with 5.1.1.2 - http://dev-builds.libreoffice.org/pre-releases/win/x86_64/LibreOffice_5.1.1.2_Win_x64.msi if you can. Tomaz - interesting to you ?
Installed LO 5.1.1.3 (x64) yesterday. I am glad to report Impress presentation mode worked great at default Graphics Output setting, whether on single-monitor or dual-monitor set-up. I have yet to run into crashes when advancing slides and moving in and out of presentation mode. Well done and thank you. ================ Environment: LO 5.1.1.3 (x64) on Microsoft Surface Pro 4 i7/8GB/256GB running Windows 10 64-bit. Default Graphics Output setting: * Use hardware acceleration - unchecked. * Use anti-aliasing - checked. * Use OpenGL for all rendering (on restart) - checked. * Force OpenGL even if blacklisted (on restart) - unchecked. Current GL status: Enabled. =================
Thanks for testing, closing the bug.