Attachment 71025 Details for Bug 185753 – More SWT release notes updates

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

[patch] More SWT release notes updates

swt_relnotes_patch.txt (text/plain), 11.01 KB, created by Carolyn MacLeod

on 2007-06-12 10:55:34 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Carolyn MacLeod

Created: 2007-06-12 10:55:34 EDT

Size: 11.01 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.platform-feature
>Index: rootfiles/readme/readme_eclipse.html
>===================================================================
>RCS file: /cvsroot/eclipse/org.eclipse.platform-feature/rootfiles/readme/readme_eclipse.html,v
>retrieving revision 1.91
>diff -u -r1.91 readme_eclipse.html
>--- rootfiles/readme/readme_eclipse.html	8 Jun 2007 17:59:25 -0000	1.91
>+++ rootfiles/readme/readme_eclipse.html	12 Jun 2007 14:50:51 -0000
>@@ -723,31 +723,36 @@
> <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>
>+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 on Windows XP with SP2</h4>
>+<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 
>+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).
>-(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87798">87798</a>)</p>
>+(See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=87798">87798</a> for details).</p>
> 
>-<h4>Internet Explorer sometimes freezes on PDF documents with Acrobat Reader 6.</h4>
>+<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 on Windows XP with SP2.</h4>
>+<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 on Motif</h4>
>+<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 
>@@ -757,7 +762,6 @@
> (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 
>@@ -776,29 +780,26 @@
> 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>
>+<h4> Unable to drag data between 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 the Eclipse bug report. (bug <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>
>+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>
>@@ -808,14 +809,13 @@
> 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>
>+<h4> Using IBM J9 VM (Photon and 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>
>+
>+<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
>@@ -829,11 +829,11 @@
>   </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
>@@ -858,7 +858,7 @@
> 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 on Windows and OS X</h4>
>+<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
>@@ -867,22 +867,36 @@
> <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>System hangs on Intel Mac OS X</h4>
>+<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>).
>+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>PPC crashes with IBM 1.5 VM</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: 
>-"eclipse -vmargs -Dosgi.locking=none -Xnojit".
>+<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.
> </p>
> 
>-<h4>Printing on GTK</h4>
>-<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.
>+<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>
>

Actions: View | Diff

Attachments on bug 185753: 66564 | 66706 | 66939 | 68276 | 68391 | 68798 | 70402 | 70408 | 70439 | 70543 | 70722 | 71025 | 71061