Bug 141142 - Fatal error since macOS Big Sur
Summary: Fatal error since macOS Big Sur
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-21 08:39 UTC by stephark
Modified: 2021-10-21 03:37 UTC (History)
0 users

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 stephark 2021-03-21 08:39:05 UTC
Description:
I downloaded Big Sur on my iMac yesterday for the first time. Immediately "fatal error" message on Libre Office. I downloaded LO again (v.7,0,5), but it won't open at all.
Big Sur version: 11,2,3

Thanks

Actual Results:
won't open at all

Expected Results:
no access to my recorded LO files (calc or write)


Reproducible: Always


User Profile Reset: No



Additional Info:
open
Comment 1 steve 2021-03-23 10:03:51 UTC
Hi stephark, does the problem persists with 7.1.1 https://www.libreoffice.org/download/download/?

If it does, please attach the crash log as txt file to this discussion.
Comment 2 QA Administrators 2021-09-20 03:43:58 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-10-21 03:36:59 UTC
Dear stephark,

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