Bug 116562 - LibreOffice crashes on start. Both "LibreOffice Desktop apps" and Calc, Writer, etc. Windows 10
Summary: LibreOffice crashes on start. Both "LibreOffice Desktop apps" and Calc, Write...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-22 12:09 UTC by reycat
Modified: 2018-11-05 16:11 UTC (History)
1 user (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 reycat 2018-03-22 12:09:05 UTC
Description:
Newly bought Windows 10 Home x64 computer. 

LibreOffice_6.0.2_Win_x64 downloaded and installed. When I try to start any of the components (Calc, Writer, the main LibreOffice app), I get a "LibreOffice has stopped working" error.

"A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available".

Rebooting didn't help. Neither uninstalling and reinstalling LibreOffice.

Safe mode works, 'though. ***Disabling hardware acceleration there fixes the problem.***

Steps to Reproduce:
1.Click on any LibreOffice application icon.
2.Get a nice crash. :)

Actual Results:  
Two small error windows, both with the text "LibreOffice has stopped working". The first one has a progress bar and the text "Hang on while Windows reports the error to Microsoft"

The second one just the text "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available"

Expected Results:
The chosen application (Writer, Calc...) should open.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.0.2.1 (x64)
Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
CPU threads: 8; OS: Windows 10.0; UI render: default; 
Locale: en-GB (en_GB); Calc: group

(in order to copy it I had to use the Safe mode). 

I don't know if OpenGL is enabled or not, but this is my graphic card.

Renderer: Intel(R) HD Graphics 630
Vendor: Intel
Memory: 1024 MB
Version: 4.4.0 - Build 21.20.16.4550
Shading language version: 4.40 - Build 21.20.16.4550


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Comment 1 Xisco Faulí 2018-03-22 12:29:17 UTC
Does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 2 Timur 2018-03-22 14:38:23 UTC
I understand that is the first LO on that computer, not an upgrade? 
Please write exact Windows 10 version. 
Could you try with master LO version from http://dev-builds.libreoffice.org/daily/master/ both 32-bit and 64-bit? Like https://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/ and https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/. That dev version will not mess with your regular LO.
Comment 3 QA Administrators 2018-10-09 11:27:28 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2018-11-05 16:11:59 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20181105