Description: I turned on my computer and logged into it. Then a crash report came up. I have LibreOffice quickstarter set to startup on login. Steps to Reproduce: 1.Turn computer on 2.Login 3.Submitted crash report... Actual Results: Everything seems to be working Expected Results: Everything seems to be working. Reproducible: Didn't try User Profile Reset: No Additional Info: crashreport.libreoffice.org/stats/crash_details/2be62e1f-5a50-4098-93f7-8cd389961802. ---Paste from About--- Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 12; OS: Windows 10.0; UI render: GL; Locale: en-US (en_US); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Not reproduced with quickstarter. Win 10 64-bit Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group
don't repro on Windows 7 32 bit Version: 6.0.0.2 Build ID: 06b618bb6f431d27fd2def25aa19c833e29b61cd CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: ru-RU (ru_RU); Calc: group
Kevin: it does not crash, if you disable quickstarter?
not reproduced on Win 7 64bit Version: 6.0.0.3
http://crashreport.libreoffice.org/stats/signature/google_breakpad::ExceptionHandler::HandlePureVirtualCall%28%29 shows 22585 crash reports in Windowd x64, last being 6.0.0.3. And this is the only bug reported. So I'll confirm, regardless we don't have steps.
(In reply to Buovjaga from comment #3) > Kevin: it does not crash, if you disable quickstarter? OTOH, does it crash if OpenGL is disabled ? -> https://wiki.documentfoundation.org/OpenGL
(In reply to Buovjaga from comment #3) > Kevin: it does not crash, if you disable quickstarter? Well, it wouldn't if quickstarter were disabled. It seems to be crashing from quickstarter - or more accurately it appears to be quickstarter that is crashing. I just logged into my computer and was eventually greeted with another error message. I'll try to figure out where the logs are and where I can upload them here to add to this.
Created attachment 139683 [details] Shows the error message pop up. Started the computer today and logged into windows. After a few minutes of up time this error message popped up.
Created attachment 139684 [details] Eventlog details of crash Here are the evenlog details regarding the pop up error message.
Created attachment 139685 [details] GL Report A comment asked about Open GL so I downloaded the app and included this report.
(In reply to Kevin W. Gagel from comment #9) > Created attachment 139684 [details] > Eventlog details of crash > > Here are the evenlog details regarding the pop up error message. The faulting module is ucrtbase.dll. About the dll it is said "It's a critical part of Windows and without it being present no dynamically linked programs compiled with Visual Studio 2015 or later will run (they will crash instead)" Kevin: did you check the OGL setting? Tools - Options - LibreOffice - View - Use OpenGL for all rendering
I checked the "Use Open GL..." setting. It was off (unchecked). I added check to it and restarted LibreOffice. Oddly the error message did not show up today after I turned the computer on and logged in. I'll see how this goes and if it makes a difference or not.
I have not seen the error since turning on the Use Open GL setting.
Completely different issue than bug 115420 and dupes -- removing. With original STR and quickstart & OpenGL configuration, could really use a crashreport via BreakPad automated reporting. Or it may be necessary for OP to attach the soffice.bin process to a WinDbg 64 session with Symbol File path pointing back to LO servers, and catch a "~* kp" stacktrace at crash.
There is nothing conflict between quickstarter is enabled and Use Open GL disabled. You should check the proper setting of them. if you are not able to do so. Then you may take help from link https://www.windowstechnicalsupportnumbers.com/ It is very helpful for libre office problem. I have also taken many time help from them for a various problem like outlook login problem and libre office issue.
Dear Kevin W. Gagel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Kevin W. Gagel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Nobody could confirm. I set Needinfo for a reporter to see if it happens Still or maybe resolved with a Bug 141769 that was fixed in 7.1.5.
Dear Kevin W. Gagel, 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
Dear Kevin W. Gagel, 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-FollowUp