Description: When typing text into a blank Writer document while VoiceOver is running, LibreOffice immediately crashes. Steps to Reproduce: 1. On a Mac, turn on VoiceOver. 2. Start LibreOffice. 3. Select Create new Writer document. 4. If the Tip Of The Day screen appears, dismiss it. 5. In the blank document that appears, type a single letter, doesn't matter which. Actual Results: LibreOffice closes completely, and sometimes the Apple Crash Reporter tool comes up. Expected Results: No crash. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Mac OS X 13.1; UI render: default; VCL: osx Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded The installation is a fresh install of LibreOffice with hardly any customization. IIRC, the only thing I entered into the Options dialog was my address information.
Hi Marco, thanks for your report. Tried reproducing the problem with VoiceOver active was able to type in LibreOffice 7.4.3.2 and current daily build. Are you able to attach a crash log to this bug report or if that is not possible maybe just send a link using a pastebin with the crash log.
Hi Steve, would love to, but have absolutely no clue where to find the crash reports, IDs, or signatures. A Google search also didn't reveal anything. Can you give me some pointers?
You can take a look at '~/Library/Logs/DiagnosticReports' and '/Library/Logs/DiagnosticReports' in Finder. Or reproduce the crash which should bring up macOS crash reporter allowing to show details and then copy the crash log to a pastbin in your browser e.g. https://bin.disroot.org/
Created attachment 184019 [details] Two crash reports The Apple Crash reporter doesn't come up consistently, but I found two reports in the DiagnosticReports folder and am attaching the ZIP archive here.
Hi Marco, I added your email as a user for the build in the appstore via testflight. Would be great if the problem can be reproduced there, since we would have debug symbols for those builds that the crash report can be matched against. If you manage to reproduce the crash in the testflight build, please mention this bugreport, then I can provide a resolved trace. (unfortunately builds are still stuck in review for Beta App testing, so cannot provide a public testing link, but have to invite people individually :-/) If you don't want to try with testflight, that's totally fine as well, just ignore the mail then.
Hi Christian, I'd be happy to try and reproduce with a TestFlight build. I do testing for other Mac apps via TestFlight, too, so this environment is familiar to me. I'll be sure to mention this bug report when I do reproduce the problem and send in the report.
I couldn't reproduce a crash with: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fe845e40ab23a3fa9fd401498edf925b7b00776f CPU threads: 2; OS: Mac OS X 12.6.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 2; OS: Mac OS X 12.6.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I also tried with DE locale and UI: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 2; OS: Mac OS X 12.6.1; UI render: default; VCL: osx Locale: de-DE (en_US.UTF-8); UI: de-DE Calc: threaded Marco, do you know what was the latest version you could use without a crash?
(In reply to Stéphane Guillou (stragu) from comment #7) > Marco, do you know what was the latest version you could use without a crash? And does it still crash with LibreOffice 7.4.5. Quite a number of macOS bugs got fixed
Dear Marco Zehe, 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 Marco Zehe, 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
(In reply to Marco Zehe from comment #6) > Hi Christian, I'd be happy to try and reproduce with a TestFlight build. Hi Marco. Any luck with that? Or any crash in a recent version of LO? (7.5.5 or 7.6.1) As you can see, the report was closed for "Insufficient data" but if you have more information, please do share it and set back to "unconfirmed" if you can still reproduce the issue. Thank you!