[jbosstools-issues] [JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

[Konstantin Marmalyukov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075988#comment-13075988 ] 

Konstantin Marmalyukov commented on JBIDE-19773:
------------------------------------------------

{quote}Is there any particular reason why to select xulrunner version 10 or 24?{quote}
This will give RHEL7 users a chance to use HTML5 visula mode under GTK2(there is no webkitgtk library for RHEL7)
{quote}Xulrunner 10 & GTK2 & JBDS -> Error: XPCOM error http://i.imgur.com/F2l9Hgi.png
Xulrunner 24 & GTK2 & JBDS -> OK
Xulrunner 10.0.4esr & GTK2 & JBDS ->

    Error: Failed to evaluate javascript expression http://i.imgur.com/6MAHSw4.png
    Also opening any other HTML page (in VPE or internal browser) results in SIGSEGV
{quote}
So at least XulRunner24 works - good news. I'll check xulrunner10 on my machine
{quote}I also noticed, that when I specify external xulrunner (using -Dorg.eclipse.swt.browser.XULRunnerPath), VPE is unable to use WebKit (it always uses the specified xulrunner, no matter what is in settings){quote}
It's normal behavior - we cannot use webkit browser together with xulrunner.

> Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-19773
>                 URL: https://issues.jboss.org/browse/JBIDE-19773
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 4.3.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Konstantin Marmalyukov
>            Priority: Critical
>             Fix For: 4.3.0.Beta1
>
>
> It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution.
> Context:
> {quote}
> * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/2839/PROJECT=devstudio,eclipseBundleVersion=mars.M6,jdk=java18_default,label_exp=%28RHEL7||beaker||jboss-prod%29&&!ia64&&!ppc64&&!rhts/console
> *    SWT problem? GTK problem? xvnc/xvfb problem?
> *    missing webkit package on RHEL7 ?
> *    @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages)
> *      what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_to_build_jbosstools_faq.adoc#my-build-is-failing-due-to-unsatisfiedlinkerror-or-a-missing-so-file {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)