Description: LibreOffice is notarised on Catalina, but the .app bundle gets corrupted after first launch breaking and removing the notarisation Steps to Reproduce: 1. Open LibreOffice 2. Open a Writer window 3. Quite LibreOffice 4. codesign --test-requirement="=notarized" --verify --verbose LibreOffice.app/ Actual Results: codesign --test-requirement="=notarized" --verify --verbose LibreOffice.app/ LibreOffice.app/: a sealed resource is missing or invalid file added: /Applications/LibreOffice.app/Contents/Resources/__pycache__/unohelper.cpython-37.pyc file added: /Applications/LibreOffice.app/Contents/Resources/__pycache__/uno.cpython-37.pyc file added: /Applications/LibreOffice.app/Contents/Resources/__pycache__/pythonloader.cpython-37.pyc file added: /Applications/LibreOffice.app/Contents/Resources/extensions/dict-en/pythonpath/__pycache__/lightproof_impl_en.cpython-37.pyc file added: /Applications/LibreOffice.app/Contents/Resources/extensions/dict-en/pythonpath/__pycache__/lightproof_opts_en.cpython-37.pyc file added: /Applications/LibreOffice.app/Contents/Resources/extensions/dict-en/pythonpath/__pycache__/lightproof_en.cpython-37.pyc file added: /Applications/LibreOffice.app/Contents/Resources/extensions/dict-en/pythonpath/__pycache__/lightproof_handler_en.cpython-37.pyc Expected Results: Output similar to e.g., Firefox.app codesign --test-requirement="=notarized" --verify --verbose Firefox.app/ Firefox.app/: valid on disk Firefox.app/: satisfies its Designated Requirement Firefox.app/: explicit requirement satisfied Reproducible: Always User Profile Reset: No Additional Info: macOS 10.15.5 (19F101)
I reproduce this issue, and it's happen in macOS 10.15.5. anyway, I also try to check Blender, but it's have similiar issue.
Based on comment 1
Dear eisa01, 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