As in subject, Libreoffice 6.1.6 RC 2 refuses to launch with OpenGL enabled on Windows 10. With OpenGL enabled, it's all OK. If I use the x86 version, it works perfectly. The PC is using only intel GPU hardware (it's a 7th generation core i3).
I can't edit previous comment: - with OpenGL enabled, Libreoffice x64 doesn't start. - with OpenGL disabled, Libreoffice x64 starts. LibreOffice x86 does start with OpenGL enabled.
Could you check you got the last update of your graphic driver (which includes OpenGL part)? Would it be possible you give a try to 6.2.3? Indeed, if it's due to a bug in 6.1.6, since there won't be another 6.1 version according to https://wiki.documentfoundation.org/ReleasePlan/6.1, you'll be stuck. If you still reproduce this, could you take a look to OpenGL part of https://wiki.documentfoundation.org/QA/FirstSteps ?
Installed LibreOffice 6.2.3 x64 (updated from a previous profile with LibreOffice 6.1.6 x86 version with ): - Previously the LibreOffice 6.1.6 x86 version had the OpenGL enabled and working; after the uninstallation of this and the installation of 6.2.3 x64, the launching failed so it restarted with safe mode (OpenGL disabled) - I tried to delete the %APPDATA%\Libreoffice and relaunch the 6.2.3 x64 version, it worked perfectly with OpenGL disabled! I suspect that there's some conflict with x86 and x64 profiles...
Thank you for your feedback In general, I may be wrong but I think it's safer to clean the profile if you switch from x86 to x86-64 (or the reverse) With x86-64 and a brand new profile, do you confirm it fails with OpenGL enabled? If yes, depending on the time you got, either you can stick with x86 version or disable OpenGL or do these: - provide <user profile>/cache/opengl_device.log - retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace) - retrieve OpenGL debug (https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_how_to_get_OpenGL_debug_output)
(In reply to Julien Nabet from comment #4) > In general, I may be wrong but I think it's safer to clean the profile if > you switch from x86 to x86-64 (or the reverse) > > With x86-64 and a brand new profile, do you confirm it fails with OpenGL > enabled? No: as I said before, it fails ONLY with an existent x86 profile. You can close this bug :-)
Ok I had wrongly understood. Let's close this one then.