Attachment #71025 for bug #185753

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.




<p>The SWT Browser widget uses a platform-specific web browser to render HTML.
The org.eclipse.swt.SWTError exception (&quot;No more handles&quot;) is thrown
on platforms that don't meet the requirements for running the Browser widget.
Supported platforms and prerequisites are listed on the SWT FAQ item <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">
&quot;Which platforms support the SWT Browser?&quot;</a>.</p>

<h4>Crash when using the file dialog (Windows XP with SP2 only)</h4>
<p>With some versions of Synergy from Telelogic, Eclipse will crash when you try to open a file 
dialog.  This is due to a problem with the CMExplorer.dll.  The workaround is to
upgrade to Synergy 6.4 (or higher) or to run <code>regsvr32 /u CMExplorer.dll</code> and 
reboot (note that this will disable Active CM).
(See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87798">87798</a> for details).</p>

<h4>Opening File Dialog crashes eclipse (Vista only)</h4>
<p>On Vista, launching eclipse using <code>-vmargs -Xmx[any size]</code> can crash eclipse when the FileDialog is opened.
The workaround is to use the default heap size, i.e. do not use the <code>-Xmx</code> VM args.
See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=188317">bug 188317</a> for details.</p>

<h4>Internet Explorer sometimes freezes on PDF documents with Acrobat Reader 6 (Windows only)</h4>
<p>With Acrobat Reader 6 or 7, some users have experienced an unresponsive user 
interface for up to two minutes when closing a browser which is displaying a PDF document.
The workaround is to disable displaying PDF in the browser. In Adobe Reader
select Edit &gt; Preferences... &gt; Internet and uncheck 'Display PDF in browser'.
(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56184">56184</a>)</p>

<h4>Crash while editing text (Windows XP with SP2 only)</h4>
<p>Some users who have installed Service Pack 2 on Windows XP have experienced
crashes while using editors in Eclipse.  The workaround is to place a working version 
of Windows\System32\USP10.DLL in the Eclipse startup directory or uninstall
Service Pack 2.
(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56390">56390</a>)</p>

<h4>Input Method broken (Motif only)</h4>
<p>Some versions of RedHat Linux such as Fedora Core 3 and Enterprise Linux WS 
release 4 use a new technology called IIIM (Intranet/Internet Input Method
Framework) to replace the old XIM (X input method).   When running on these 

(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89722">89722</a>)</p>

<h4>Eclipse does not start on Linux-Motif with Xinerama and a UTF-8 locale</h4>

<p>The Linux-motif build of Eclipse does not launch properly when run on a 
computer with Xinerama (provides support for dual head monitors) and a UTF-8 
locale.  The workaround for this problem is to change the locale to a non-UTF-8 

encountered when copying from an Eclipse target workbench, suspending the target
workbench at a breakpoint and pasting into the hosting Eclipse workbench. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44915">44915</a>)</p>

<h4> Unable to drag data between applications in simplified Chinese locale (Motif only)</h4>
applications in simplified Chinese locale (Motif only)</h4>
<p>When configured for the simplified Chinese locale, it is not possible to
drag data between applications running on the Motif window system. This is a
known limitation of the Open Motif library. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=29777">29777</a>)</p>
<h4> Crash when attempting to
launch file browser (AIX Motif only)</h4>

<h4> Crash when attempting to launch file browser (AIX Motif only)</h4>
<p>There is a known AIX graphics bug affecting certain levels of AIX
releases. Ensure that the AIX install includes the necessary service updates as
described in the &quot;Install notes/requirements for Eclipse on AIX&quot;
attachment to Eclipse bug report number <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34524">34524</a></p>

<h4> Available colors on 8-bit Linux (Linux only)</h4>
<p>Typically, in Gnome Linux installs running with 8-bit visuals (i.e. 256
color mode), before the Eclipse application is started there are no free colors.
This may mean that Eclipse is unable to allocate the default widget background
color, causing it to display a white background. The functionality, however, is
otherwise unaffected.</p>
<h4> List and ComboBox on Windows
NT (Windows NT only)</h4>
<p>On Windows NT only, you should avoid creating items in a <code>List</code>

<h4> List and ComboBox on Windows NT (Windows NT only)</h4>
<p>On Windows NT only, you should avoid creating items in a <code>List</code>
or <code>ComboBox</code> with strings longer than 1000 characters. Doing so may
result in a General Protection Fault. This has been fixed in more recent
versions of Windows.</p>

crash if the IME client window is left open when the parent window is disposed.
(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32045">32045</a>)</p>

<h4> Using IBM J9 VM (Photon and AIX)</h4>
AIX)</h4>
<p>On QNX Photon and IBM AIX, the SWT library will not be found when running
with an IBM J9 1.5 VM. This is a bug in the IBM J9 class library in version 1.5.
You can workaround this problem by adding the SWT library directory to your
LD_LIBRARY_PATH environment variable.</p>

<h4> Missing permissions for SWT native libraries in workspace (HP-UX only)</h4>
<p>When retrieving the SWT Motif fragment into an Eclipse workspace, the
permissions of the native libraries are reset. This creates a problem on HP-UX
because shared libraries need to have execute permission. Attempting to

  </blockquote>
</blockquote>
<p></p>

<h4> gtk_init_check and X11 socket failure when using the IBM 1.4.2 JRE (GTK only)</h4>
<p>Under RHEL 3.1 with the IBM 1.4.2 JRE and a large number
of plugins, Eclipse may fail to launch with an exception from
<tt>gtk_init_check</tt> along with this error:</p>

<pre>
_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local

and GTK+ bug <a href="http://bugzilla.gnome.org/show_bug.cgi?id=109246">109246</a>
for more information.</p>

<h4>Browser does not display applets (Windows and OS X)</h4>
<p>The Browser widget cannot be used to display pages containing Java applets on Windows
and OS X, as a result of crashes that occur when attempting to launch a second JVM for the
applet that is in-process with the main process JVM.  The workaround for clients wishing

<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59506">59506</a> and
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=100622">100622</a>).</p>

<h4>Eclipse hangs with earlier versions of Quicktime (Intel Mac OS X only)</h4>
<p>Some users reported encountering system hangs while using Eclipse on Intel-based Macs.
These hangs were traced to a problem in some versions of QuickTime, which has now been fixed.
Therefore, Eclipse users on Intel-based Macs should use Quicktime's update facilities to ensure
that their Quicktime version is at least 7.1.1. (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=142892">142892</a>).
</p>

<h4>Typing in an editor crashes with IBM 1.5 VM (Linux GTK PPC only)</h4>
<p>When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor.
If using this VM you must disable the JIT with the -Xnojit vm argument to avoid the crashes
(see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116730">116730</a>).
The command line for launching Eclipse with this vm should be: <br>
<code>eclipse -vmargs -Dosgi.locking=none -Xnojit</code>
</p>

<h4>Eclipse won't start (Linux GTK PPC only)</h4>
<p>Eclipse fails to create a lock file with reason &quot;No locks available&quot;. 
To launch eclipse you must disable file locking using the osgi.locking property.
For example, you could launch eclipse as follows: <br>
<code>eclipse -vmargs -Dosgi.locking=none</code>
</p>

<h4>SWT_AWT bridge doesn't work (Mac OSX only)</h4>
<p>In order to use the SWT_AWT bridge on the Mac, OS X jre version 1.5.0 Release 5
(or greater) must be used.
"eclipse -vmargs -Dosgi.locking=none -Xnojit".
</p>

<h4>Eclipse printing is disabled or Eclipse hangs when opening editor (GTK only)</h4>
<p>In order to print from eclipse on GTK, you need to have GTK+ version 2.10 or later.
In addition, at least two print backends must exist on the machine: file and lpr.
Assuming a that GTK was installed in /usr, the installed backends can be viewed at /usr/lib/gtk-2.0/2.10.0/printbackends.
</p>


Return to bug 185753

Lines 723-753 Link Here

(-)rootfiles/readme/readme_eclipse.html (-34 / +48 lines)
723	<p>The SWT Browser widget uses a platform-specific web browser to render HTML.	723	<p>The SWT Browser widget uses a platform-specific web browser to render HTML.
724	The org.eclipse.swt.SWTError exception ("No more handles") is thrown	724	The org.eclipse.swt.SWTError exception ("No more handles") is thrown
725	on platforms that don't meet the requirements for running the Browser widget.	725	on platforms that don't meet the requirements for running the Browser widget.
726	Supported platforms and prerequisites are listed on the SWT FAQ item <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">"Which	726	Supported platforms and prerequisites are listed on the SWT FAQ item <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">
727	platforms support the SWT Browser?"</a>.</p>	727	"Which platforms support the SWT Browser?"</a>.</p>
728		728
729	<h4>Crash when using the file dialog on Windows XP with SP2</h4>	729	<h4>Crash when using the file dialog (Windows XP with SP2 only)</h4>
730	<p>With some versions of Synergy from Telelogic, Eclipse will crash when you try to open a file	730	<p>With some versions of Synergy from Telelogic, Eclipse will crash when you try to open a file
731	dialog. This is due to a problem with the CMExplorer.dll. The workaround is to	731	dialog. This is due to a problem with the CMExplorer.dll. The workaround is to
732	upgrade to Synergy 6.4 (or higher) or to run <code>"regsvr32 /u CMExplorer.dll"</code> and	732	upgrade to Synergy 6.4 (or higher) or to run <code>regsvr32 /u CMExplorer.dll</code> and
733	reboot (note that this will disable Active CM).	733	reboot (note that this will disable Active CM).
734	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87798">87798</a>)</p>	734	(See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87798">87798</a> for details).</p>
735		735
736	<h4>Internet Explorer sometimes freezes on PDF documents with Acrobat Reader 6.</h4>	736	<h4>Opening File Dialog crashes eclipse (Vista only)</h4>
		737	<p>On Vista, launching eclipse using <code>-vmargs -Xmx[any size]</code> can crash eclipse when the FileDialog is opened.
		738	The workaround is to use the default heap size, i.e. do not use the <code>-Xmx</code> VM args.
		739	See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=188317">bug 188317</a> for details.</p>
		740
		741	<h4>Internet Explorer sometimes freezes on PDF documents with Acrobat Reader 6 (Windows only)</h4>
737	<p>With Acrobat Reader 6 or 7, some users have experienced an unresponsive user	742	<p>With Acrobat Reader 6 or 7, some users have experienced an unresponsive user
738	interface for up to two minutes when closing a browser which is displaying a PDF document.	743	interface for up to two minutes when closing a browser which is displaying a PDF document.
739	The workaround is to disable displaying PDF in the browser. In Adobe Reader	744	The workaround is to disable displaying PDF in the browser. In Adobe Reader
740	select Edit > Preferences... > Internet and uncheck 'Display PDF in browser'.	745	select Edit > Preferences... > Internet and uncheck 'Display PDF in browser'.
741	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56184">56184</a>)</p>	746	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56184">56184</a>)</p>
742		747
743	<h4>Crash while editing text on Windows XP with SP2.</h4>	748	<h4>Crash while editing text (Windows XP with SP2 only)</h4>
744	<p>Some users who have installed Service Pack 2 on Windows XP have experienced	749	<p>Some users who have installed Service Pack 2 on Windows XP have experienced
745	crashes while using editors in Eclipse. The workaround is to place a working version	750	crashes while using editors in Eclipse. The workaround is to place a working version
746	of Windows\System32\USP10.DLL in the Eclipse startup directory or uninstall	751	of Windows\System32\USP10.DLL in the Eclipse startup directory or uninstall
747	Service Pack 2.	752	Service Pack 2.
748	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56390">56390</a>)</p>	753	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56390">56390</a>)</p>
749		754
750	<h4>Input Method broken on Motif</h4>	755	<h4>Input Method broken (Motif only)</h4>
751	<p>Some versions of RedHat Linux such as Fedora Core 3 and Enterprise Linux WS	756	<p>Some versions of RedHat Linux such as Fedora Core 3 and Enterprise Linux WS
752	release 4 use a new technology called IIIM (Intranet/Internet Input Method	757	release 4 use a new technology called IIIM (Intranet/Internet Input Method
753	Framework) to replace the old XIM (X input method). When running on these	758	Framework) to replace the old XIM (X input method). When running on these
Lines 757-763 Link Here
757	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89722">89722</a>)</p>	762	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89722">89722</a>)</p>
758		763
759	<h4>Eclipse does not start on Linux-Motif with Xinerama and a UTF-8 locale</h4>	764	<h4>Eclipse does not start on Linux-Motif with Xinerama and a UTF-8 locale</h4>
760
761	<p>The Linux-motif build of Eclipse does not launch properly when run on a	765	<p>The Linux-motif build of Eclipse does not launch properly when run on a
762	computer with Xinerama (provides support for dual head monitors) and a UTF-8	766	computer with Xinerama (provides support for dual head monitors) and a UTF-8
763	locale. The workaround for this problem is to change the locale to a non-UTF-8	767	locale. The workaround for this problem is to change the locale to a non-UTF-8
Lines 776-804 Link Here
776	encountered when copying from an Eclipse target workbench, suspending the target	780	encountered when copying from an Eclipse target workbench, suspending the target
777	workbench at a breakpoint and pasting into the hosting Eclipse workbench. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44915">44915</a>)</p>	781	workbench at a breakpoint and pasting into the hosting Eclipse workbench. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44915">44915</a>)</p>
778		782
779	<h4> Unable to drag data between	783	<h4> Unable to drag data between applications in simplified Chinese locale (Motif only)</h4>
780	applications in simplified Chinese locale (Motif only)</h4>
781	<p>When configured for the simplified Chinese locale, it is not possible to	784	<p>When configured for the simplified Chinese locale, it is not possible to
782	drag data between applications running on the Motif window system. This is a	785	drag data between applications running on the Motif window system. This is a
783	known limitation of the Open Motif library. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=29777">29777</a>)</p>	786	known limitation of the Open Motif library. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=29777">29777</a>)</p>
784	<h4> Crash when attempting to
785	launch file browser (AIX Motif only)</h4>
786		787
		788	<h4> Crash when attempting to launch file browser (AIX Motif only)</h4>
