Fr:Guide de dépannage

From NeoWiki

Revision as of 03:47, 11 October 2006 (edit) Stardust ( | contribs) (Traduction en cours) ← Previous diff		Revision as of 04:00, 11 October 2006 (edit) (undo) Stardust ( | contribs) (Siute de la traduction) Next diff →
Line 50:		Line 50:
	}</pre>		}</pre>
-	* Contrôlez l'intégrité de votre machine Java en 1.4.2	+	* Contrôlez l'intégrité de votre machine Java en version 1.4.2
	*# Créer un fichier texte nommé '''Test Java''', mettez-y le code suivant et sauvez le : <br>		*# Créer un fichier texte nommé '''Test Java''', mettez-y le code suivant et sauvez le : <br>
	*#:		*#:

---

Revision as of 04:00, 11 October 2006

There are several common sources of problems that cause crashes or sub-optimal performance in NeoOffice. This page collects some common problems and tips to help narrow down the cause of, or in some cases even fix, the problem.

Il y a un grand nombre de problèmes qui peuvent causer un plantage de NeoOffice ou une dégradation de ses performances. Cette page liste les problèmes connus et les astuces permettant d'empêcher le problème d'apparaître, de le contourner ou d'en minimiser les conséquences.

Contents 1 NeoOffice fails to start, or crashes during startup or right after starting 2 NeoOffice ne veut démarrer ou bien se plante pendant le démarrage ou juste après 3 NeoOffice crashes randomly 4 Problems with the menus or menu bar 5 Crashing in the font dropdown 6 Performance 7 A patch does not appear to fix a bug it claims to fix 8 Preferences don't seem to stick 9 Certain keyboard shortcuts do not work

NeoOffice fails to start, or crashes during startup or right after starting

NeoOffice ne veut démarrer ou bien se plante pendant le démarrage ou juste après

• Check if the relevant soffice.* files have executable permissions.
• Contrôlez que les fichiers correspondants à soffice.* ont des droits d'exécution.

• Check the Console.log (via /Applications/Utilities/Console.app) for messages about Java, soffice.bin, or NeoOffice
• Contrôlez dans Console.log (accessible par /Applications/Utilitaires/Console.app la présence de messages au sujet de Java, soffice.bin ou NeoOffice.

• Check for a current entry in ~/Library/Logs/CrashReport/soffice.bin.crash.log (the crash log for NeoOffice, and, unfortunately OpenOffice.org)
• Contrôlez s'il y a une entre current dans ~/Bibliothèque/logs/CrashReport/soffice.bin.crash.log (C'est la log en cas de crash de NeoOffice et malheureusement de 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.

  Ces fichiers de log contiennent souvent des informations très utiles, et même si pour vous, ça n'a pas de sens, pour un des développeurs ou une des personnes de l'équipe de support , ce peut être très utile pour diagnostiquer le problème.

• See this section of the Bugzilla Guide for more information about obtaining the crash log.

  Consultez cette section du Bugzilla Guide pour trouver des informations complémentaires sur les emplacements des logs de crash.

• Check to see if you are running the most up-to-date version of Java 1.4.2
  • Open the Terminal (/Applications/Utilities/Terminal.app) and type the following and then press return:
    

    java -version

    • Mac OS X 10.3.9:
      java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-233)
Java HotSpot(TM) Client VM (build 1.4.2-56, mixed mode)
    • Mac OS X 10.4.3:
      java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-232)
Java HotSpot(TM) Client VM (build 1.4.2-54, mixed mode)

• Contrôlez que votre machine Java est à la dernière mise à jour de la version 1.4.2
  • Ouvrez le terminal (/Applications/Utilitaires/Terminal.app), tapez ce qui suit et pressez la touche Retour Chariot :
    

    java -version

    • Mac OS X 10.3.9:
      java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-233)
Java HotSpot(TM) Client VM (build 1.4.2-56, mixed mode)
    • Mac OS X 10.4.3:
      java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-232)
Java HotSpot(TM) Client VM (build 1.4.2-54, mixed mode)

• Check for a corrupt Java 1.4.2 installation
  1. 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();

        }

}

• Contrôlez l'intégrité de votre machine Java en version 1.4.2
  1. Créer un fichier texte nommé Test Java, mettez-y le code suivant et sauvez le :
     

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. [1] (modified for Java 1.4.2)
• Java Shared Archive corrupted (would this be detected by the above?)

  Often caused by some 10.3.x update; Apple issued another update to fix it (but other causes, too; Terry had a potential solution for them)

• You have installed a Java extension in one of the following folders and it is messing up your JVM [2]:
  • ~/Library/Java/Extensions/
  • /Library/Java/Extensions/
  • /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/lib/ext/

  Remove the offending extension and try launching NeoOffice again (N.B.: NeoOffice tries to prevent extensions in the first two directories from loading, but the last one also contains key files for the JVM and its contents cannot be forced not to load).

