Description: Tried to open a .xls file in LO but LO window did not appear. Eventually looked in W10 Task Manager and found a number of LO processes running. Killed them all and rebooted laptop. When restarted LO it came up with a recovery message and then opened main menu before reporting a crash had occurred. Steps to Reproduce: 1. Killed LO in Task Manager after main window failed to open when trying to open a file 2. Rebooted PC 3. Restarted LO and got a recovery message before main window appeared Actual Results: System reported a crash and advised me to raise a bug report: crashreport.libreoffice.org/stats/crash_details/fa8ce3ef-bb89-45bf-9e43-f2903be8c4d8 Expected Results: Have got LO to run normally after starting it in safe mode. I have been a LO user for several years and love it, but I do feel that my current version is unstable, which is a concern! Reproducible: Sometimes User Profile Reset: No Additional Info: I have had this crash once before on 22 May 2018 - see crashreport.libreoffice.org/stats/crash_details/679ec043-2d9f-4827-965b-cbc7974c3c92 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36
Could you check you use last graphic driver (for OpenGL part)? Could you give a try to brand new 6.0.4 Finally, could you give a look to https://wiki.documentfoundation.org/QA/FirstSteps ?
1. According to my Device Manager I have Intel HD Graphics HD440 and drivers are up to date. OpenGL is ver 4.3 2. I am reluctant to instant LO version 6 as I am a conservative user. 3. My LO Help\About shows LO is set to 'UI render - default'
Just for curiosity, can you try to open the xls file again? Indeed, I wonder if LO didn't disable OpenGL after the crash.
At the moment OL is opening a variety of files without any problem. This does appear to be an intermittant issue,
BTW, did you WIN 10 get updated recently?
Yes, it upgraded to W10 version 1803 on 23 May
For the test, it could be interesting you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and reinstall your extensions if any. Indeed, it'll force LO to rescan your config.
I am unclear whether you are asking me to rename my profile (registrymodifications.xcu) or the folder containing it (user). If you mean the profile, I have regenerated this several times in the last few days. I do not know how to reinstall extensions but I only have 5 - English, French & Spanish Dictionaries, Solver for Nonlinear Prrogramming and Wiki Publisher.
(In reply to Martin Terry from comment #8) > I am unclear whether you are asking me to rename my profile > (registrymodifications.xcu) or the folder containing it (user). If you mean > the profile, I have regenerated this several times in the last few days. > > I do not know how to reinstall extensions but I only have 5 - English, > French & Spanish Dictionaries, Solver for Nonlinear Prrogramming and Wiki > Publisher. Sorry, I was talking about renaming the whole directory. About extensions, it seems you've got only those bundled in LO so no need extra steps install to have them again.
I have renamed the <user> folder and successfully run LO. From the nature of your suggestions I gather that you think that some sort of corruption in the configuration data caused the crashes that I had, rather than a fault in the coding. If this is the case only an extended period of running will prove it. Perhaps you could advise what the crash report showed/what you think the problem is. I am not an expert on the inner working of LO (although I have learned a lot in the last 2 weeks) but I am an ISTQB qualified software tester (now retired). Julien, I want to thank you for your attention to this problem. As a long term LO user who got fed up with Microsoft continually changing the design of its Office suite I have been very happy with LO as an excellent alternative and appreciate the efforts of its developer and support coummunity.
Thank you for your feedback Martin. The corruption can also be due to a LO coding problem in a former version. Indeed, fixing a LO bug (or whatever the software) can't fix automatically the files corrupted with the buggy version. Since you seem not having installer 3th party extension, it may due to a bug in a former LO version. Now, as you indicate, only time will tell if renaming profile directory sufficient or not. Perhaps the bug is still there after all. If you still reproduce the crash, these elements can obviously help: - a link to the crashreport (as you already done but this time we'll be sure it won't be related to the profile) - a minimum step by step process to reproduce this. Perhaps it'll need a specific xls file. In this case, take a look to https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission - attach <user profile>/cache/opengl_device.log (as indicated in https://wiki.documentfoundation.org/QA/FirstSteps) since your first crashreport showed OpenGl part BTW, have in mind that if you use LO 64 bits, you need Java 64 bits. If you use LO 32bits, you need Java 32 bits.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181203
I have not encountered this crash since I reported it in June. I am now running LO ver 6.0.7.3 and I have had a number of W10 updates. I suggest you close this bug report as the crah has not occurred again. Thank you for your attention to this issue.
Thank you Martin for your feedback, let's put this one to WFM then.