787	<p>There is a known AIX graphics bug affecting certain levels of AIX	789	<p>There is a known AIX graphics bug affecting certain levels of AIX
788	releases. Ensure that the AIX install includes the necessary service updates as	790	releases. Ensure that the AIX install includes the necessary service updates as
789	described in the "Install notes/requirements for Eclipse on AIX"	791	described in the "Install notes/requirements for Eclipse on AIX"
790	attachment to the Eclipse bug report. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34524">34524</a>)</p>	792	attachment to Eclipse bug report number <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34524">34524</a></p>
791	<h4> Available colors on 8-bit	793
792	Linux (Linux only)</h4>	794	<h4> Available colors on 8-bit Linux (Linux only)</h4>
793	<p>Typically, in Gnome Linux installs running with 8-bit visuals (i.e. 256	795	<p>Typically, in Gnome Linux installs running with 8-bit visuals (i.e. 256
794	color mode), before the Eclipse application is started there are no free colors.	796	color mode), before the Eclipse application is started there are no free colors.
795	This may mean that Eclipse is unable to allocate the default widget background	797	This may mean that Eclipse is unable to allocate the default widget background
796	color, causing it to display a white background. The functionality, however, is	798	color, causing it to display a white background. The functionality, however, is
797	otherwise unaffected.</p>	799	otherwise unaffected.</p>
798	<h4> List and ComboBox on Windows
799	NT (Windows NT only)</h4>
800	<p>On Windows NT only, you should avoid creating items in a <code>List</code>
801		800
		801	<h4> List and ComboBox on Windows NT (Windows NT only)</h4>
		802	<p>On Windows NT only, you should avoid creating items in a <code>List</code>
