Known Linux issues and workarounds
Because of the high number of available Linux distributions, it's not possible to guarantee a smooth experience at all times. There can be some quirks and errors that need a workaround or that need to be accepted. This site is meant to collect these issues, and everyone is invited to add their findings. If you find a new bug, please post an issue for it in our issue tracker.
The example wizard uses a built-in browser to display a preview and a description of the example. If the built-in browser is not configured for some reason, the Help will show up in your standard browser instead of the Eclipse one and the YAKINDU SCT Example Wizard will not open at all. You can easily solve this by installing libwebkitgtk. The name of this package in your distribution can differ.
- Ubuntu:
libwebkitgtk - Fedora:
webkitgtk - Arch Linux:
webkitgtk2
This is an issue that can arise when GTK3 is used - which is the default behavior. A good workaround is to tell Java to use GTK2 instead. You can do this by adding another start script in the folder where SCT is located. Create a file SCT_gtk2.sh, and put SWT_GTK3=0 ./SCT inside. Now, with a terminal in that folder, just type ./SCT_gtk2.sh instead of ./SCT.
When you're building SCT from source, you should start your parent Eclipse with GTK2 as well. Assuming your install folder is named sct-master, go to sct-master/eclipse, create the script eclipse_gtk2.sh, and put SWT_GTK3=0 ./eclipse in. In both cases, it is possible you need to do a quick chmod +x for the file allowing you to execute it.
This is a workaround for Issue #948 as well.
Especially when you're using KDE, GTK Applications can have a bad look at times. You'll need the package kde-gtk-config and breeze-gtk. After doing this, you can set up GTK to use the Breeze-Theme from your KDE settings and Eclipse should be a bit easier on the eye after a quick restart.