• Corrupted user preference 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)
    • 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
• 24Uemail scripting addition
  • This scripting addition has been reported to cause Java problems; remove it from your user's ~/Library/ScriptingAdditions folder.

NeoOffice crashes randomly

• Haxies (programs that use Unsanity's APE)

  Not all random crashes are caused by haxies, but we have found a disproportionate correlation between the presence of haxies and strange NeoOffice crashes (this was particularly true of NeoOffice versions prior to 1.2 Alpha, which used Java 1.3.1). Many other Mac developers have experienced similar issues with their applications when haxies are present.

  Haxies work by injecting their code into running applications in order to customize the behvior 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 a crash.

  Because of the scope of the 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)
• Corrupted user preference 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)
    • 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

Problems with the menus or menu bar

• Haxies and haxie-like programs
  • MenuCracker

    While not an Unsanity APE haxie, this hack for enabling third parties to add items to the Mac OS X menu bar has caused problems, such as the disappearance of NeoOffice's menus from the menu bar, in the past.

Crashing in the font dropdown

• This is usually caused by a corrupt font that hangs or crashes Apple's text layout routines (e.g. Vivaldi)
  • Check for a corrupt font and disable this font via Font Book
    • Mac OS X 10.3.x: Use FontDoctorâ„¢ (demo mode)
    • Mac OS X 10.4.x: Use Font Book :
      • Select all your fonts in Font Book
      • In the file menu, select Validate Fonts
      • Select Warnings in the dropdown menu while Font Book operates
      • Then check the fonts you would like to delete and click "Delete selected fonts"

Performance

Common causes of slow or lackluster performance

• Background processes

  Constantly-running background processes can degrade the performance of NeoOffice

  • Seti@Home
  • Folding@Home
  • DNET client (http://www.distributed.net/)
  • others?
• Less than 512 MB of RAM

  While NeoOffice will run on a Mac with 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). Luckily, RAM is cheap; adding RAM is the most cost-efficient way to speed up your Mac. See this thread for some real-life stories.

• Large number of fonts installed (see this section of the Installation Issues article)
• 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.

  • Do not use the standard OpenOffice.org 2.0 .app package; use Start OpenOffice.org and the "stand-alone" OpenOffice.org 2.0 instead (may not fix it?)
  • After using OpenOffice.org 2.0, reboot before using NeoOffice to clear the extra fonts from ATS
• 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 access a large number of files at startup, including a number of .zip and .jar archives.

  • Disable virus scanning of the NeoOffice application and profile directory, or of archive files in the NeoOffice application and profile directory

A patch does not appear to fix a bug it claims to fix

• Mac OS X "caches" shared libraries and Java classes to improve performance; unfortuantely, it has a very nasty habit of not clearing the cache when updated libraries and classes are installed (like in NeoOffice patches). If a bug doesn't appear to be fixed after applying a patch that should fix the bug, try restarting your Mac, which will clear the old versions of libraries and classes from cache. If the bug is still present after rebooting, you can then reopen the bug in Bugzilla.
• You applied the patch while NeoOffice was running. Quit and restart NeoOffice.

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, so allowing NeoOffice to re-import your NeoOffice 1.x or NeoOffice/J 1.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.

Certain keyboard shortcuts do not work

• If you assign a keyboard shortcut in NeoOffice and then it doesn't work, it may be because you've chosen a key combo that Mac OS X is already using either as a general system shortcut, or in its Services.
  • Look in the System Preferences, Keyboard & Mouse preference pane, Keyboard Shortcuts tab to see if your choice is in use already as a general system shortcut (edit: this option may only be available in Mac OS X 10.4).
  • Then look in e.g. TextEdit's TextEdit->Services submenu to see if any Services are using your chosen key combo (e.g. cmd-shift-L is often assigned to Search with Google).
    • If you never use the Services keyboard shortcuts and want to free them up, you can install the very handy Service Manager (freeware) preference pane to disable individual Services (works in 10.2.x, 10.3.x, 10.4.x).
    • Users of 10.4.x can also use the ServiceScrubber application (freeware) to disable Services or reassign their keyboard shortcuts.
• If a key combo shows in one of the NeoOffice menus as a shortcut, but doesn't actually work, it may be because although it has been assigned as a Global NeoOffice shortcut, it is being overridden by a shortcut assigned to the particular module you're in (i.e. Writer, Calc etc.)
  This is the case with cmd-shift-F11, for example; the menubar shows this key combo as calling up the Tools-Options dialogue, but this doesn't work in Writer, as Writer has it assigned to something else arcane to do with templates. Once you delete that module-specific assignment, the shortcut works as displayed in the menubar.