|
El Capitan and Sierra Upgrade Issues
From NeoWiki
(Difference between revisions)
Revision as of 18:45, 7 September 2015 (edit) ( | contribs) (→Send us a bug report - Simplify instructions) ← Previous diff |
Revision as of 18:47, 7 September 2015 (edit) (undo) ( | contribs) (→Send us a bug report - Use general Apple support URL instead of English URL) Next diff → |
||
Line 43: | Line 43: | ||
==Send us a bug report== | ==Send us a bug report== | ||
- | If you are running OS X El Capitan and you find a bug, send us an [mailto:elcapitanbugs@neooffice.org e-mail]. Please include any instructions, sample documents, or [https://support.apple.com | + | If you are running OS X El Capitan and you find a bug, send us an [mailto:elcapitanbugs@neooffice.org e-mail]. Please include any instructions, sample documents, or [https://support.apple.com/HT201361 screen snapshots] that might help us reproduce the bug on our machines. |
Revision as of 18:47, 7 September 2015
This article describes known issues for running NeoOffice on Mac OS X 10.11 El Capitan. Follow us on Twitter @NeoOffice to get notified when we fix any El Capitan issues.
Problems after upgrading to El Capitan?
Step 1 - Download and install the latest version of NeoOffice
- NeoOffice Mac App Store users:
- Upgrade to NeoOffice 2017.33 from the Mac App Store
- If NeoOffice does not launch or NeoOffice Free Edition launches, we recommend that you try the following steps. These steps will force Apple's App Store application to redownload NeoOffice:
- Quit NeoOffice if it is running
- Move NeoOffice to the Trash and empty the Trash
- Reboot your machine (note: this step is very important because if you do not reboot, the steps below may not work)
- Launch Apple's App Store application, select the Store :: Sign In menu, and login using your Apple iTunes account
- In the App Store application, click on the "Purchases" icon and press the "Install" button to the right of NeoOffice
- Wait for NeoOffice to finish downloading before you try to launch NeoOffice
- NeoOffice Classic Edition users:
- Install NeoOffice 3.4.1 if you are running an older version of NeoOffice
- Install the latest NeoOffice 3.4.1 patch
- Install Java from Apple. Note: Java from Oracle will not work, only Java 6 from Apple will work.
Step 2 - If NeoOffice does not launch, displays an error when saving documents, or has any new bugs immediately after doing the above steps, we recommend deleting NeoOffice's preferences files using the following steps
These steps will force NeoOffice to create new preference files with default values:
- Quit NeoOffice
- NeoOffice Mac App Store users:
- Launch the /Applications/Utilities/Terminal application, copy the following commands into the Terminal window, and press the Return key:
open ~/Library/Containers/org.neooffice.NeoOfficeSecureEdition/Data/Library/Preferences/NeoOfficeSecureEdition
defaults delete org.neooffice.NeoOfficeSecureEdition - A new Finder window should open. Rename the selected NeoOfficeSecureEdition folder by pressing the Return key, editing the folder name, and pressing the Return key again.
- Launch the /Applications/Utilities/Terminal application, copy the following commands into the Terminal window, and press the Return key:
- NeoOffice Classic Edition users:
- Launch the /Applications/Utilities/Terminal application, copy the following commands into the Terminal window, and press the Return key:
open ~/Library/Preferences/NeoOffice-3.0
defaults delete org.neooffice.NeoOffice - A new Finder window should open. Rename the selected NeoOffice-3.0 folder by pressing the Return key, editing the folder name, and pressing the Return key again.
- Launch the /Applications/Utilities/Terminal application, copy the following commands into the Terminal window, and press the Return key:
- Launch NeoOffice
Fixed bugs
- NeoOffice would hang when opening a new window while in full screen mode.
- Typing text in a full screen mode window would fail.
Unfixed bugs
Send us a bug report
If you are running OS X El Capitan and you find a bug, send us an e-mail. Please include any instructions, sample documents, or screen snapshots that might help us reproduce the bug on our machines.