802	or <code>ComboBox</code> with strings longer than 1000 characters. Doing so may	803	or <code>ComboBox</code> with strings longer than 1000 characters. Doing so may
803	result in a General Protection Fault. This has been fixed in more recent	804	result in a General Protection Fault. This has been fixed in more recent
804	versions of Windows.</p>	805	versions of Windows.</p>
Lines 808-821 Link Here
808	crash if the IME client window is left open when the parent window is disposed.	809	crash if the IME client window is left open when the parent window is disposed.
809	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32045">32045</a>)</p>	810	(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32045">32045</a>)</p>
810		811
811	<h4> Using IBM J9 VM (Photon and	812	<h4> Using IBM J9 VM (Photon and AIX)</h4>
812	AIX)</h4>
813	<p>On QNX Photon and IBM AIX, the SWT library will not be found when running	813	<p>On QNX Photon and IBM AIX, the SWT library will not be found when running
814	with an IBM J9 1.5 VM. This is a bug in the IBM J9 class library in version 1.5.	814	with an IBM J9 1.5 VM. This is a bug in the IBM J9 class library in version 1.5.
815	You can workaround this problem by adding the SWT library directory to your	815	You can workaround this problem by adding the SWT library directory to your
816	LD_LIBRARY_PATH environment variable.</p>	816	LD_LIBRARY_PATH environment variable.</p>
817	<h4> Missing permissions for SWT	817
818	native libraries in workspace (HP-UX only)</h4>	818	<h4> Missing permissions for SWT native libraries in workspace (HP-UX only)</h4>
819	<p>When retrieving the SWT Motif fragment into an Eclipse workspace, the	819	<p>When retrieving the SWT Motif fragment into an Eclipse workspace, the
820	permissions of the native libraries are reset. This creates a problem on HP-UX	820	permissions of the native libraries are reset. This creates a problem on HP-UX
821	because shared libraries need to have execute permission. Attempting to	821	because shared libraries need to have execute permission. Attempting to
Lines 829-839 Link Here
829	</blockquote>	829	</blockquote>
830	</blockquote>	830	</blockquote>
831	<p></p>	831	<p></p>
		832
