Bug 116500 - No text is displaying in any of the applications
Summary: No text is displaying in any of the applications
Status: RESOLVED DUPLICATE of bug 112305
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-19 15:44 UTC by rogerpalmer15
Modified: 2018-03-19 20:23 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rogerpalmer15 2018-03-19 15:44:56 UTC 
Description:
No menus or any headings displaying, just lines.
I am therefore unable to access any of the commands.
i am also unable to access the user profile, if that is the problem.

Actual Results:  
Upon opening Libre Office or any of it's applications

Expected Results:
No texts are displayed


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299
Comment 1 V Stuart Foote 2018-03-19 20:23:41 UTC 
Disable OpenGL rendering.

You'll need to add the below stanzas with a text editor to your profile configuration--registrymodifications.xcu in the %APPDATA%\LibreOffice\4\user folder.

They won't be there with a new default profile, because on Windows builds OpenGL is enabled (unless it was black-listed); once the stanzas are added they can be edited true or false as needed.

<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="ForceOpenGL" oor:op="fuse"><value>false</value></prop></item>
<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseOpenGL" oor:op="fuse"><value>false</value></prop></item>


Also, please let us know what GPU and driver your system has (from Windows msinfo32.exe) 

You can probably resolve with a driver update. But for now marking as duplicate of bug 112305

*** This bug has been marked as a duplicate of bug 112305 ***