Description: Since latest MacOS and Security update, LibreOffice V5.4.6.2 crashes when requesting "Check for Updates". Crash reports are sent to Apple, but don't think you received them. Going to LibreOffice site, I see Ver. 6.0.7 is available. I will d/l & install to see if problem persists. Steps to Reproduce: 1. Click Help > Check for Updates 2.Crash 3. Actual Results: Crash, Crash report send to APPLE Expected Results: Updates available reported Reproducible: Always User Profile Reset: No Additional Info:
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Budd, 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
I am now running V6.2.12 and no longer suffer that bug, or remember anything that would help you. Thanks for all your work.
(In reply to Budd from comment #3) > I am now running V6.2.12 and no longer suffer that bug, or remember anything > that would help you. > Thanks for all your work. Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.