Eclipse: The SWT browser widget could not be created The 2019 Stack Overflow Developer Survey Results Are InHow do you disable browser Autocomplete on web form field / input tag?Create ArrayList from arrayHow to align checkboxes and their labels consistently cross-browsersHow can you speed up Eclipse?How can I create an executable JAR with dependencies using Maven?How to make a div 100% height of the browser window?'Must Override a Superclass Method' Errors after importing a project into Eclipse“Debug certificate expired” error in Eclipse Android pluginsCreating a memory leak with JavaHow to make SWT Browser control use Mozilla/Firefox instead of WebKit on Linux(Ubuntu 14)
aging parents with no investments
Dual Citizen. Exited the US on Italian passport recently
What is this 4-propeller plane?
Why isn't airport relocation done gradually?
Carnot-Caratheodory metric
Is there a name of the flying bionic bird?
Inline version of a function returns different value then non-inline version
Are USB sockets on wall outlets live all the time, even when the switch is off?
What does "sndry explns" mean in one of the Hitchhiker's guide books?
Output the Arecibo Message
Realistic Alternatives to Dust: What Else Could Feed a Plankton Bloom?
Why Did Howard Stark Use All The Vibranium They Had On A Prototype Shield?
What is the best strategy for white in this position?
Monty Hall variation
If a poisoned arrow's piercing damage is reduced to 0, do you still get poisoned?
How long do I have to send payment?
Access elements in std::string where positon of string is greater than its size
How was Skylab's orbit inclination chosen?
Pristine Bit Checking
Falsification in Math vs Science
Why don't Unix/Linux systems traverse through directories until they find the required version of a linked library?
What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?
How to make payment on the internet without leaving a money trail?
What do hard-Brexiteers want with respect to the Irish border?
Eclipse: The SWT browser widget could not be created
The 2019 Stack Overflow Developer Survey Results Are InHow do you disable browser Autocomplete on web form field / input tag?Create ArrayList from arrayHow to align checkboxes and their labels consistently cross-browsersHow can you speed up Eclipse?How can I create an executable JAR with dependencies using Maven?How to make a div 100% height of the browser window?'Must Override a Superclass Method' Errors after importing a project into Eclipse“Debug certificate expired” error in Eclipse Android pluginsCreating a memory leak with JavaHow to make SWT Browser control use Mozilla/Firefox instead of WebKit on Linux(Ubuntu 14)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have installed eclipse (4.10) on my Linux Machine (KDE Neon 5.15) and everything works quite well except for the JavaDoc. Whenever I view the JavaDoc-hover, I get a plain text representation and at the bottom it says
NOTE: The SWT Browser widget could not be created. This fallback mode doesn't show links and misses other functionality.
Further investigation led me to create a minimal SWT-example using the SWT Browser widget:
import org.eclipse.swt.SWT;
import org.eclipse.swt.browser.Browser;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
public class BrowserTest
public static void main(String[] args)
Display display = new Display();
Shell shell = new Shell(display);
shell.setLayout(new FillLayout());
Browser b = new Browser(shell, SWT.NONE);
b.setUrl("www.google.com");
shell.open();
while (!shell.isDisposed())
display.readAndDispatch();
display.sleep();
display.dispose();
Trying to execute this code failed with the exception
Exception in thread "main" org.eclipse.swt.SWTError: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.browser.MozillaDelegate.<init>(Unknown Source)
at org.eclipse.swt.browser.Mozilla.create(Unknown Source)
at org.eclipse.swt.browser.Browser.<init>(Unknown Source)
at Main.main(Main.java:31)
which clearly shows that the system is indeed unable to create the browser widget. Although this time the error message is more informative.
I also tried setting the style of the browser widget to SWT.MOZILLA
which yielded the same error message (as expected) and using SWT.WEBKIT
also threw the same error, though without any explanatory text (so only org.eclipse.swt.SWTError: No more handles
).
java html linux eclipse
migrated from unix.stackexchange.com 2 days ago
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
add a comment |
I have installed eclipse (4.10) on my Linux Machine (KDE Neon 5.15) and everything works quite well except for the JavaDoc. Whenever I view the JavaDoc-hover, I get a plain text representation and at the bottom it says
NOTE: The SWT Browser widget could not be created. This fallback mode doesn't show links and misses other functionality.
Further investigation led me to create a minimal SWT-example using the SWT Browser widget:
import org.eclipse.swt.SWT;
import org.eclipse.swt.browser.Browser;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
public class BrowserTest
public static void main(String[] args)
Display display = new Display();
Shell shell = new Shell(display);
shell.setLayout(new FillLayout());
Browser b = new Browser(shell, SWT.NONE);
b.setUrl("www.google.com");
shell.open();
while (!shell.isDisposed())
display.readAndDispatch();
display.sleep();
display.dispose();
Trying to execute this code failed with the exception
Exception in thread "main" org.eclipse.swt.SWTError: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.browser.MozillaDelegate.<init>(Unknown Source)
at org.eclipse.swt.browser.Mozilla.create(Unknown Source)
at org.eclipse.swt.browser.Browser.<init>(Unknown Source)
at Main.main(Main.java:31)
which clearly shows that the system is indeed unable to create the browser widget. Although this time the error message is more informative.
I also tried setting the style of the browser widget to SWT.MOZILLA
which yielded the same error message (as expected) and using SWT.WEBKIT
also threw the same error, though without any explanatory text (so only org.eclipse.swt.SWTError: No more handles
).
java html linux eclipse
migrated from unix.stackexchange.com 2 days ago
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
Okay to whoever voted this question as OT (or is thinking about it): The problem is more or less linux-specific (it certainly is when factoring in its solution). So where else would you want to post such a question, if not here? It occurs in Linux and it is being fixed inside Linux (not inside eclipse itself). To me it is therefore exactly what this site is all about.
– Raven
Apr 6 at 13:44
@muru I wouldn't call that "general debugging" the code is only in there as it helped getting to the root of the original problem. The question that gets answered here is why eclipse won't show the JavaDoc properly when being run on Linux. So I wouldn't say that counts as debugging.
– Raven
Apr 6 at 19:11
add a comment |
I have installed eclipse (4.10) on my Linux Machine (KDE Neon 5.15) and everything works quite well except for the JavaDoc. Whenever I view the JavaDoc-hover, I get a plain text representation and at the bottom it says
NOTE: The SWT Browser widget could not be created. This fallback mode doesn't show links and misses other functionality.
Further investigation led me to create a minimal SWT-example using the SWT Browser widget:
import org.eclipse.swt.SWT;
import org.eclipse.swt.browser.Browser;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
public class BrowserTest
public static void main(String[] args)
Display display = new Display();
Shell shell = new Shell(display);
shell.setLayout(new FillLayout());
Browser b = new Browser(shell, SWT.NONE);
b.setUrl("www.google.com");
shell.open();
while (!shell.isDisposed())
display.readAndDispatch();
display.sleep();
display.dispose();
Trying to execute this code failed with the exception
Exception in thread "main" org.eclipse.swt.SWTError: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.browser.MozillaDelegate.<init>(Unknown Source)
at org.eclipse.swt.browser.Mozilla.create(Unknown Source)
at org.eclipse.swt.browser.Browser.<init>(Unknown Source)
at Main.main(Main.java:31)
which clearly shows that the system is indeed unable to create the browser widget. Although this time the error message is more informative.
I also tried setting the style of the browser widget to SWT.MOZILLA
which yielded the same error message (as expected) and using SWT.WEBKIT
also threw the same error, though without any explanatory text (so only org.eclipse.swt.SWTError: No more handles
).
java html linux eclipse
I have installed eclipse (4.10) on my Linux Machine (KDE Neon 5.15) and everything works quite well except for the JavaDoc. Whenever I view the JavaDoc-hover, I get a plain text representation and at the bottom it says
NOTE: The SWT Browser widget could not be created. This fallback mode doesn't show links and misses other functionality.
Further investigation led me to create a minimal SWT-example using the SWT Browser widget:
import org.eclipse.swt.SWT;
import org.eclipse.swt.browser.Browser;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
public class BrowserTest
public static void main(String[] args)
Display display = new Display();
Shell shell = new Shell(display);
shell.setLayout(new FillLayout());
Browser b = new Browser(shell, SWT.NONE);
b.setUrl("www.google.com");
shell.open();
while (!shell.isDisposed())
display.readAndDispatch();
display.sleep();
display.dispose();
Trying to execute this code failed with the exception
Exception in thread "main" org.eclipse.swt.SWTError: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.browser.MozillaDelegate.<init>(Unknown Source)
at org.eclipse.swt.browser.Mozilla.create(Unknown Source)
at org.eclipse.swt.browser.Browser.<init>(Unknown Source)
at Main.main(Main.java:31)
which clearly shows that the system is indeed unable to create the browser widget. Although this time the error message is more informative.
I also tried setting the style of the browser widget to SWT.MOZILLA
which yielded the same error message (as expected) and using SWT.WEBKIT
also threw the same error, though without any explanatory text (so only org.eclipse.swt.SWTError: No more handles
).
java html linux eclipse
java html linux eclipse
edited 2 days ago
Raven
asked Apr 6 at 10:36
RavenRaven
1,25111023
1,25111023
migrated from unix.stackexchange.com 2 days ago
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
migrated from unix.stackexchange.com 2 days ago
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
Okay to whoever voted this question as OT (or is thinking about it): The problem is more or less linux-specific (it certainly is when factoring in its solution). So where else would you want to post such a question, if not here? It occurs in Linux and it is being fixed inside Linux (not inside eclipse itself). To me it is therefore exactly what this site is all about.
– Raven
Apr 6 at 13:44
@muru I wouldn't call that "general debugging" the code is only in there as it helped getting to the root of the original problem. The question that gets answered here is why eclipse won't show the JavaDoc properly when being run on Linux. So I wouldn't say that counts as debugging.
– Raven
Apr 6 at 19:11
add a comment |
Okay to whoever voted this question as OT (or is thinking about it): The problem is more or less linux-specific (it certainly is when factoring in its solution). So where else would you want to post such a question, if not here? It occurs in Linux and it is being fixed inside Linux (not inside eclipse itself). To me it is therefore exactly what this site is all about.
– Raven
Apr 6 at 13:44
@muru I wouldn't call that "general debugging" the code is only in there as it helped getting to the root of the original problem. The question that gets answered here is why eclipse won't show the JavaDoc properly when being run on Linux. So I wouldn't say that counts as debugging.
– Raven
Apr 6 at 19:11
Okay to whoever voted this question as OT (or is thinking about it): The problem is more or less linux-specific (it certainly is when factoring in its solution). So where else would you want to post such a question, if not here? It occurs in Linux and it is being fixed inside Linux (not inside eclipse itself). To me it is therefore exactly what this site is all about.
– Raven
Apr 6 at 13:44
Okay to whoever voted this question as OT (or is thinking about it): The problem is more or less linux-specific (it certainly is when factoring in its solution). So where else would you want to post such a question, if not here? It occurs in Linux and it is being fixed inside Linux (not inside eclipse itself). To me it is therefore exactly what this site is all about.
– Raven
Apr 6 at 13:44
@muru I wouldn't call that "general debugging" the code is only in there as it helped getting to the root of the original problem. The question that gets answered here is why eclipse won't show the JavaDoc properly when being run on Linux. So I wouldn't say that counts as debugging.
– Raven
Apr 6 at 19:11
@muru I wouldn't call that "general debugging" the code is only in there as it helped getting to the root of the original problem. The question that gets answered here is why eclipse won't show the JavaDoc properly when being run on Linux. So I wouldn't say that counts as debugging.
– Raven
Apr 6 at 19:11
add a comment |
1 Answer
1
active
oldest
votes
From the error message and from some further research it is clear, that the SWT browser widget relies on the XULRunner
software to render HTML. As the error message states, this hasn't been ported to GTK3 (yet) and can thus not be used. Per default eclipse does start in GTK3-mode though, so that's the root problem.
An attempt to solve it could be to force eclipse into GTK2-mode (see here) but further investigation of the Eclipse FAQ shows, that from Eclipse 4.8 and onward XULRunner isn't supported at all anymore.
Therefore the option to use the SWT.MOZILLA
style for creating the browser seems to be invalid in those versions. Instead one has to focus on getting the SWT.WEBKIT
style to work. For that another visit in the FAQ reveals that
WebKitGTK 1.2.0 or newer must be in the library load path.
Therefore I went ahead and searched for the respective library and installed it (libwebkitgtk-3.0-0
in my case).
After having installed that package above SWT-snipped started just fine and after having restarted eclipse, the JavaDoc was back to full functionality.
If this doesn't work for you directly, you might have to set the org.eclipse.swt.browser.DefaultType
variable accordingly. According to this question, this can be done by ensuring that -Dorg.eclipse.swt.browser.DefaultType=webkit
is in the eclipse.ini
file.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55556630%2feclipse-the-swt-browser-widget-could-not-be-created%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the error message and from some further research it is clear, that the SWT browser widget relies on the XULRunner
software to render HTML. As the error message states, this hasn't been ported to GTK3 (yet) and can thus not be used. Per default eclipse does start in GTK3-mode though, so that's the root problem.
An attempt to solve it could be to force eclipse into GTK2-mode (see here) but further investigation of the Eclipse FAQ shows, that from Eclipse 4.8 and onward XULRunner isn't supported at all anymore.
Therefore the option to use the SWT.MOZILLA
style for creating the browser seems to be invalid in those versions. Instead one has to focus on getting the SWT.WEBKIT
style to work. For that another visit in the FAQ reveals that
WebKitGTK 1.2.0 or newer must be in the library load path.
Therefore I went ahead and searched for the respective library and installed it (libwebkitgtk-3.0-0
in my case).
After having installed that package above SWT-snipped started just fine and after having restarted eclipse, the JavaDoc was back to full functionality.
If this doesn't work for you directly, you might have to set the org.eclipse.swt.browser.DefaultType
variable accordingly. According to this question, this can be done by ensuring that -Dorg.eclipse.swt.browser.DefaultType=webkit
is in the eclipse.ini
file.
add a comment |
From the error message and from some further research it is clear, that the SWT browser widget relies on the XULRunner
software to render HTML. As the error message states, this hasn't been ported to GTK3 (yet) and can thus not be used. Per default eclipse does start in GTK3-mode though, so that's the root problem.
An attempt to solve it could be to force eclipse into GTK2-mode (see here) but further investigation of the Eclipse FAQ shows, that from Eclipse 4.8 and onward XULRunner isn't supported at all anymore.
Therefore the option to use the SWT.MOZILLA
style for creating the browser seems to be invalid in those versions. Instead one has to focus on getting the SWT.WEBKIT
style to work. For that another visit in the FAQ reveals that
WebKitGTK 1.2.0 or newer must be in the library load path.
Therefore I went ahead and searched for the respective library and installed it (libwebkitgtk-3.0-0
in my case).
After having installed that package above SWT-snipped started just fine and after having restarted eclipse, the JavaDoc was back to full functionality.
If this doesn't work for you directly, you might have to set the org.eclipse.swt.browser.DefaultType
variable accordingly. According to this question, this can be done by ensuring that -Dorg.eclipse.swt.browser.DefaultType=webkit
is in the eclipse.ini
file.
add a comment |
From the error message and from some further research it is clear, that the SWT browser widget relies on the XULRunner
software to render HTML. As the error message states, this hasn't been ported to GTK3 (yet) and can thus not be used. Per default eclipse does start in GTK3-mode though, so that's the root problem.
An attempt to solve it could be to force eclipse into GTK2-mode (see here) but further investigation of the Eclipse FAQ shows, that from Eclipse 4.8 and onward XULRunner isn't supported at all anymore.
Therefore the option to use the SWT.MOZILLA
style for creating the browser seems to be invalid in those versions. Instead one has to focus on getting the SWT.WEBKIT
style to work. For that another visit in the FAQ reveals that
WebKitGTK 1.2.0 or newer must be in the library load path.
Therefore I went ahead and searched for the respective library and installed it (libwebkitgtk-3.0-0
in my case).
After having installed that package above SWT-snipped started just fine and after having restarted eclipse, the JavaDoc was back to full functionality.
If this doesn't work for you directly, you might have to set the org.eclipse.swt.browser.DefaultType
variable accordingly. According to this question, this can be done by ensuring that -Dorg.eclipse.swt.browser.DefaultType=webkit
is in the eclipse.ini
file.
From the error message and from some further research it is clear, that the SWT browser widget relies on the XULRunner
software to render HTML. As the error message states, this hasn't been ported to GTK3 (yet) and can thus not be used. Per default eclipse does start in GTK3-mode though, so that's the root problem.
An attempt to solve it could be to force eclipse into GTK2-mode (see here) but further investigation of the Eclipse FAQ shows, that from Eclipse 4.8 and onward XULRunner isn't supported at all anymore.
Therefore the option to use the SWT.MOZILLA
style for creating the browser seems to be invalid in those versions. Instead one has to focus on getting the SWT.WEBKIT
style to work. For that another visit in the FAQ reveals that
WebKitGTK 1.2.0 or newer must be in the library load path.
Therefore I went ahead and searched for the respective library and installed it (libwebkitgtk-3.0-0
in my case).
After having installed that package above SWT-snipped started just fine and after having restarted eclipse, the JavaDoc was back to full functionality.
If this doesn't work for you directly, you might have to set the org.eclipse.swt.browser.DefaultType
variable accordingly. According to this question, this can be done by ensuring that -Dorg.eclipse.swt.browser.DefaultType=webkit
is in the eclipse.ini
file.
answered Apr 6 at 10:36
RavenRaven
1,25111023
1,25111023
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55556630%2feclipse-the-swt-browser-widget-could-not-be-created%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Okay to whoever voted this question as OT (or is thinking about it): The problem is more or less linux-specific (it certainly is when factoring in its solution). So where else would you want to post such a question, if not here? It occurs in Linux and it is being fixed inside Linux (not inside eclipse itself). To me it is therefore exactly what this site is all about.
– Raven
Apr 6 at 13:44
@muru I wouldn't call that "general debugging" the code is only in there as it helped getting to the root of the original problem. The question that gets answered here is why eclipse won't show the JavaDoc properly when being run on Linux. So I wouldn't say that counts as debugging.
– Raven
Apr 6 at 19:11