Package Details: scilab-bin 2025.1.0-1

Git Clone URL: https://aur.archlinux.org/scilab-bin.git (read-only, click to copy)
Package Base: scilab-bin
Description: a powerful computing environment for engineering and scientific applications.
Upstream URL: https://www.scilab.org
Keywords: programming scientific scilab
Licenses: GPL-2.0-or-later
Conflicts: scilab
Provides: scilab
Submitter: marcel83
Maintainer: envolution
Last Packager: envolution
Votes: 34
Popularity: 0.24
First Submitted: 2015-11-11 19:36 (UTC)
Last Updated: 2025-05-23 01:16 (UTC)

Dependencies (33)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Potomac commented on 2018-06-27 01:55 (UTC)

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

reuseman commented on 2018-03-25 08:47 (UTC)

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

eleftg commented on 2018-02-12 23:02 (UTC)

Thank you brunohcastro! I didn't know this trick :)

(I've just always run it from the command line)

brunohcastro commented on 2018-02-01 06:59 (UTC)

It's working if run from command line. Also working with Terminal=true on the scilab.desktop file. The same goes for xcos.

gnuku commented on 2018-01-08 14:23 (UTC)

Solving only partially. Now scilab opens and crashes/closes right away. Ditto for xcos

eleftg commented on 2018-01-03 23:29 (UTC) (edited on 2018-01-03 23:29 (UTC) by eleftg)

Fixed. Many thanks to curufinwe and eolianoe for their suggestions

eolianoe commented on 2018-01-03 17:36 (UTC)

@curufinwe: I can confirm that deleting the files make scilab works

# Fix bug: http://bugzilla.scilab.org/show_bug.cgi?id=15145
+  rm -f -- "${pkgdir}/opt/${_pkgname}/lib/thirdparty/libz.so"*

curufinwe commented on 2017-12-30 17:38 (UTC)

To run scilab-6.0.0 you should delete zlib* libraries from

scilab-6.0.0/lib/thirdparty

After that scilab will start normally. Information from http://bugzilla.scilab.org/show_bug.cgi?id=15145

It works for me.

grandchild commented on 2017-12-06 17:42 (UTC) (edited on 2017-12-22 15:14 (UTC) by grandchild)

If you just now want to install Scilab, no prior installation, you have to do the following:

  1. Edit the PKGBUILD: pgkver=5.5.2 and sha256sums_x86_64=("SKIP")

  2. Make sure that your default Java version is not java-8-openjdk (plotting failed for me on openjdk8): sudo archlinux-java set java-7-openjdk/jre # or java-7-openjdk or similar, check archlinux-java status to see what you have available

  3. Start Scilab with: _JAVA_OPTIONS='-Dswing.installedlafs=com.sun.java.swing.plaf.gtk.GTKLookAndFeel' /opt/scilab/bin/scilab

  4. Then edit /etc/pacman.conf to IgnorePkg = scilab-bin to avoid having to do this all again later.

eleftg commented on 2017-10-28 20:52 (UTC) (edited on 2017-10-28 20:53 (UTC) by eleftg)

As of 2017-10-28 the official binary distribution of scilab does not work. It throws a segmentation fault : bin/scilab: line 957: 31730 Segmentation fault (core dumped) "$SCILABBIN" "$@" Updates will follow once this gets fixed upstream

« First ‹ Previous 1 2 3 4 Next › Last »