Bug 95715 - LO, Intel Graphics Driver 520, Surface Pro 4
Summary: LO, Intel Graphics Driver 520, Surface Pro 4
Status: RESOLVED DUPLICATE of bug 95639
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-10 00:48 UTC by libre
Modified: 2015-11-29 19:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description libre 2015-11-10 00:48:26 UTC
(Note: My first time here, so I hope this is correct place to post)

The initial graphics driver on the PC, Intel Graphics Driver 
 10.18.15.4293 works fine. When Win10 does its auto update to 20.19.15.4308, LO either will not start at all or it starts with a black screen.

I am using a new MS Surface Pro 4, Win 10, 64, i5 chip.
Comment 1 Buovjaga 2015-11-12 11:35:17 UTC
Does this help: https://wiki.documentfoundation.org/OpenGL#Crash_on_program_start

Crash on program start

As of September 2015, our latest release (LibreOffice 5.0.2) comes with OpenGL rendering enabled by default. This configuration might cause problems with certain combinations of hardware and drivers, leading to errors or even crashes.

If LibreOffice crashes immediately on startup, it will not be possible to go to Tools ▸ Options ▸ LibreOffice ▸ View to disable OpenGL. In this case, we suggest downloading this registry fragment, which will disable the UseOpenGL parameter.

For more details, please see tdf#93546.
Comment 2 libre 2015-11-13 16:37:29 UTC
I tried that Registry fix several times with no success. It keeps giving me an error.

Not being an expert in these things I am hesitant to change the "fix" but there may a mistake in it. Shouldn't it end with a bracket, ]  ?  

Very hesitant to do this on my own.

Before:

[HKEY_CURRENT_USER\Software\Policies\LibreOffice\org.openoffice.Office.Common\VCL\UseOpenGL]
"Value"="false"
"Final"=dword:1

[HKEY_CURRENT_USER\Software\Policies\LibreOffice\org.openoffice.Office.Common\VCL\ForceOpenGL]
"Value"="false"
"Final"=dword:1

After:

[HKEY_CURRENT_USER\Software\Policies\LibreOffice\org.openoffice.Office.Common\VCL\UseOpenGL]
"Value"="false"
"Final"=dword:1

[HKEY_CURRENT_USER\Software\Policies\LibreOffice\org.openoffice.Office.Common\VCL\ForceOpenGL]
"Value"="false"
"Final"=dword:1]
Comment 3 Buovjaga 2015-11-13 17:33:14 UTC
I don't see why, as there is no "orphan" opening bracket.

Maybe you could open regedit and navigate to the relevant place and do it manually.
Comment 4 libre 2015-11-13 21:36:42 UTC
You must be right, of course. My previous response was only because I am not all that familiar with this.

This is the error when I try to enter the snippet as a *.reg file:

Cannot import C:*****\snippet.reg. The specified file is not a registry script. You can only import binary files from within the registry editor.

[note: I did save the snippet as a txt file. *****is only used as shorthand]

Before that same previous response I did try to enter the data manually. There was no "thread" (don't know what else to call it) after 
[HKEY_CURRENT_USER\Software\Policies\   . I did not want to add anything else to that myself.
Comment 5 Buovjaga 2015-11-14 17:55:03 UTC
The engineering steering committee is considering disabling OpenGL "on by default" for the 5.0.4 release.

They will then focus on a better solution for 5.1.
Comment 6 libre 2015-11-14 19:44:10 UTC
I really appreciate your responses and trying to help me. For a fix, I am a patient guy so no problem waiting for 5.04 and see what happens.
Comment 7 Maxim Monastirsky 2015-11-29 19:34:17 UTC

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