Thank you for the detailed description.
Based on what you describe, I suspect that this is primarily a
LibreOffice user-profile or AutoCorrect data-saving problem, rather than
a problem with the Apple Silicon processor or macOS itself.
There is one especially important detail in your report:
- You can add an entry successfully.
- The entry appears in the AutoCorrect replacement list.
- It remains visible while LibreOffice is running.
- After restarting LibreOffice, it disappears.
- The modification date of `acor_el-GR.dat` does not change.
This suggests that LibreOffice is accepting the modification in memory
but is not successfully writing it to the persistent AutoCorrect data file.
Let's investigate this systematically, starting with the least
disruptive solutions.
1. First, check which AutoCorrect language is selected
This is an important check because LibreOffice maintains separate
AutoCorrect replacement lists for different languages.
For Greek, the relevant file is:
`acor_el-GR.dat`
However, having this file in the correct directory does not necessarily
mean that LibreOffice is currently using it.
Please try the following:
1. Open LibreOffice Writer.
2. Open a new document.
3. Go to Tools → AutoCorrect → AutoCorrect Options.
4. Select the Replace tab.
5. Look at the language selection at the top of the window.
6. Make sure it explicitly says Greek (Greece).
7. Add your test entry again:
- Replace: `zztest`
- With: `TEST`
8. Click New, followed by OK.
The language selector is important because AutoCorrect replacements are
language-dependent.
2. Verify that LibreOffice is using the directory you inspected
This is probably the most important diagnostic step.
LibreOffice allows the AutoCorrect directory to be configured
independently of the other profile directories.
On your Mac:
1. Open LibreOffice.
2. Go to LibreOffice → Preferences.
3. Find LibreOffice → Paths.
4. Locate the entry named AutoCorrect.
5. Check the directory displayed there.
It should point to:
`~/Library/Application Support/LibreOffice/4/user/autocorr`
If it points somewhere else, LibreOffice might be reading and writing a
different AutoCorrect file.
The official LibreOffice documentation confirms that the AutoCorrect
path is configurable.
help.libreoffice.org
If the path is different, this would be a very promising explanation for
your problem.
3. Check whether macOS permissions or file attributes are interfering
Even if Finder reports Read & Write permissions, it is worth checking
the actual filesystem permissions, including ACLs and file flags.
First, completely quit LibreOffice using Command + Q.
Then open Terminal and execute:
bash
bash
ls -leO ~/Library/Application\ Support/LibreOffice/4/user/autocorr
This displays the file permissions, ACL entries and filesystem flags.
Next, execute:
bash
bash
ls -leO ~/Library/Application\ Support/LibreOffice/4/user
Look for anything unusual, particularly:
- An unexpected owner.
- ACL entries that deny writing.
- Immutable flags such as `uchg`.
- A folder that does not allow your account to create or modify files.
You can also check the file's ownership:
bash
bash
stat -f "%Su:%Sg %Sp %N" ~/Library/Application\
Support/LibreOffice/4/user/autocorr/acor_el-GR.dat
Important: Do not change permissions recursively or use `chmod 777`. We
should first identify whether there is actually a permissions problem.
4. Test whether the LibreOffice user profile is corrupted
This is the solution I would particularly recommend investigating.
LibreOffice stores its configuration, extensions, dictionaries and
AutoCorrect information in its user profile.
A damaged profile can cause unexpected problems even when individual
files appear to have correct permissions.
I recommend testing with a completely new profile.
How to do this safely on macOS
1. Quit LibreOffice completely.
2. Open Finder.
3. Press Command + Shift + G.
4. Enter:
`~/Library/Application Support/LibreOffice/4/`
5. Locate the folder named `user`.
6. Rename it to:
`user_backup`
7. Start LibreOffice again.
LibreOffice should automatically create a new user profile.
Now perform the following test:
1. Open Writer.
2. Open AutoCorrect Options → Replace.
3. Select Greek (Greece).
4. Add `zztest` → `TEST`.
5. Click New and then OK.
6. Quit LibreOffice using Command + Q.
7. Wait a few seconds.
8. Restart LibreOffice.
9. Check whether the entry is still present.
If the entry survives, we have strong evidence that the original
LibreOffice user profile was responsible.
Important diagnostic testIf this test works, you do not need to
reinstall LibreOffice or change macOS permissions.
You can retain the new profile and selectively restore your personal
settings from `user_backup`.
Do not delete the backup until everything has been checked.
LibreOffice also provides a Troubleshoot Mode for investigating
profile-related problems. Its official documentation explains the
available profile restoration options.
5. Check whether the AutoCorrect file is actually a valid data file
There is another useful detail: LibreOffice's `.dat` AutoCorrect files
are ZIP archives containing XML data.
This means that a file can exist and have apparently correct permissions
but still have an internal problem.
You can check its integrity without modifying it.
After quitting LibreOffice, execute:
bash
bash
unzip -t ~/Library/Application\
Support/LibreOffice/4/user/autocorr/acor_el-GR.dat
If the file is valid, you should see a message indicating that no errors
were detected.
You can also inspect its contents:
bash
bash
unzip -l ~/Library/Application\
Support/LibreOffice/4/user/autocorr/acor_el-GR.dat
Do not manually modify the archive yet. First, let's establish whether
LibreOffice can save entries normally with a fresh profile.
6. Could this be a macOS 27 compatibility problem?
It is certainly worth considering, but I would not make it my first suspect.
Your configuration is:
- macOS 27
- Apple Silicon M5
- LibreOffice 26.8.2.2 (AARCH64)
The fact that LibreOffice runs normally and allows you to modify the
AutoCorrect list suggests that the problem is not necessarily related to
the processor architecture.
I would investigate the following possibilities in this order:
| Possible cause | My assessment |
| --- | --- |
| Corrupted LibreOffice user profile | Strong possibility |
| Incorrect AutoCorrect directory | Worth checking |
| File ownership or ACL restrictions | Possible |
| Damaged `acor_el-GR.dat` archive | Possible |
| macOS 27 compatibility issue | Not established |
| Apple Silicon incompatibility | Unlikely |
I have not established a confirmed LibreOffice 26.8.2.2 bug matching
your exact symptoms, so I would avoid attributing the problem to macOS
27 without further testing.
You can also consult the official [LibreOffice 26.8 release
information](<https://blog.documentfoundation.org/blog/2026/08/26/libreoffice-26-8/?utm_source=chatgpt.com>).
7\. What I would like you to test first
Rather than changing several things simultaneously, I suggest performing
these three tests in this order:
1. Verify the AutoCorrect directory in LibreOffice Preferences → Paths.
2. Verify that Greek (Greece) is selected in the AutoCorrect Replace tab.
3. Create a fresh LibreOffice user profile using the procedure in section 4.
The third test is particularly valuable because it can distinguish a
profile problem from a possible application-level problem.
8\. Three questions that would help me identify the exact cause
I would appreciate it if you could tell me the following:
1\. What happens when you use a completely new LibreOffice user profile?
Does the `zztest` entry survive after quitting and restarting LibreOffice?
2\. In LibreOffice → Preferences → Paths, what is the exact directory
displayed for AutoCorrect?
Is it the same directory you mentioned in your original message?
3\. Does the problem also occur with another language?
For example, if you select English (USA), add a test entry, quit
LibreOffice and restart it, does that entry also disappear?
This last test is particularly useful because it can help distinguish a
problem affecting all AutoCorrect files from one specific to the Greek
`acor_el-GR.dat` file.
My recommendation: I would start with the fresh user-profile test before
reinstalling LibreOffice or changing any macOS permissions.
If a fresh profile solves the problem, we will have identified the
likely cause without needing to reinstall the application.
If the problem persists even with a completely new profile, I would then
investigate a possible LibreOffice 26.8 regression and prepare a
reproducible bug report for the LibreOffice developers.
Or:
if `acor_el-GR.dat`’s modification time really stays unchanged,
LibreOffice likely isn’t committing the entry to that file. Read & Write
permissions on the file alone don’t rule out a profile problem, an
app-level issue, or a mismatch between the language of the entry and the
AutoCorrect data being edited.
Try these checks in order:
1. **Confirm the entry’s language.** In Writer, select the test text and
check **Tools → Language → For Selection** (or the status bar). Make
sure it is Greek, and that you are editing the Greek replacement list.
As a diagnostic, try adding the same `zztest → TEST` entry to the
replacement list for another language you use, then restart and check
whether that entry persists.
2. **Test with a fresh LibreOffice profile.** First quit LibreOffice
completely. In Writer, choose **Help → Restart in Safe Mode**, then use
the safe-mode option to create/reset a profile. Prefer creating a fresh
profile or renaming the existing profile rather than deleting it; back
up your custom dictionaries, templates, macros, and settings first.
Reopen Writer, add one test entry, quit, and reopen. If it persists in
the fresh profile, the original profile is the likely cause. cite3
3. **Check the profile path LibreOffice is actually using.** In **Help →
About LibreOffice**, look for the **User Profile** path. Confirm it
matches the `~/Library/Application Support/LibreOffice/4/user` location
you inspected. If it differs, check the `autocorr` folder under the
active profile instead.
4. **Check whether the folder is writable, not just the file.** Quit
LibreOffice and, in Finder, inspect permissions for the `autocorr`
folder and its parent folders; ensure your account has Read & Write
access. If you use Terminal, you can also test whether your account can
create and remove a harmless temporary file in that folder. Don’t change
permissions recursively across the whole LibreOffice profile.
5. **If a clean profile still fails, test another supported LibreOffice
build.** The version number and macOS version you list may be a
compatibility factor, but the evidence here doesn’t establish that as
the cause. A fresh-profile test is the quickest way to separate
profile/configuration trouble from a version-specific bug. If the issue
reproduces, report it to LibreOffice with the exact version, macOS
build, language, active profile path, and the fact that the file’s
modification time does not change.
I’d start with the active profile path and the fresh-profile test. Those
will help distinguish a profile issue from a permissions or application
bug without disturbing your current setup.
Hope this helps.
Paolo
Il 08/11/26 17:51, ΓΙΩΡΓΟΣ ΞΥΝΟΠΟΥΛΟΣ ha scritto:
Dear LibreOffice Support Team,
I am experiencing a problem with the AutoCorrect feature in LibreOffice Writer on my MacBook.
When I add new entries to the AutoCorrect replacement list (Tools → AutoCorrect → AutoCorrect
Options → Replace), the entries appear to be added successfully. However, after completely closing
LibreOffice and reopening the application, all the new entries have disappeared.
I have performed the following checks:
The Greek AutoCorrect data file, acor_el-GR.dat, exists in the following directory:
~/Library/Application Support/LibreOffice/4/user/autocorr
The file has Read & Write permissions for my macOS user account.
I have tested the issue by adding a new replacement entry (e.g. "zztest" → "TEST"). After
restarting LibreOffice, the entry is no longer present.
I also checked the file's modification date before and after adding a new entry. The modification
date did not change, indicating that LibreOffice does not appear to be writing the new entries to
the AutoCorrect data file.
An additional observation: After clicking "New" and then "OK", the new replacement entry appears
correctly in the AutoCorrect replacement list. It remains visible for as long as LibreOffice is running. However, once
I close and restart the application, the entry disappears completely.
Both the acor_el-GR.dat file and the autocorr folder have Read & Write permissions for my macOS
user account. Nevertheless, the file's modification date remains unchanged after adding new entries.
This suggests that the entries are accepted by the application interface but are not being
permanently saved to disk.I would appreciate your assistance in identifying the cause of this
problem and providing instructions on how to fix it.
In particular, I would like to know whether this could be related to a problem with the LibreOffice
user profile, file permissions, or a compatibility issue with macOS.
My system details are:
Operating system: macOS 27
Computer: MacBook with Apple Silicon (M5 processor)
LibreOffice version: Version: 26.8.2.2 (AARCH64)
Calc: threadedThank you in advance for your assistance.
Kind regards,
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.