| Summary: | Eclipse exits on initiation of auto activation with out prompt, warning, or log messages when typing 'import java.' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Nick <nickkolegraff> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | eclipse.felipe, grant_gayed, remy.suen | ||||
| Version: | 3.6.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Nick
Which JRE are you using? I suspect that JRE you are using is not supported. Use Sun or IBM JRE. (In reply to comment #1) > Which JRE are you using? java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode (In reply to comment #3) > Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode If you're using HotSpot then it's usually pretty good about generating crash logs. Look for files starting with hs_err_pid in ~/ or your 'eclipse/' folder. What versions of Firefox/Seamonkey/XULRunner do you have installed? (In reply to comment #4) > (In reply to comment #3) > > Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode > > If you're using HotSpot then it's usually pretty good about generating crash > logs. Look for files starting with hs_err_pid in ~/ or your 'eclipse/' folder. > > What versions of Firefox/Seamonkey/XULRunner do you have installed? Will have to get back to you later this evening. (Not at home computer) Had to rip java version off from a previous post of mine :) Created attachment 188022 [details]
Most recent log file, there were many So didn't want to attach all
user@host:~$ seamonkey -version
Mozilla SeaMonkey 2.0.4, Copyright (c) 1998-2010 mozilla.org
user@host:~$ firefox -version
Mozilla Firefox 3.6.3, Copyright (c) 1998 - 2010 mozilla.org
Don't have XULRunner
The log shows that the Browser is attempting to use your seamonkey install, which is not valid (using seamonkey 1.x usually works ok for this but versions >= 2.x never do and are not supported). There's a good chance that your case is fixed by the fix for bug 319123, which is in the eclipse 3.6.2 stream. My first suggestion is to try a recent 3.6.2 build such as http://download.eclipse.org/eclipse/downloads/drops/M20110119-0834/index.php (the red 'X' beside it on the download page does not indicate a problem that matters). At the very least this should make the crash go away. To see if you also have Browser functionality (ie.- it found in alternative native renderer to use), try out Eclipse's "Internal Web Browser" view. If this does not help then your choices are: 1. Use WebKitGTK as the Browser's underlying renderer as described in http://www.eclipse.org/swt/faq.php#browserwebkitgtk . In a nutshell, either set java property "org.eclipse.swt.browser.UseWebKitGTK" to true in your 3.6.x, or instead get a 3.7-stream build and WebKitGTK should be used automatically. 2. Alternatively, download XULRunner from http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.13/runtimes/xulrunner-1.9.2.13.en-US.linux-i686.tar.bz2 and install it with either "./xulrunner --register-global" (as root) or "./xulrunner --register-user" (to install for one user only). After doing this Eclipse should pick it up and use it next time it's started. Closing report as a duplicate of bug 317383 since the underlying problem is the attempt of the Browser to use seamonkey 2.x. *** This bug has been marked as a duplicate of bug 317383 *** |