Illustrative scenario: Jordan is editing a spreadsheet in LibreOffice on a Mac running macOS Sonoma. The file is stored on a company SMB share, and LibreOffice quits when Jordan saves. This example is hypothetical. It shows how to protect the document first, then determine whether the crash follows the file, LibreOffice, macOS permissions, or the network share.
A crash that happens while saving to a network drive does not, by itself, prove that Sonoma or LibreOffice has a known, universal defect. I could not verify an official notice identifying one general Sonoma-only crash for this exact situation. LibreOffice’s current system requirements list macOS 11 or newer, which includes Sonoma, but individual builds, file formats, share servers, and permissions can still behave differently. The steps below are diagnostic; the right fix depends on which test reproduces the crash.
If the document is still open, do not repeatedly press Save or overwrite the only copy. Use File > Save As to save a working copy to a local folder such as Documents, with a new name. If LibreOffice crashes before you can do that, reopen the app and check for its document recovery prompt. Recovery is not guaranteed, so preserve the original network file and any recovered copy separately.
For Jordan’s spreadsheet, a safe first copy might be Budget-working-copy.ods in the Mac’s Documents folder. Once saved, close and reopen that local copy to confirm it is readable. This protects the current work while Jordan tests the share. Do not start by deleting LibreOffice preferences, clearing folders on the server, or granting the app broad disk access.
Write down the macOS version from Apple menu > About This Mac and the LibreOffice version from LibreOffice > About LibreOffice. Note whether the Mac uses Apple silicon or Intel, which LibreOffice build is installed, the document format (such as ODS or XLSX), and what type of share is involved. SMB is commonly used with Windows servers and many NAS devices; NFS and WebDAV are other possible network file protocols.
Also record when the crash occurs: while opening the Save dialog, after choosing a folder, immediately after clicking Save, or while replacing an existing file. Those details help distinguish a file-picker or app issue from a connection, access, or server-side problem. Jordan notes that the same document saves locally and that the crash happens only when writing to the SMB share.
In Finder, open the mounted network volume and copy a small test file into the same destination folder. Rename that test file, then move it to the Trash if permitted. These simple checks test whether Jordan’s account can create, rename, and remove files in the target folder. They do not fully test LibreOffice, but they can reveal a disconnected mount, expired credentials, read-only access, or a folder permission problem.
If Finder cannot create or rename a file, fix the share or account permissions with the server or NAS administrator before changing LibreOffice settings. A share may allow reading but not writing, or permit writing in one folder but not another. Reconnect through Finder using the server’s documented address, such as smb://server-name/share-name, and sign in with the intended account. Do not change server-wide SMB settings or permission inheritance without understanding their impact on other users.
Create a new, small Writer document or Calc spreadsheet and save it to the Mac locally. Then save a second copy to a new filename in the network folder. Avoid testing by replacing the only copy of a work document. If local saves work but a new file on the share crashes, the network path, share permissions, server behavior, or the way LibreOffice interacts with that volume deserves attention.
If the test file saves successfully to the share, try a copy of the original document. A crash limited to one document can indicate file-specific damage, complex embedded content, or a format-specific issue. Keep a local backup and test a copy in LibreOffice’s native OpenDocument format and, if needed, in the original format. Do not repeatedly convert and replace the original; conversion can alter formatting or features.
Check for a current LibreOffice release compatible with your Mac and install it from the official LibreOffice download page. The macOS download must match the Mac’s processor type; LibreOffice’s installation instructions distinguish Intel and Apple silicon installers. Also install applicable macOS Sonoma updates after saving work and following your organization’s update policy. A newer release may contain general fixes, but updating is not proof that the network drive caused the crash.
macOS can ask whether an app may access a network volume. If you dismissed or denied such a prompt, review the access controls in System Settings > Network and System Settings > Privacy & Security > Files & Folders. The exact controls visible depend on the app and macOS configuration. Allow only access that matches your intended use. Full Disk Access is broad and should not be the first troubleshooting step for a single network share.
LibreOffice Troubleshoot Mode starts with a temporary user profile and disables hardware acceleration. A user profile stores settings and extensions; using a temporary one can help reveal whether a damaged setting or extension is involved. From the macOS menu bar, choose Help > Restart in Troubleshoot Mode, then choose Continue in Troubleshoot Mode in the dialog. Create a harmless test document and try saving it to the share.
If saving works only in Troubleshoot Mode, return to normal mode and investigate extensions or profile settings before resetting anything. Disable user extensions one at a time and repeat the local-versus-network test. If the crash continues in Troubleshoot Mode but local saves remain reliable, a profile reset is less likely to address the share-specific cause. Troubleshoot Mode uses a temporary profile; changes made there do not carry over after LibreOffice restarts normally.
If LibreOffice continues to crash only when saving directly to the network drive, work from a local copy and transfer it with Finder after saving and closing the document. Then reopen the transferred file from the network location and verify that it contains the expected changes. This is a workaround, not a repair, and it is safest when one person edits the file at a time.
For a shared team document, tell collaborators which copy is authoritative while troubleshooting. Concurrent edits to a local copy and a server copy can create conflicting versions. Keep dated local backups, and do not delete lock or temporary files from the share unless the administrator confirms that no user has the document open.
After reproducing the crash with a small test file, open the macOS Console app and select Crash Reports in the sidebar. Apple says crash report files use the .ips extension. Save or copy the report details along with the LibreOffice version, Sonoma version, Mac processor type, file format, share protocol, and exact steps that trigger the failure. Remove document names, account names, server paths, or other private information before sharing logs publicly.
Use the official LibreOffice help and bug-reporting channels to check for an existing issue or report a reproducible crash. Include whether the issue happens with a fresh test file, whether local saving works, and whether Troubleshoot Mode changes the result. If Finder also fails to write to the share, involve the storage administrator or server vendor; an application bug report alone will not repair share permissions.
Jordan considers the issue isolated when a local test save works, Finder can create and rename a test file in the target folder, a new LibreOffice file can be saved there without a crash, and the reopened network copy contains the expected changes. If only Troubleshoot Mode succeeds, Jordan returns to normal mode and checks the profile or extensions. If direct network saves still crash, Jordan preserves the local-copy workflow and sends a privacy-reviewed crash report to the appropriate support channel.
Create an Outlook meeting invite, add required or optional attendees, choose a time, add Teams details, set recurrence, and check replies in new or classic Outlook.
Use Excel's Data Validation settings to set a maximum, minimum, exact length, or character range, then add clear prompts and error alerts.
Fix the Outlook “We can’t schedule the meeting” error by checking account support, refreshing Teams sign-in, and repairing the Classic Outlook add-in.
Change Office 365 menus, spelling and grammar settings, or keyboard input in desktop apps and Microsoft 365 for the web.
Learn how to auto-forward all or selected emails in Outlook 365 using Forwarding settings or Rules, plus how to stop forwarding and fix blocked external forwards.
Use Microsoft Editor in Word for Microsoft 365 to check spelling, grammar, clarity, and conciseness, review suggestions, and tune proofing settings.
Learn how to add an RSS feed to Outlook 365 in classic Outlook for Windows, find the correct feed URL, manage subscriptions, and fix common RSS issues.
Jump straight to any page in Word for Microsoft 365 with Ctrl+G or F5, relative page numbers, or the Navigation pane, with Windows and Mac shortcuts.
Learn how to add contacts to Outlook on the web, new Outlook, classic Outlook, and mobile, plus how contact syncing and CSV imports work.
Change a Word page color, add a picture background, remove either, and enable background printing on Windows or Mac with clear, current steps.
