facebook

Install kills X [Closed]

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #206768 Reply

    James Ots
    Member

    I’ve just upgraded to SuSE 9.1, and on running EnterpriseWorkbenchInstaller_030702.bin, X restarts. Any ideas?

    #206775 Reply

    Scott Anderson
    Participant

    No ideas at all. However, it it’s causing a problem of any kind, I’d suggest using our manual install procedures. You can download the zip file from the downloads page and the instructions are included in HTML format. It’s really quite simple.

    #206816 Reply

    James Ots
    Member

    Ok, I’ve now installed it manually, and it all runs up fine. However, when I try to import one of my old myeclipse projects into the workspace I get this:

    JVM terminated. Exit code=1
    /usr/lib/java/bin/java
    -cp /home/james/opt/eclipse-M8/startup.jar org.eclipse.core.launcher.Main
    -os linux
    -ws gtk
    -arch x86
    -showsplash /home/james/opt/eclipse-M8/eclipse -showsplash 600
    -exitdata /home/james/opt/eclipse-M8/eclipse -exitdata 3f8006
    -data /home/james/workspace-M8-b
    -vm /usr/lib/java/bin/java
    -vmargs
    -cp /home/james/opt/eclipse-M8/startup.jar org.eclipse.core.launcher.Main

    This is in the log file:

    !SESSION May 08, 2004 11:38:01.81 ----------------------------------------------
    java.version=1.4.2_04
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_GB
    !ENTRY org.eclipse.osgi May 08, 2004 11:38:01.82
    !MESSAGE Bundle reference:file:/home/james/opt/eclipse-M8/plugins/org.eclipse.jdt.debug_3.0.0/ [55] was not resolved
    !ENTRY org.eclipse.osgi May 08, 2004 11:38:01.83
    !MESSAGE Bundle reference:file:/home/james/opt/eclipse-M8/plugins/org.eclipse.debug.ui_3.0.0/ [71] was not resolved

    On following attempts to run the programme it seems to crash if I open a .jsp file while in the MyEclipse view, or if I switch to MyEclipse view while viewing a .jsp file.

    #206817 Reply

    James Ots
    Member

    By the way, this is what I get in the log on subsequent attempts:

    !SESSION May 08, 2004 11:46:52.206 ---------------------------------------------
    java.version=1.4.2_04
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_GB
    !ENTRY org.eclipse.osgi May 08, 2004 11:46:52.208
    !MESSAGE Bundle reference:file:/home/james/opt/eclipse-M8/plugins/org.eclipse.jdt.debug_3.0.0/ [55] was not resolved
    !ENTRY org.eclipse.osgi May 08, 2004 11:46:52.208
    !MESSAGE Bundle reference:file:/home/james/opt/eclipse-M8/plugins/org.eclipse.debug.ui_3.0.0/ [71] was not resolved
    !ENTRY org.eclipse.ui 4 4 May 08, 2004 11:47:41.949
    !MESSAGE Unable to find view label: org.eclipse.debug.ui.ConsoleView
    !ENTRY org.eclipse.ui 4 4 May 08, 2004 11:47:41.954
    !MESSAGE Could not create view: com.genuitec.eclipse.core.browserview.perspectiveextension
    #206818 Reply

    Scott Anderson
    Participant

    James,

    Most of what you’re seeing is normal. The debug log entries in your first post are normal because we send updated versions of those two Eclipse plugins in order to enable source level JSP debugging. In your second post, I believe the ConsoleView has been renamed, so if your old workspace had it open, it can no longer be found. And, our browser view doesn’t work on some flavors of Linux when certain default settings are not available in the environment.

    That’s a long way of saying that these messages are not the root cause of the difficulty you’re experiencing. Is your project very large? Could the JVM be suddenly running out of RAM? Please try modifying the startup command to include ‘-Xms128M -Xmx384M’ after the ‘-vmargs’ entry to test this theory. Did you delete the <workspace>/.metadata/.config and <eclipse>/configuration directories before starting up with MyEclipse? Please try that as it will force a complete refresh of your installation. Does Eclipse 3.0 M8 run well without MyEclipse installed? Is the JDK you’re using new? If the above doesn’t work, can you try running Eclipse by itself for a bit and seeing if you experience a similar problem? It might be a low-level interaction between your Linux release / JDK / SWT or something. We’ll just have to poke around until we determine what that might me.

    #206820 Reply

    James Ots
    Member

    Well, Eclipse was running on its own fine until you posted that message 😕

    Now it dies all over the place, which means that it’s not your fault. Which is a shame, because I’m not going to get half such good support from eclipse mailings lists.

    #206822 Reply

    Riyad Kalla
    Member

    James,
    Is this a normal install of SuSE? Did you recompile anything with too agressive of settings? Is your kernel not stock?

    This is certainly a strange one…

    #206823 Reply

    James Ots
    Member

    I’ve spotted what’s killing it. It’s the Qt-GTK theme. I’ve switched to Industrial instead now and everything is fine. I had recompiled Qt-GTK after upgrading, but obviously something wasn’t right.

    Anyway, it’s all working now. Sorry for any inconvenience!

    #206824 Reply

    Riyad Kalla
    Member

    Anyway, it’s all working now.

    Sorry for any inconvenience!

    Its no problem at all, that’s our job 😉

Viewing 9 posts - 1 through 9 (of 9 total)
Reply To: Install kills X [Closed]

You must be logged in to post in the forum log in