Details

      Description

      First program launch OK
      All subsequent program launch crash when starting to display user interface.
      Can not run anymore.

      Workaround :
      Edit file /home/username/.ApacheDirectoryStudio/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.prefs
      Change showIntro=false to showIntro=true

      Can launch the program ONCE, showIntro reset to false then the program can not be launched again

        Activity

        Hide
        elecharny Emmanuel Lecharny added a comment -

        Have you tried with the Sun JDK ?

        Show
        elecharny Emmanuel Lecharny added a comment - Have you tried with the Sun JDK ?
        Hide
        Puce00 Harold added a comment -

        Thank you for your reply.
        Just installed Sun JDK : #java -version
        java version "1.8.0_40"
        Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
        Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)

        and confirm the exact same failing behaviour

        Centos version is CentOS release 6.6 (Final)
        Anything else I can easily check or try ?

        Show
        Puce00 Harold added a comment - Thank you for your reply. Just installed Sun JDK : #java -version java version "1.8.0_40" Java(TM) SE Runtime Environment (build 1.8.0_40-b26) Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode) and confirm the exact same failing behaviour Centos version is CentOS release 6.6 (Final) Anything else I can easily check or try ?
        Hide
        seelmann Stefan Seelmann added a comment -

        Please try if a workaround from DIRSTUDIO-962 works for you, especially the

        -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false

        option seems promising.

        The Eclipse libraries (especially SWT) used by Studio 2.0.0-M8 are just too old and don't play well with recent Gnome versions. We are working on a release based on latest Eclipse Luna.

        Show
        seelmann Stefan Seelmann added a comment - Please try if a workaround from DIRSTUDIO-962 works for you, especially the -Dorg.eclipse.swt.internal.gtk.cairoGraphics= false option seems promising. The Eclipse libraries (especially SWT) used by Studio 2.0.0-M8 are just too old and don't play well with recent Gnome versions. We are working on a release based on latest Eclipse Luna.
        Hide
        Puce00 Harold added a comment -

        Newbie inside.

        I've added the -Dorg... line in .../ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130628/configuration/config.ini file
        Result : still crashing at launch

        I've created .../ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130628/ApacheStudioDirectory.ini file with -Dorg... line
        Result : still crashing at launch

        Not sure that is what you where expecting from me though.
        Thanks Stefan

        Show
        Puce00 Harold added a comment - Newbie inside. I've added the -Dorg... line in .../ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130628/configuration/config.ini file Result : still crashing at launch I've created .../ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130628/ApacheStudioDirectory.ini file with -Dorg... line Result : still crashing at launch Not sure that is what you where expecting from me though. Thanks Stefan
        Hide
        seelmann Stefan Seelmann added a comment -

        Harold, you tried the right thing.

        Do you get a crash report, or is there a hs_error.log, or are the any hints in ~/.ApacheDirectoryStudio/.metadata/.log? Then please post them.

        What should work till the new release is out: Download and install a regular Eclipse form http://www.eclipse.org/downloads/ (e.g. Eclipse IDE for Java Developers), within that install the Studio plugins (Menu Help -> Install New Software..., Work with "http://directory.apache.org/studio/update/2.x", select all the features you need except the "RCP" feature).

        Show
        seelmann Stefan Seelmann added a comment - Harold, you tried the right thing. Do you get a crash report, or is there a hs_error.log, or are the any hints in ~/.ApacheDirectoryStudio/.metadata/.log? Then please post them. What should work till the new release is out: Download and install a regular Eclipse form http://www.eclipse.org/downloads/ (e.g. Eclipse IDE for Java Developers), within that install the Studio plugins (Menu Help -> Install New Software..., Work with "http://directory.apache.org/studio/update/2.x", select all the features you need except the "RCP" feature).
        Hide
        Puce00 Harold added a comment -

        This is the .metadata/.log file :
        !SESSION 2015-03-15 12:32:39.841 -----------------------------------------------
        eclipse.buildId=unknown
        java.version=1.8.0_40
        java.vendor=Oracle Corporation
        BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
        Framework arguments: -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false
        Command-line arguments: -os linux -ws gtk -arch x86_64 -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false

        !ENTRY org.eclipse.ui 2 0 2015-03-15 12:32:42.169
        !MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AddExceptionBreakpoint', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AddClassPrepareBreakpoint', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.StepIntoSelection', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Execute', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.171
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Display', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.171
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Inspect', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.171
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.ForceReturn', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.172
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.localJavaShortcut.debug', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.172
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.localJavaShortcut.run', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.172
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.javaAppletShortcut.debug', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.javaAppletShortcut.run', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Watch', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AllReferences', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AllInstances', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.InstanceCount', categoryId='org.eclipse.debug.ui.category.run'
        !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173
        !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.breakpoint.properties', categoryId='org.eclipse.debug.ui.category.run'

        Show
        Puce00 Harold added a comment - This is the .metadata/.log file : !SESSION 2015-03-15 12:32:39.841 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_40 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false Command-line arguments: -os linux -ws gtk -arch x86_64 -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false !ENTRY org.eclipse.ui 2 0 2015-03-15 12:32:42.169 !MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points. !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AddExceptionBreakpoint', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AddClassPrepareBreakpoint', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.StepIntoSelection', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.169 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Execute', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.171 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Display', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.171 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Inspect', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.171 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.ForceReturn', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.172 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.localJavaShortcut.debug', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.172 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.localJavaShortcut.run', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.172 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.javaAppletShortcut.debug', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.javaAppletShortcut.run', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.Watch', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AllReferences', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.AllInstances', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.commands.InstanceCount', categoryId='org.eclipse.debug.ui.category.run' !SUBENTRY 1 org.eclipse.ui 2 0 2015-03-15 12:32:42.173 !MESSAGE Commands should really have a category: plug-in='org.eclipse.jdt.debug.ui', id='org.eclipse.jdt.debug.ui.breakpoint.properties', categoryId='org.eclipse.debug.ui.category.run'
        Hide
        Puce00 Harold added a comment -

        Installed regular Eclipse to bypass the launch problem.

        Thank you very much for

        • writing this nice piece of software
        • the detailed instructions for newbie
        • providing such fast, kind & smart assistance

        Harold

        Show
        Puce00 Harold added a comment - Installed regular Eclipse to bypass the launch problem. Thank you very much for writing this nice piece of software the detailed instructions for newbie providing such fast, kind & smart assistance Harold
        Hide
        seelmann Stefan Seelmann added a comment -

        Upcoming release 2.0.0-M9 based on Eclipse Luna should fix the issue.

        Show
        seelmann Stefan Seelmann added a comment - Upcoming release 2.0.0-M9 based on Eclipse Luna should fix the issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Puce00 Harold
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development