Installed LibreOffice 5.0.2 on Surface Book (model with 256gb ssd, 8gb memory, and discrete graphics) day it arrived (Oct 26, 2015). Worked well. Then on Nov 3, Surface Book updated with "System Firmware Update - 11/2/2015" which is known to included display driver updates. When I next opened LibreOffice, the frame was all black except for title bar. Today (Nov 4), I installed version 5.0.3 and it has the same problem. BTW Installed version 4.4.6 and ti works correctly. Have reported the issue to Microsoft as well.
This is probably something related to the OpenGL support. You can try the workaround described in bug 94686 comment 3, about modifying an .xcu file, which is located in the %APPDATA%\libreoffice\4\user\ folder.
also consider upgrading to LibO 5.0.3.2 which has been released a few days ago. many bug fixes have been done in respect to 5.0.2.2
Any news regarding the suggestions in comment 1 + 2? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Please test with 5.0.3. The fix for Bug 94686 might fix this one as well.
Confirmed that this problem is still present with LibreOffice 5.0.3.2 both x86 and x64 on Windows 10 professional build 10586 (November 2015 update) with all updates as of time of writing. So NOT FIXED, previous comments with potential bug fixes aren't applicable.
Updated to current version tested.
Problem went away, as described in comment 1. Specifically, added the line to my %APPDATA%\libreoffice\4\user\registrymodifications.xcu file <item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseOpenGL" oor:op="fuse"><value>false</value></prop></item>
Note, this issue occurs for both 64-bit and 32-bit installs of 5.0.3.2 on Win10 x64 Professional.
(In reply to Jason C. from comment #6) > Updated to current version tested. this is wrong. did you notice that the version field says "earliest affected" ? reverting to 5.0.2.2
Setting to NEW as we have confirmation.
Is it the same as Bug 95639?
(In reply to Maxim Monastirsky from comment #11) > Is it the same as Bug 95639? I can't say, but the effects look very much the same. I would suggest closing this bug and keeping #95639 open. Differences between this and the other bug: * Found in 5.0.2.2 / 5.0.3.2 * This only occurred after a FW update on the Surface Book.
*** This bug has been marked as a duplicate of bug 95639 ***