/jEdit/tags/jedit-4-2-pre14/doc/FAQ/faq-problems.xml
XML | 495 lines | 459 code | 28 blank | 8 comment | 0 complexity | be5e06c2dfce8eb647a53a2f8598fc15 MD5 | raw file
Possible License(s): BSD-3-Clause, AGPL-1.0, Apache-2.0, LGPL-2.0, LGPL-3.0, GPL-2.0, CC-BY-SA-3.0, LGPL-2.1, GPL-3.0, MPL-2.0-no-copyleft-exception, IPL-1.0
1<!-- jEdit buffer-local properties: -->
2<!-- :indentSize=4:noTabs=false:maxLineLen=72:tabSize=4: -->
3<!-- :xml.root=faq.xml: -->
4
5<!-- jEdit FAQ -->
6<!-- Copyright (C) 2003 John Gellene, Kris Kopicki -->
7
8<sect1 id="problems"><title>Problems</title>
9<para>
10 This section deals with problems you may experience while using or
11 installing jEdit. Problems that aren't OS specific are listed under
12 <link linkend="general-problems"><quote>General Problems</quote></link>.
13</para>
14<qandaset defaultlabel="qanda">
15
16<qandadiv id="general-problems">
17 <title>General Problems</title>
18
19 <qandaentry>
20 <question id="wont-start"><para>
21 jEdit won't start. What should I do?
22 </para></question>
23 <answer><para>
24 If you don't have a clue as to why you cannot run jEdit, it's
25 best to perform a step-by-step diagnosis. Begin by finding the
26 Java application loader you are using: <filename>java.exe</filename>,
27 <filename>javaw.exe</filename> or <filename>java</filename>. Make sure
28 it is running by entering its full path with the <userinput>-h</userinput>
29 parameter in a terminal or console window. If you can't find
30 the Java application loader, your Java runtime environment package
31 may be missing or incomplete.
32 </para>
33 <para>
34 Next, find where you have installed jEdit. You should look
35 for the file <filename>jedit.jar</filename> which contains all
36 of the application's Java class files in a compressed archive.
37 </para>
38 <para>
39 Once you have both files, run the Java loader with the
40 <userinput>-jar</userinput> option and with
41 <filename>jedit.jar</filename> as the target. Make sure that
42 you either specify full paths for both files or that the
43 directories for the files are part of your <filename>PATH</filename>
44 environment variable. If jEdit does not load at this point, the likely
45 problem is a corrupt <filename>jedit.jar</filename> file. Try
46 downloading the application again.
47 </para>
48 <para>
49 If jEdit does load using this procedure, you need to examine
50 the <quote>shortcut</quote> loading mechanism you wish to use.
51 </para>
52 <para>
53 On Linux and MacOS X, you need to find and examine the <filename>jedit</filename>
54 shell script provided by the installation routine to confirm that the
55 script's commands target the correct files and locations, and that
56 variables like <filename>JAVA_HOME</filename> are either defined in the
57 script or elsewhere in your shell's environment. Don't forget to make
58 sure that the script's file permissions allow you to execute it as a shell script.
59 </para>
60 <para>
61 On Windows, if you are using a batch script to run jEdit, the
62 same points (other than file permissions) apply to examining
63 <filename>jedit.bat</filename>. If you are using
64 jEditLauncher, run <userinput>jedit /p</userinput> in jEdit's
65 installation directory from a command line to get the custom
66 loader's setup dialog. Here you can check the paths for both
67 the Java application loader and jEdit as well as any command
68 line parameters for both programs. Make sure that you have
69 placed Java and jEdit options in the correct input fields.
70 If the parameters seems correct
71 but jEdit will not load with the Windows launcher, try
72 uninstalling and reinstalling the launcher by running
73 <userinput>jedit /u</userinput> followed by
74 <userinput>jedit /i</userinput>.
75 </para>
76 <para>
77 If at this point you're still stuck, ask for help on the
78 jedit-users mailing list, the jEdit Community
79 <quote>Installation</quote> message board or on IRC.
80 You're bound to find someone quickly.
81 </para>
82 </answer>
83 </qandaentry>
84
85 <qandaentry>
86 <question id="start-missing-plugins"><para>
87 After jEdit starts, I can't see all of the plugins I have downloaded.
88 How can I make them appear?
89 </para></question>
90 <answer><para>
91 If you use jEdit's Plugin Manager to download and install plugins, your
92 plugins will be found in the <filename>jars</filename> subdirectory of
93 one of two directories: either the directory in which jEdit is
94 installed, or the current user's settings directory. These are the only
95 location jEdit examines when it loads plugins at startup.
96 </para>
97 <para>
98 The default location of the settings directory depends on your operating
99 system. You can find out its location during a jEdit session by
100 evaluating <userinput>jedit.getSettingsDirectory()</userinput> in BeanShell.
101 </para>
102 <para>
103 The settings directory can be changed by using the
104 <userinput>-settings</userinput> command line parameter. If you change the
105 location of the settings directory with this parameter, jEdit will not
106 be able to find plugin archive files in the old location.
107 If you use or change the <userinput>-settings</userinput>
108 parameter, make sure your plugins don't get left behind.
109 </para>
110 </answer>
111 </qandaentry>
112
113 <qandaentry>
114 <question id="problems-out-of-memory"><para>
115 During an editing session I get an error message about an
116 <quote>OutOfMemoryError</quote> while working with a large file or
117 performing a lengthy operation. The message reappears every time
118 I retry the operation. How can I prevent this?
119 </para></question>
120 <answer><para>
121 One solution that often works is to set or increase the allocation of
122 memory to the heap for Java objects created by the Java Virtual Machine
123 in which jEdit is running. Add the command line option
124 <userinput>-mxXXm</userinput> to the options passed to the version of
125 the Java application loader you are using (such as
126 <filename>java</filename>, <filename>java.exe</filename> or
127 <filename>javaw.exe</filename>). In place of the
128 <userinput>XX</userinput> in the option, use a multiple of 16
129 between 32 and 128. If you already are using the option, increase the
130 numeric portion of the <userinput>-mxXXm</userinput> parameter in
131 increments of 16. Many users have good results using 48 or 64, but you
132 should try different values for the best result on your installation.
133 </para>
134 <para>
135 If you are using the <userinput>-jar</userinput> command line option
136 with Java to run jEdit, remember that the <userinput>-jar</userinput>
137 parameter must be the last Java option, followed immediately by the path
138 to <filename>jedit.jar</filename> and then any jEdit command line options.
139 </para>
140 <para>
141 If out of memory errors occur while running a build or compilation
142 operation from within jEdit, you can also have the operation run in an
143 external process rather than inside the same Java Virtual Machine
144 running jEdit. The AntFarm plugin, for example, lets you select this
145 approach as a configuration option. In other cases, you can run an
146 external program using the command line interface of the Console plugin,
147 which will capture and display the output of the external process and in
148 many cases parse the output for error information.
149 </para></answer>
150 </qandaentry>
151
152 <qandaentry>
153 <question id="install-no-such-file"><para>
154 What should I do when the installer displays the message,
155 <screen>No such file or directory</screen>?
156 </para></question>
157 <answer><para>
158 The full message that you may receive from the Java application launcher
159 begins as follows:
160 <screen>Exception in thread "main" java.util.zip.ZipException: No such file or directory
161...</screen>
162 This means that the Java application launcher cannot read the
163 jar archive file that you specified on the command line. If your Java
164 runtime environment otherwise runs properly, then either you have named
165 the incorrect file name or the installation file is corrupt or
166 incomplete. Check the file name, download the installer again if
167 necessary, and be sure to follow any specific instructions for your
168 operating system posted on the <ulink
169 url="http://www.jedit.org">jEdit web site</ulink>.
170 </para></answer>
171 </qandaentry>
172
173 <qandaentry>
174 <question id="install-noclassdef">
175 <para>
176 After downloading <filename>jeditXXXinstall.jar</filename> (the
177 <filename>XXX</filename> represents the version number), I tried to run
178 <userinput>java jeditXXXinstall.jar</userinput>, but got the error message,
179 <screen>Exception in main(), NoClassDefFoundError: jeditXXXinstall/jar.</screen> What am I doing wrong?
180 </para>
181 </question>
182 <answer>
183
184 <para>
185 You need to specify the <userinput>-jar</userinput> option for the Java
186 application loader so that the loader will search the installation archive
187 for the starting class file. Without the option, it treats the archive as a
188 single class file (which it is not!), thus producing the error. The correct
189 command line would be <userinput>java -jar jeditXXXinstall.jar</userinput>.
190 </para>
191 </answer>
192 </qandaentry>
193
194 <qandaentry>
195 <question id="jedit-crashed">
196 <para>
197 jEdit crashed the JVM, what gives?
198 </para>
199 </question>
200 <answer>
201 <para>
202 It's important to realise that java applications should never do this.
203 The problem is almost certainly a bug in the JVM. Problems of this
204 nature are often tricky to solve. Depending on your platform, there
205 should be information logged about what caused the crash to occur. For
206 Unix type systems you will likely get an error in the console (and for
207 Mac OS X you may also get a report in ~/Library/Logs/CrashReporter/JavaApplicationStub.crash.log).
208 Some recent problems with Java 1.4.x and Windows were the result of a
209 bug in the JVM and certain graphics card drivers.
210 </para>
211 </answer>
212 </qandaentry>
213
214 <qandaentry>
215 <question id="general-slowstart">
216 <para>
217 Why is jEdit so slow to start up?
218 </para>
219 </question>
220 <answer>
221 <para>
222 The most likely cause is one or more plugins that are installed. jEdit 4.1
223 displays loading times for plugins in the activity log.
224 </para>
225 <procedure>
226 <step>
227 <para>
228 To go the <guimenu>Utilities</guimenu> menu and select <guimenuitem>Activity Log</guimenuitem>.
229 </para>
230 </step>
231 <step>
232 <para>
233 Scroll to the area where you see lines like <quote>[notice] JARClassLoader: Starting plugin XXX</quote>.
234 </para>
235 </step>
236 </procedure>
237 <para>
238 You should be able to see which (if any) plugins are causing an excesively long delay.
239 </para>
240 </answer>
241 </qandaentry>
242
243 <qandaentry>
244 <question id="general-slow">
245 <para>
246 Why is jEdit so slow?
247 </para>
248 </question>
249 <answer>
250 <para>
251 There may be many causes for this. Java by nature is more demanding on hardware than native
252 applications. Modern computers should not have much problem with this.
253 </para>
254 <para>
255 The most likely cause is plugins that parse buffers or do other computationally expensive
256 operations. These include XML, SpeedJava and CodeAid. If performance is important to you, installing
257 a whole batch of plugins in one go is probably not a very good idea. Install them one at a time,
258 so you can evaluate the effects of each.
259
260 <note>
261 <para>
262 If you are experiencing slow downs when switching and saving buffers (up to 20 second delays) and you
263 have the TaskList plugin installed, check that the version is greater than 0.4. Versions after 0.4 fix
264 the problem.
265 </para>
266 </note>
267 </para>
268 </answer>
269 </qandaentry>
270
271 <qandaentry>
272 <question id="general-docking">
273 <para>
274 Go to left/top/bottom/right docking area does not work for some plugins?
275 </para>
276 </question>
277 <answer>
278 <para>
279 The plugin is missing a <methodname>requestDefaultFocus()</methodname> method.
280 Plugin updates will be available from time to time, or you can email the author
281 of the plugin to let them know of the problem.
282 </para>
283 </answer>
284 </qandaentry>
285
286</qandadiv>
287
288<!--********************************************************* Mac OS -->
289
290<qandadiv id="macos-problems">
291 <title>Mac OS Problems</title>
292 <qandaentry>
293 <question id="blurry-tabs">
294 <para>
295 Why are the tabs for docked windows blurry under OS X 10.2?
296 </para>
297 </question>
298 <answer>
299 <para>
300 In Mac OS X 10.2 Apple enabled Hardware Acceleration for Java by default.
301 Unfortunately it had some bugs. This is the result of one of these bugs.
302 The only way to avoid this problem is to disable hardware acceleration for
303 jEdit or your whole system.
304 To disable it in jEdit you will need to edit
305 the following file:
306 jEdit/jEdit.app/Contents/Resources/MRJApp.properties
307
308 You will need to add the line <userinput>com.apple.hwaccel=false</userinput>.
309 This is done for you in the Mac OS X package of jEdit 4.1.
310 </para>
311 </answer>
312 </qandaentry>
313 <qandaentry>
314 <question id="not-in-menubar">
315 <para>
316 Why are the menus not in the menubar?
317 </para>
318 </question>
319 <answer>
320 <para>
321 You can enable the use of OS X's menubar in the Mac OS Plugin settings.
322 You should note that the reason this is off by default is because of numerous
323 problems with using the Mac OS X menubar. For example dynamic menus, shortcuts
324 and check box menu items do not work correctly or at all. All bar the shortcut
325 issue is resolved in Java 1.4.1 (currently in beta).
326 </para>
327 </answer>
328 </qandaentry>
329 <qandaentry>
330 <question id="freeze-hide">
331 <para>
332 Why does jEdit freeze when I hide the application while it is starting up?
333 </para>
334 </question>
335 <answer>
336 <para>
337 This appears to be a bug in Java 1.3.1. Once the splash screen has gone
338 it should be safe to hide the application.
339 </para>
340 </answer>
341 </qandaentry>
342 <qandaentry>
343 <question id="freeze-general">
344 <para>
345 Why does jEdit freeze my whole system?
346 </para>
347 </question>
348 <answer>
349 <para>
350 Under some hardware configurations this can happen. It is only known to happen
351 with Rage 128 Pro graphics cards. There appears to be a bug relating to the graphics
352 card drivers that cause any carbon applications using the card to freeze. Since java
353 1.3.1 is carbon based, it suffers from this problem. Follow the instructions
354 <link linkend="blurry-tabs">here</link> to disable hardware acceleration. Java 1.4.x
355 does not suffer from this problem (in beta at this time).
356 </para>
357 </answer>
358 </qandaentry>
359</qandadiv>
360
361<!--***************************************************** Unix/Linux -->
362
363<qandadiv id="unix-problems">
364 <title>Unix/Linux Problems</title>
365 <qandaentry>
366 <question id="install-jedit-home">
367 <para>
368 After installing jEdit on Linux, running the <userinput>jedit</userinput>
369 command causes the error message:
370 <screen>Warning: JAVA_HOME environment variable not set</screen>
371 How can I fix this?
372 </para>
373 </question>
374 <answer>
375 <para>
376 Your <filename>jedit</filename> shell script should
377 be modified to set the <userinput>JAVA_HOME</userinput> variable
378 to the directory containing the executables of
379 your desired Java runtime environment (JRE).
380 </para>
381 </answer>
382 </qandaentry>
383
384 <qandaentry>
385 <question id="install-mandrake-kaffe">
386 <para>
387 How can I get jEdit to run on Mandrake Linux 8.1? When I try to start the
388 program, I keep getting an error which begins as follows:
389 <screen>java/lang/NoClassDefFoundError: Ljavax/swing/text/Document; at
390 java.lang.reflect.Method.invoke(Method.java:native) at
391 kaffe.jar.ExecJarName.main</screen>
392 </para>
393 </question>
394 <answer>
395 <para>
396 This version of Mandrake Linux uses the Open Source Kaffe package as its default
397 Java virtual machine. Kaffe is compliant with version 1.1 (and to a limited extent,
398 version 1.2) of the Java platform. However, the latest version of jEdit, version 4.1, requires
399 at least version 1.3. You will need to install another Java package for Linux
400 (either Blackdown, IBM or Sun) that complies with at least version 1.3.
401 </para>
402 </answer>
403 </qandaentry>
404
405 <qandaentry>
406 <question id="install-linux-keyboard">
407 <para>
408 I installed jEdit 3.2.2 from the RPM on Mandrake 8.1 and I am unable to send any
409 keyboard inputs to jEdit. But the mouse interacts with the program just fine. I
410 have tried running it on Sun's JDK 1.3.1 and Blackdown's latest JDK (Dec. 2001)
411 without any luck.
412 </para>
413 </question>
414 <answer>
415 <para>
416 This problem has been reported with various combinations of window managers and
417 desktop environments. The IBM JDK has not been reported to have this problem. In
418 addition, there have not been reported problems with the Sun and Blackdown JDK's
419 when running under the Sawfish window manager.
420 </para>
421 </answer>
422 </qandaentry>
423</qandadiv>
424
425<!--******************************************************** Windows -->
426
427<qandadiv id="windows-problems">
428 <title>Windows Problems</title>
429 <qandaentry>
430 <question id="install-windows-errmessage">
431 <para>
432 When I try to run
433 <filename>jedit.exe</filename> I get the message
434 <screen>The JEditLauncher component does not appear to be installed.</screen>
435 </para>
436 </question>
437 <answer>
438 <para>
439 The dialog presenting this message asks if you would like to install the
440 launcher. Select <userinput>Yes</userinput> and supply further information
441 as prompted. A file named <filename>install.log</filename> is generated in the
442 same directory as <filename>jedit.exe</filename> that
443 contains information on the launcher's installation. You can send this file
444 along with jEdit's Activity Log if you continue to have problems running jEdit
445 with the launcher package.
446 </para>
447 </answer>
448 </qandaentry>
449
450 <qandaentry>
451 <question id="install-error-regkey">
452 <para>
453 When I try to run the jEdit installation package in Windows, I get an error
454 message, <screen>Error opening registration key
455 "software\javasoft\java runtime environment".</screen> How can I fix this?
456 </para>
457 </question>
458 <answer>
459 <para>
460 The problem is not with jEdit but may be caused by your installation of the Java
461 runtime environment. Under Windows, Sun's Java application loader relies on
462 entries in the Windows registry to find the files that create the runtime
463 environment and a Java virtual machine. The loader (<filename>java.exe</filename>e or
464 <filename>javaw.exe</filename>) is
465 unable to find the necessary registration entry and therefore sends the error
466 message. The best approach to fixing this is to uninstall and reinstall the JDK.
467 </para>
468 </answer>
469 </qandaentry>
470
471 <qandaentry>
472 <question id="install-windows-badcommand">
473 <para>
474 When trying to install jEdit on Windows Me with an MS-DOS prompt, after entering
475 <userinput>java -jar jeditXXXinstall.jar</userinput> I get the message
476 <userinput>bad command or file name</userinput>.
477 I have tried various alternatives but still cannot install.
478 </para>
479 </question>
480 <answer>
481 <para>
482 You should confirm that you have a Java runtime environment installed, which
483 will include <filename>java.exe</filename> and the version that omits a separate
484 terminal window, <filename>javaw.exe</filename>. Make sure that the directory
485 containing <filename>java.exe</filename> or <filename>javaw.exe</filename>is found
486 in the value of your <filename>PATH</filename> environment variable.
487 Otherwise you should give the full path to the chosen loader on your command line.
488 </para>
489 </answer>
490 </qandaentry>
491</qandadiv>
492
493</qandaset>
494
495</sect1>