1 2 Previous Next 19 Replies Latest reply on Jul 27, 2016 4:34 AM by Ilya Buziuk

    Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??

    Wayne McDermott Newbie

      I am going around in circles trying to get this editor to work. According to the FAQ, Windows 10 is out of the question, the only option is to disable the XULRunner at startup. I cannot even load JBoss Developer Studio in Fedora as it is complaining about the VM so I have put that aside for the moment. It did install on a fresh Ubuntu VM but the Visual Page Editor won't run and I cannot change the engine configuration due to GTK3. I tried downloading GTK2 (over 700MB) but it has made no difference. Any advice on how to proceed would be greatly appreciated.

        • 1. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
          Mickael Istria Newbie

          JBoss Developer Studio is known to work well under Fedora 23. Actually, Fedora 23 is currently the most reliable Linux distribution for JBoss Developer Studio or all Eclipse-based applications. If you tell us more about your problem with Fedora, we'd rather assist you with it than sending you in the Windows 10 and Ubuntu limbos ;) If you want to stick with Ubuntu, a possible way to have JBDS working under Ubuntu 16.04 is to install and use gnome-shell instead of Unity (Unity is the desktop environment that's not really compliant with many standard practices in the Linux world, it's the cause of many problems). I believe on Ubuntu, installing gnome-shell is only a matter of doing "apt-get install gnome-shell", make sure libwebkitgtk3 is installed -this is required for the Visual Page Editor- and to keep using GTK3. Hope this helps!

          • 2. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
            Mickael Istria Newbie

            About the VM in Fedora, you can probably try to update the studio/jbdevstudio.ini file to fix the location of the VM. It's possible that this location changes when updating, but this doesn't cascade the change to this configuration file. If this works, you can even try to remove the -vm and its value settings. It should work and always decide the location of the JVM according to your JAVA_HOME or java binary location at each startup so it better handles JVM changes.

            • 3. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
              Wayne McDermott Newbie

              Thanks very much Mickael, I will go back to Fedora 23, concentrate on getting it installed successfully there and report back. Thanks again.

              • 4. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                Ilya Buziuk Newbie

                Hello, Wayne

                I do believe that VPE should work fine on Ubuntu. You can try the following steps:

                - apt-get install libwebkitgtk-1.0-0  (install GTK 2 libs)

                - disable GTK3 by exporting SWT_GTK3=0

                Basically, after this steps studio should use GTK2 and both engines (JSP / JSF  & HTML5) will be available.

                • 5. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                  Wayne McDermott Newbie

                  Hello Mickael,

                   

                  I have jdevstudio running successfully in Fedora 23, I have imported the BPM tutorial project I had been building in Windows 10 and am getting the same "Could not open the visual page editor" error. I have installed GTK2 with dnf install libwebkitgtk-1.0.so.0, switched off GTK3 with "export SWT_GTK3=0 (thanks Ilya) but have the same problem and cannot change the engine to JSP/JSF.

                   

                  I am posting the details below. Thanks again for all the help!

                   

                  org.jboss.tools.vpe.xulrunner.XulRunnerException: You currently have Visual editor configured to have better HTML5 experience. If you want to see preview for JSF pages please change Visual Editor Browser Engine to JSF option in <a href="#">Visual Page Editor Preferences</a> and restart Eclipse.

                    at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.ensureEmbeddedXulRunnerIsNotDisabledByDialog(XulRunnerBrowser.java:286)

                    at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:120)

                    at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128)

                    at org.jboss.tools.vpe.editor.mozilla.XulRunnerEditor2.<init>(XulRunnerEditor2.java:23)

                    at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:594)

                    at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:813)

                    at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:283)

                    at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1102)

                    at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:511)

                    at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:363)

                    at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)

                    at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)

                    at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)

                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                    at java.lang.reflect.Method.invoke(Method.java:498)

                    at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)

                    at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:898)

                    at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:879)

                    at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:121)

                    at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:345)

                    at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:264)

                    at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)

                    at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104)

                    at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73)

                    at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55)

                    at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1306)

                    at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:103)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:658)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:525)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:509)

                    at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:69)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:151)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:151)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:151)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveRenderer.processContents(PerspectiveRenderer.java:49)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.showTab(PerspectiveStackRenderer.java:82)

                    at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:103)

                    at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.postProcess(PerspectiveStackRenderer.java:63)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:658)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:151)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:71)

                    at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:614)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)

                    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1061)

                    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)

                    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)

                    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)

                    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)

                    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)

                    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)

                    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)

                    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)

                    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

                    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)

                    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

                    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)

                    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)

                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                    at java.lang.reflect.Method.invoke(Method.java:498)

                    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)

                    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)

                    at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

                    at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

                  • 6. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                    Ilya Buziuk Newbie

                    Hello, Wayne

                    I guess you still running against GTK3. Please, try to run studio the following way:

                    ./jbdevstudio SWT_GTK3=0

                    After that GTK2 should be used and two engines will be available - Snaggy - easy screenshots

                    Please, let me know if this works for you

                    • 7. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                      Wayne McDermott Newbie

                      Good evening Ilya, I have just tried that, it makes no difference. The editor cannot be displayed and "switching visual editor engine is not available under GTK3 or when embedded XULRunner is disabled". Maybe I should try enabling the embedded XULRunner? Not sure how to do that though.

                       

                      Thanks again

                       

                      Wayne

                      • 8. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                        Ilya Buziuk Newbie

                        Well, XULRunner should be enabled by default unless there is a -Dorg.jboss.tools.vpe.loadxulrunner=false  in jbdevstudio.ini / eclipse.ini. Unfortunately, I have no Fedora ready on hand but VPE seems to work fine on Ubuntu for me - Snaggy - easy screenshots

                        Please, try the following steps (if  VPE doesn't work in this case I will open a jira):

                         

                        - check there is no -Dorg.jboss.tools.vpe.loadxulrunner=false  in jbdevstudio.ini / eclipse.ini

                        - open terminal and run export SWT_GTK3=0

                        - launch studio  from the same terminal  ./jbdevstudio


                        NOTE: Make sure that GTK2 libs installed on Fedora machine - yum install webkitgtk

                        • 9. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                          Ilya Buziuk Newbie

                          Wayne,

                          actually you can use VPE on windows but the studio should be installed against x32 bit JVM:

                           

                          - download and run Stand-alone Installer 9.1.0 GA from JBoss Tools - JBoss Developer Studio 9.1.0.GA

                          - on "Step 4" of the installation you will likely see the following - Snaggy - easy screenshots (VPE is not supported for selected jvm)

                          - change JVM to x32 version and continue installation - https://snag.gy/wWe3fR.jpg

                           

                          Basically, installing against x32 JVM should bring VPE on Windowsvm32.png

                          • 10. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                            Wayne McDermott Newbie

                            Good morning Ilya,

                             

                            Thank you very much, I will work on getting it up in Windows today, my eventual BPM clients are all Windows based as are the examples I am using to climb the JBoss learning cliff.

                             

                            It now works in Ubuntu ! The trick is to start from the terminal with ~/jbdevstudio/jbdevstudio not from the icon I have placed on the Gnome shell dash. I will work on why that is later, after professor google teaches me how to change dash arguments.

                             

                            On Fedora 23 it crashes the VM which is annoying. I have attached the error log it generates. I am keen on getting it working and stable in Fedora 23 and would be happy to start with a fresh install of the OS if that is the only way to get it working.

                            • 11. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                              Wayne McDermott Newbie

                              Well I have it working on Windows and Ubuntu. I then set up a brand new Fedora 23 VM. After an OS update with dnf I installed jboss-devstudio-9.0.1ga-installer-standalone.jar. I then opened terminal, entered EXPORT SWT-GTK3=0 and then ~/jbdevstudio/studio/jbdevstudio, I get the option to change from HTML5 to JSF which I accept and then it crashes. I would be keen to get this solved as I am a big fan of Fedora (though a JBPM newbie) and there are bound to be other newcomers finding themselves in the same situation.

                              • 12. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                                Ilya Buziuk Newbie

                                Hello, Wayne

                                I have created a jira for Fedora 23 VM crash coupled with VPE - [JBIDE-22288] VPE crashes studio with JRE fatal error on Fedora 23 - JBoss Issue Tracker

                                Thank you for your report and feel free to add more details in jira in case I missed smth.

                                • 13. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                                  Wayne McDermott Newbie

                                  Hello Ilya,

                                   

                                  I am delighted to help. I hope it is not something stupid I am doing that is just wasting your time.

                                  • 14. Re: Visual Page Editor on Ubuntu 16.04? Or Fedora 23? Or Windows 10??
                                    Ilya Buziuk Newbie

                                    Thanks Wayne,

                                    I'm quite sure that this is a critical issue and not just some missing configurations. According to the log (Problematic frame:# C  [libplds4.so+0x1697] ) it is very likely upstream one coupled with WebKit / Xulrunner conflict - [JBIDE-9144] VPE crashes with Eclipse 3.7 on some Linux distributions - JBoss Issue Tracker

                                    1 2 Previous Next