[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16290: --------------------------------------- {quote} JBIDE-16280 VPE/XulRunner crashes workbench {quote} We are using our own version of XULRunner compiled with GTK2. An application (JBDS, Eclipse, etc) can't load different versions of a library (GTK2 and GTK3, for instance). These are possible solutions: - compiling XULRunner with GTK3 (the best solution in my opinion) - removing/disabling XULRunner/VPE - using GTK2 {quote} Where is this configured in tests? {quote} https://github.com/snjeza/jbosstools-central/commit/6526bfe6017112f573b79... {quote} Can you please give details about what's exactly failing in Central tests that made you set SWT_GTK3=0 {quote} I have already described the issue. See https://issues.jboss.org/browse/JBIDE-16282?focusedCommentId=12930558&... Disabling GTK3 solves the issue. I will check if it is possible to solve it without disabling GTK3. Anyway, the main issue is related to XULRunner. Porting it to GTK3 isn't trivial. We could do the following: - if a user starts Eclipse with GTK3, we would disable XULRunner (the VPE editor) - if a user tries to open the VPE editor, we would warn him that the VPE editor requires GTK2 and would describe the way to run Eclipse with GTK2(export SWT_GTK3=0; ../eclipse) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira