50
Chapter 14: Troubleshooting Common Problems
1. This error usually means that the NeoOffice .dmg was not completely
downloaded. Some combinations of browsers and internet connections
frequently cause large downloads like NeoOffice to stop before the entire file
is downloaded but do not inform you that the download has failed.
2. In this case, you might try using the command-line curl tool to complete the
download (this tool is also useful if you are on a dial-up connection and may
need to stop and start the download to use the phone line). Instructions on
using curl to download NeoOffice can be found via the NeoWiki.
2. When running the NeoOffice installer, the "test" returns with "NeoOffice can not
be installed on this computer":
○
This can sometimes occur simply because your current version of NeoOffice
is open. Check whether that is the case, and quit NeoOffice if it is open. Try
again to install.
○
The BSD subsystem is installed by default on 10.3.x and 104.x as part of the
BaseSystem.pkg. If this problem occurs on 10.3.x machines, your BSD
subsystem may have been somehow removed or messed up. It is not
recommended that you reinstall BaseSystem.pkg alone, since this may leave
your system in an unusable state. Instead, reinstall Mac OS X from your retail
CD; select the "Upgrade" option to preserve all of your settings, documents,
etc. Then reinstall the latest Mac OS X updates and security updates to return
you system to an up-to-date state.
○
N.B.: Since this requires a fairly significant amount of work, and perhaps
time, you should probably check the trinity forums first, to see if someone can
determine if something else is the problem and find another solution.
3. Installation stalls when it gets to the "Select Destination" screen
○
Installation sometimes stalls or hangs when it gets to the "Select Destination"
screen (and no drives will appear to choose from). The Apple Installer is
known to hang when probing all of the volumes on your system, if any of
your volumes are unreadable.
○
Try opening each of the volumes on your desktop in the Finder and
unmounting any iPods. Once you can open all volumes, then try re-running
the installer. If opening any volumes causes the Finder to hang, you have
found the cause of the problem and you might need to reboot to force Mac OS
Xto unmount the offending volume.
4. Installation fails with a "generic" error message
○
For some users, installation will fail and the following error message will
appear:
■
There were errors installing the software
■
Please try installing again.
NeoOffice User Guide for 2.x
485
PDF Image Viewer| What is PDF software; Open standard for more secure, dependable electronic version among a suite of PDF-based standards to develop specifications for creating, viewing, and
decrypt pdf; pdf security remover
44
Chapter 14: Troubleshooting Common Problems
○
If you see this message, you need to open the System Preferences application
(/Applications/System Preferences), click on the International icon, select the
Languages tab, move English to the top of the list, log out, login again, and
then rerun the installer. After installation, you can (and should) revert to your
preferred language.
○
This behavior is required to work around a rare but serious bug in the Mac OS
XInstaller on some versions of Mac OS X; for more information, see the
NeoWiki.
Post-Installation Issues
NeoOffice fails to start, or crashes during startup
If NeoOffice fails to start, or crashes during startup or right after starting
1. Check the Console.log (via /Applications/Utilities/Console.app) for messages
about Java, soffice.bin, or NeoOffice
◦
If NeoOffice starts but “hangs” during startup (longer than a minute or so on
recent Macs), take a sample before force-quitting NeoOffice. One of the
developers or community support team might be able to deduce the problem
based on the log information.
◦
If NeoOffice crashes, check for a current entry in
~/Library/Logs/CrashReport/soffice.bin.crash.log (the crash log for NeoOffice
and also, unfortunately, OpenOffice.org)
◦
These logs will often contain useful information, and even if they are
gibberish to you, one of the developers or community support team can often
deduce the problem based on log info.
2. Check to see if you are running the most up-to-date version of Java 1.4.2 (or Java
1.5 on Mac OS X 10.4)
3. Run the Mac OS X Software Update application (from the Apple menu) and
install any Mac OS X Updates, Security Updates, and Java Updates that are
offered. Youmay need to run Software Update multiple times in order to
completely update your system.
Check the Java Version
Open the Terminal(/Applications/Utilities/Terminal.app) and type the first line below,
and then press return. You should get a message like that below:
java -version
+Mac OS X 10.3.9:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-270)
NeoOffice User Guide for 2.x
486
43
Chapter 14: Troubleshooting Common Problems
Java HotSpot(TM) Client VM (build 1.4.2-70, mixed mode)
+Mac OS X 10.4.8:
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
Check for a corrupt Java 1.4.2 installation
Create a plain-text file called Test.java and put the following lines in it, saving
afterwards:
import java.awt.*;
public class Test{
public static void main(String[] args) {
Frame f = new Frame();
Panel p = new Panel();
f.add(p);
f.setSize(500, 500);
f.show();
}
}
*
1. Open the Terminal (/Applications/Utilities/Terminal.app) and "cd" to the folder
that you put the Test.java file in.
2. Compile the Test.java file using the following terminal command:
javac Test.java
3. Run the compiled program with Java 1.4.2 using the following terminal
command:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Commands
/java -classpath . Test
4. If a blank window appears when you run the program, then you know that Java
1.4.2 is working.
Haxies
Haxies work by injecting their code into running applications in order to customize the
behavior of Mac OS X or an application in a way that neither Apple nor the application
developer intended. A haxie may have a bug that causes an application to crash, or it may
simply create a condition that the application is not prepared to handle and thereby cause
acrash.
Because of the scope of the NeoOffice project and the limited time and resources of the
NeoOffice developers, no effort will be made to fix a bug that only occurs when a haxie
is present.
●
Disable any installed haxie(s), or add NeoOffice to the exclusions list for the haxie(s)
NeoOffice User Guide for 2.x
487
42
Chapter 14: Troubleshooting Common Problems
Corrupted userpreference files
(Force-)Quit NeoOffice, move your NeoOffice preferences folder aside, and restart (don't
let NeoOffice 2.x (re-)import your NeoOffice 1.x preferences). Here is where the
preference folder for respective versions of NeoOffice is located:
+NeoOffice 2.x: ~/Library/Preferences/NeoOffice-2.x
+NeoOffice 1.2.x: ~/Library/Preferences/NeoOffice-1.x
+NeoOffice/J 1.1: ~/Library/NeoOfficeJ-1.1 Error Message contains “Get Storage:
"No Content"”
Performance
Common causes of slow or lackluster performance
1. Background processes
Constantly-running background processes can degrade the performance of NeoOffice
◦ Folding@Home
◦ Seti@Home
◦ DNET client (http://www.distributed.net/)
○ Dashboard/widgets - disable all inessential widgets for best performance
○ Others?
2. Turn off Auto Spellchecking, because the wavy lines are a problem to draw. This is
due to the fact that OOo code sets individual pixels but Cocoa and Java, used in
NeoOffice, don't have any functions for setting individual pixels; so NeoOffice must
do a much more expensive operation of drawing a 1x1 pixel filled rectangle
3. Less than 512 MB of RAM: NeoOffice is a big suite of programs, and generally
requires at least 512 MB of RAM to run comfortably. While NeoOffice will run on a
Mac with less than 512 MB of RAM, it will run (and launch) more slowly, particularly
if you have other applications also running (Mac OS X really runs best with 512 MB
or more of RAM).
4. Large number of fonts installed. Font Book allows the OS X user to manage fonts
very quickly and effectively. Take a minute to disable fonts that are rarely used.
5. OpenOffice.org 2.0: OpenOffice.org 2.0 by default creates converted copies of all
of your installed Mac fonts. Because these fonts are stored inside an application bundle
in OpenOffice.org 2.0 (as opposed to simply being in a normal folder in
OpenOffice.org 1.1.2), all of the duplicate fonts are loaded by the Apple Type Server
(ATS)process and made available to Mac OS X apps. These duplicate fonts seriously
degrade the performance of NeoOffice, may cause fonts to display incorrectly, and
may even cause crashes. To remedy this,
○ Do not use the standard OpenOffice.org 2.0 .app package; use Start
OpenOffice.org and the "stand-alone" OpenOffice.org 2.0 instead
○ After using OpenOffice.org 2.0, reboot before using NeoOffice to clear the
extra fonts from ATS.
NeoOffice User Guide for 2.x
488
38
Chapter 14: Troubleshooting Common Problems
6. Virus-scanning applications:
○ Some virus scanners scan all files when the files are opened
○ Some virus scanners scan archive files (.sit, .tar, .gz, and .zip and its cousins,
like .jar) when those files are accessed
○ NeoOffice opens and accesses a large number of files at startup, including a
number of .zip and .jar archives, so they may all be scanned in turn by the virus
scanner.
○ To remedy, disable virus scanning of the NeoOffice application and preferences
directory (~/Library/Preferences/NeoOffice-2.x), or of archive files in the
NeoOffice application and preferences directory.
Hints and Tips
Preferences don't seem to stick
When preferences or settings changes don't seem to apply or don't stick between restarts
of NeoOffice, the most likely cause is a some sort of corruption of your
profile/preferences. Allowing NeoOffice to create a fresh set should fix the problem.
1. Move or rename your ~/Library/Preferences/NeoOffice-2.x folder
(~/Library/Preferences/NeoOffice-1.x folder for NeoOffice 1.x; in this case, also rename
or move aside your ~/Library/NeoOfficeJ-1.1 folder, if you had ever installed
NeoOffice/J 1.1)
2. Launch NeoOffice; it will then create a fresh user profile and settings (for NeoOffice
2.0, be sure not to let the "wizard" import preferences from older versions when starting)
In some cases the corruption may only be present in the NeoOffice 2.x or 1.x profile. In
this case, allowing NeoOffice to re-import your NeoOffice 1.x or NeoOffice/J1.1 profile
could restore some of your settings without reintroducing the corruption. In that case,
simply move or rename only the ~/Library/Preferences/NeoOffice-2.x
(~/Library/Preferences/NeoOffice-1.x for NeoOffice 1.x) folder before launching
NeoOffice.
How to get the page count to ignore a title page
-(How do I “offset” the page count?)
If you have a title page or cover page in the document, Writer's "page count" field still
counts those pages, and so your overall page count will be too high.
1. Place the cursor directly in front of the page number (in the header or footer) on
any page. If the pages are yet to be numbered, follow the instructions for
numbering, then start this process again.
2. Double-click to bring up the Edit Fields dialog
NeoOffice User Guide for 2.x
489
14
Chapter 14: Troubleshooting Common Problems
3. Enter -1 in the Offset box at the bottom [or -x, where x is the number of pages to
be kept un-numbered at the start]
4. Press OK.
Note: If there are pages added later at the beginning of the dcoument, this process may need to be repeated.
NeoOffice refuses to print Landscape
There is a tendency for OS X users to expect that all they need to do to change from
printing portrait to printing landscape (and back) is to change settings via File > Page
Setup. Unfortunately, this is not sufficient in NeoOffice. The key is to go to Format >
Page. Select the Page tab, and you will see the selections of Portrait and Landscape
there. Select as relevant and close the menu. This is counter-intuitive for Mac users, but
it works.
NeoOffice User Guide for 2.x
490
Documents you may be interested
Documents you may be interested
