Arch Linux User Repository

Fixed missing fonts in the UI by using system's java, not ideal but the best approach I could find (the other one is to change Scilab's default Look and Feel settings). Also updated so it no longer runs on the terminal.

As for the MESA_GL errors, that is not Scilab's fault, the Intel Media Driver is not properly supported by jogl (also happens with other packages such as Matlab) so there are two options:

• Running with MESA_GL_VERSION_OVERRIDE=3.0

• Installing the i965 driver and running with MESA_LOADER_DRIVER_OVERRIDE=i965

Fixed missing fonts in the UI by using system's java, not ideal but the best approach I could find (the other one is to change Scilab's default Look and Feel settings). Also updated so it no longer runs on the terminal.

As for the MESA_GL errors, that is not Scilab's fault, the Intel Media Driver is not properly supported by jogl (also happens with other packages such as Matlab) so there are two options:

• Running with MESA_GL_VERSION_OVERRIDE=3.0

• Installing the i965 driver and running with MESA_LOADER_DRIVER_OVERRIDE=i965

Instead of disabling the HW support: Adding MESA_GL_VERSION_OVERRIDE=3.0 to the .desktop file fixes the error of graphic windows not displaying any graphs for me.

Adding LIBGL_ALWAYS_SOFTWARE=1 to the .desktop file fixes the error of graphic windows not displaying any graphs for me.

I took this fix from the scilab package on the AUR

scilab-bin: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Installing ncurses5-compat-libs solves it. Please add it as a dependency.

@eleftg, Scilab CLI and Scilab advanced CLI behave atypically: when I type something and press any arrow keys, or backspace, the console freezes and I need to kill the process. I reinstalled the package, but the same behaviour occurs.

Scilab, in graphical interface, works as expected.

Hi, in my case Scilab 6.0.2 no longer needs to run in the terminal to work (Plasma, linux-lts, ATI gpu).

I have update the PKGBUILB to the newer version and it works perfectly, so @eleftg can you update it on AUR, please? This is the pastebin page: https://pastebin.com/B8iF43Nk

@eleftg, any updates on the new pkgbuild? It's been quite a while since the new version released.

scilab 6 has a bug related to jogl jar library, if mesa version is >= 17.2 then scilab will be unable to use graphic hardware acceleration, no graph plotting,

http://forum.jogamp.org/Mesa-17-2-0-renderer-driver-name-change-error-causes-GLProfile-not-mapped-initialization-error-td4038176.html

in the console we can read these error logs : javax.media.opengl.GLException: X11GLXDrawableFactory - Could not initialize shared resources for :0 at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:317) at jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:295) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:625) at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:539) at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:293) ... 2 more

the solution is to build scilab with a beta version of jogl (2.3.3), or to disable gpu hardware acceleration :

export LIBGL_ALWAYS_SOFTWARE=1

How can I fix this: "The theme engine could not be found in module_path: «adwaita»"