832	<h4> gtk_init_check and X11 socket failure when using the IBM 1.4.2 JRE (GTK only)</h4>	833	<h4> gtk_init_check and X11 socket failure when using the IBM 1.4.2 JRE (GTK only)</h4>
833	<p>Under RHEL 3.1 with the IBM 1.4.2 JRE and a large number	834	<p>Under RHEL 3.1 with the IBM 1.4.2 JRE and a large number
834	of plugins, Eclipse may fail to launch with an exception from	835	of plugins, Eclipse may fail to launch with an exception from
835	<tt>gtk_init_check</tt> along with this error:</p>	836	<tt>gtk_init_check</tt> along with this error:</p>
836
837	<pre>	837	<pre>
838	_X11TransSocketOpen: socket() failed for local	838	_X11TransSocketOpen: socket() failed for local
839	_X11TransSocketOpenCOTSClient: Unable to open socket for local	839	_X11TransSocketOpenCOTSClient: Unable to open socket for local
Lines 858-864 Link Here
858	and GTK+ bug <a href="http://bugzilla.gnome.org/show_bug.cgi?id=109246">109246</a>	858	and GTK+ bug <a href="http://bugzilla.gnome.org/show_bug.cgi?id=109246">109246</a>
859	for more information.</p>	859	for more information.</p>
860		860
861	<h4>Browser does not display applets on Windows and OS X</h4>	861	<h4>Browser does not display applets (Windows and OS X)</h4>
862	<p>The Browser widget cannot be used to display pages containing Java applets on Windows	862	<p>The Browser widget cannot be used to display pages containing Java applets on Windows
863	and OS X, as a result of crashes that occur when attempting to launch a second JVM for the	863	and OS X, as a result of crashes that occur when attempting to launch a second JVM for the
864	applet that is in-process with the main process JVM. The workaround for clients wishing	864	applet that is in-process with the main process JVM. The workaround for clients wishing
Lines 867-888 Link Here
867	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59506">59506</a> and	867	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59506">59506</a> and
868	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=100622">100622</a>).</p>	868	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=100622">100622</a>).</p>
869		869
870	<h4>System hangs on Intel Mac OS X</h4>	870	<h4>Eclipse hangs with earlier versions of Quicktime (Intel Mac OS X only)</h4>
871	<p>Some users reported encountering system hangs while using Eclipse on Intel-based Macs.	871	<p>Some users reported encountering system hangs while using Eclipse on Intel-based Macs.
872	These hangs were traced to a problem in some versions of QuickTime, which has now been fixed.	872	These hangs were traced to a problem in some versions of QuickTime, which has now been fixed.
873	Therefore, Eclipse users on Intel-based Macs should use Quicktime's update facilities to ensure	873	Therefore, Eclipse users on Intel-based Macs should use Quicktime's update facilities to ensure
874	that their Quicktime version is at least 7.1.1. (see bug	874	that their Quicktime version is at least 7.1.1. (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=142892">142892</a>).
875	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=142892">142892</a>).	875	</p>
		876
		877	<h4>Typing in an editor crashes with IBM 1.5 VM (Linux GTK PPC only)</h4>
		878	<p>When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor.
		879	If using this VM you must disable the JIT with the -Xnojit vm argument to avoid the crashes
		880	(see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116730">116730</a>).
		881	The command line for launching Eclipse with this vm should be: <br>
		882	<code>eclipse -vmargs -Dosgi.locking=none -Xnojit</code>
		883	</p>
		884
		885	<h4>Eclipse won't start (Linux GTK PPC only)</h4>
		886	<p>Eclipse fails to create a lock file with reason "No locks available".
		887	To launch eclipse you must disable file locking using the osgi.locking property.
		888	For example, you could launch eclipse as follows: <br>
		889	<code>eclipse -vmargs -Dosgi.locking=none</code>
876	</p>	890	</p>
877		891
878	<h4>PPC crashes with IBM 1.5 VM</h4>	892	<h4>SWT_AWT bridge doesn't work (Mac OSX only)</h4>
879	<p>When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor. If using this VM you must disable the JIT	893	<p>In order to use the SWT_AWT bridge on the Mac, OS X jre version 1.5.0 Release 5
880	with the -Xnojit vm argument to avoid the crashes (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116730">116730</a>). The command line for launching Eclipse with this vm should be:	894	(or greater) must be used.
881	"eclipse -vmargs -Dosgi.locking=none -Xnojit".
882	</p>	895	</p>
883		896
884	<h4>Printing on GTK</h4>	897	<h4>Eclipse printing is disabled or Eclipse hangs when opening editor (GTK only)</h4>
885	<p>GTK 2.10 supports printing. In order for it to work properly, at least two print backends must exist on the machine: file and lpr.	898	<p>In order to print from eclipse on GTK, you need to have GTK+ version 2.10 or later.
		899	In addition, at least two print backends must exist on the machine: file and lpr.
886	Assuming a that GTK was installed in /usr, the installed backends can be viewed at /usr/lib/gtk-2.0/2.10.0/printbackends.	900	Assuming a that GTK was installed in /usr, the installed backends can be viewed at /usr/lib/gtk-2.0/2.10.0/printbackends.
887	</p>	901	</p>
888		902