scilab libraries are heavily underlinked, causing segfaults on load

Bug #1299686 reported by toccata
78
This bug affects 11 people
Affects Status Importance Assigned to Milestone
scilab (Debian)
Fix Released
Unknown
scilab (Ubuntu)
Fix Released
High
Unassigned

Bug Description

5.5.0~beta-1+git~20140327-1135-1ubuntu1 doesn't launch at all with 14.04
It ends on Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: scilab 5.5.0~beta-1+git~20140327-1135-1ubuntu1
Uname: Linux 3.14.0-031400rc8-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Mar 30 09:03:45 2014
PackageArchitecture: all
SourcePackage: scilab
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
toccata (jdruel) wrote :
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for taking your time to report this issue and help making Ubuntu better.

Could you please include the full output when attempting to start scilab from the terminal?

It doesn't start on i386 either, but I get a message about missing symbols, not seg fault, so I'm trying to figure out whether this is related or if I should file a separate bug on it:
$ scilab
The native library sciconsole does not exist or cannot be found.
/usr/lib/scilab/libsciconsole.so.5.5.0: /usr/lib/scilab/libsciconsole.so.5.5.0: undefined symbol: _ZN13GiwsException22JniCallMethodExceptionD1Ev
Current java.library.path is : :/usr/lib/jni/:/usr/lib:/usr/share/scilab//../../lib/scilab/:/usr/lib/scilab/

Revision history for this message
toccata (jdruel) wrote :

Starting scilab from the terminal just gives me:
Segmentation fault (core dumped)

scilab-cli seems to work just fine: I can launch it and write a few commands.

If I launch scilab from the Kubuntu start menu (kickoff application launcher),
I notice a very short lived window which closes almost immediatly.
If I try again from the Kubuntu start menu: nothing happens.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in scilab (Ubuntu):
status: New → Confirmed
Revision history for this message
Sergio Benjamim (sergio-br2) wrote :

Here the error message is:

scilab
Error parsing gtk-icon-sizes string: ''
The native library sciaction_binding does not exist or cannot be found.
/usr/lib/scilab/libsciaction_binding.so.5.5.0: /usr/lib/scilab/libsciaction_binding.so.5.5.0: undefined symbol: _ZN13GiwsException22JniCallMethodExceptionD1Ev
java.lang.UnsatisfiedLinkError: /usr/lib/scilab/libsciaction_binding.so.5.5.0: /usr/lib/scilab/libsciaction_binding.so.5.5.0: undefined symbol: _ZN13GiwsException22JniCallMethodExceptionD1Ev
 at java.lang.ClassLoader$NativeLibrary.load(Native Method)
 at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1965)
 at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1890)
 at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1880)
 at java.lang.Runtime.loadLibrary0(Runtime.java:849)
 at java.lang.System.loadLibrary(System.java:1088)
 at org.scilab.modules.action_binding.InterpreterManagementJNI.<clinit>(Unknown Source)
 at org.scilab.modules.action_binding.InterpreterManagement.requestScilabExec(Unknown Source)
 at org.scilab.modules.xcos.Xcos$1.run(Unknown Source)
 at org.scilab.modules.core.Scilab.executeInitialHooks(Unknown Source)
Impossible d'exécuter la procédure d'initialisation. Erreur :
Exception in thread "main" java.lang.UnsatisfiedLinkError: org.scilab.modules.action_binding.InterpreterManagementJNI.requestScilabExec(Ljava/lang/String;)I
 at org.scilab.modules.action_binding.InterpreterManagementJNI.requestScilabExec(Native Method)
 at org.scilab.modules.action_binding.InterpreterManagement.requestScilabExec(Unknown Source)
 at org.scilab.modules.xcos.Xcos$1.run(Unknown Source)
 at org.scilab.modules.core.Scilab.executeInitialHooks(Unknown Source)
Segmentation fault (core dumped)

Revision history for this message
saxo_zen (serge-iovleff) wrote :

I get the same kind of problem with the following output

$ scilab
libEGL warning: failed to create a pipe screen for i965
Segmentation fault (core dumped)

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

It renders essential functionality of the package (or a dependent one) broken.

Changed in scilab (Ubuntu):
importance: Undecided → High
Revision history for this message
toccata (jdruel) wrote :

I tried to compile the 5.5-beta sources. It didn't give me any usable software. Why not stay on a more stable 5.4.1 version (specially for a LTS) ?
The 5.5 seems clearly far from finished.

Revision history for this message
Matthias Klose (doko) wrote :

I didn't request the sync, I was trying to fix the build failures in the synced version.

apparently a lot of the loadable modules are underlinked. what makes things worse is that there seem to be some circular build dependencies.

Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

I just uploaded verison 5.5.0~beta-1+git~20140406-1522-1 which fixes the issue.

Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

(uploaded in Debian) I will request the sync once it reached the mirrors

Matthias Klose (doko)
summary: - Segmentation fault (core dumped) when starting
+ scilab libraries are heavily underlinked, causing segfaults on load
Changed in scilab (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package scilab - 5.5.0-1

---------------
scilab (5.5.0-1) unstable; urgency=medium

  * Stable release (very similar to beta-1+git~20140406-1522)
  * Add back the wrongly removed depend-scicos.diff
  * Also disable ocamlopt features on mips mipsel s390x sparc

 -- Sylvestre Ledru <email address hidden> Fri, 11 Apr 2014 15:02:39 +0200

Changed in scilab (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Sergio Benjamim (sergio-br2) wrote :
Download full text (15.3 KiB)

Trying to run this new version, but the problem remains:

(gdb) run
Starting program: /usr/bin/scilab-bin -debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0x99ba8b40 (LWP 9728)]
[New Thread 0x999ffb40 (LWP 9729)]
[New Thread 0x997ffb40 (LWP 9730)]
[New Thread 0x995ffb40 (LWP 9731)]
[New Thread 0x984d1b40 (LWP 9732)]
[New Thread 0x9957eb40 (LWP 9733)]
[New Thread 0x98450b40 (LWP 9734)]
[New Thread 0x980ffb40 (LWP 9735)]
[New Thread 0x980aeb40 (LWP 9736)]
[New Thread 0x9802db40 (LWP 9737)]
[New Thread 0x97facb40 (LWP 9738)]
[New Thread 0x97f5bb40 (LWP 9739)]
[New Thread 0x96dbab40 (LWP 9740)]
[New Thread 0x96d69b40 (LWP 9741)]
[New Thread 0x96bffb40 (LWP 9742)]
[New Thread 0x96baeb40 (LWP 9743)]
[New Thread 0x968efb40 (LWP 9744)]
[New Thread 0x946ffb40 (LWP 9745)]
[New Thread 0x93efeb40 (LWP 9746)]
[New Thread 0x936fdb40 (LWP 9747)]
[New Thread 0x92efcb40 (LWP 9748)]
Error parsing gtk-icon-sizes string: ''

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x96baeb40 (LWP 9743)]
0xb1e6047f in ?? ()
(gdb) bt full
#0 0xb1e6047f in ?? ()
No symbol table info available.
#1 0xb1dd451a in ?? ()
No symbol table info available.
#2 0xb1dd451a in ?? ()
No symbol table info available.
#3 0xb1dd451a in ?? ()
No symbol table info available.
#4 0xb1dd451a in ?? ()
No symbol table info available.
#5 0xb1dd451a in ?? ()
No symbol table info available.
#6 0xb1dd4387 in ?? ()
No symbol table info available.
#7 0xb1dd4387 in ?? ()
No symbol table info available.
#8 0xb1dd45fb in ?? ()
No symbol table info available.
#9 0xb1dd451a in ?? ()
No symbol table info available.
#10 0xb1dd451a in ?? ()
No symbol table info available.
#11 0xb1dd4905 in ?? ()
No symbol table info available.
#12 0xb1dd4905 in ?? ()
No symbol table info available.
#13 0xb1dd4387 in ?? ()
No symbol table info available.
#14 0xb1dd4387 in ?? ()
No symbol table info available.
#15 0xb1dd451a in ?? ()
No symbol table info available.
#16 0xb1dd1459 in ?? ()
No symbol table info available.
#17 0xb52f6746 in JavaCalls::call_helper (result=0x96badb5c, m=0x96badb24, args=0x96badb78, __the_thread__=0x84d4400)
    at /build/buildd/openjdk-7-7u51-2.4.6/build/openjdk/hotspot/src/share/vm/runtime/javaCalls.cpp:415
        hm = {_thread = 0x84d4400, _area = 0x84c3c48, _chunk = 0x98103d40,
          _hwm = 0x98103d6c "X\003Й\330/ɬp|\361\231\b\200\\\255\210VX\255\220?\361\231(zљ\330\361o\255\030<љ\030<љ(zљ\220?\361\231\260Ȟ\232\220?\361\231\220?\361\231\260Ȟ\232\350\070\361\231\220?\361\231\210VX\255\220?\361\231\260Ȟ\232\370\256?\232\060\301\236\232\260Ȟ\232\210VX\255\210VX\255\260Ȟ\232\060\301\236\232\260Ȟ\232\210VX\255\210VX\255\260Ȟ\232\070\223\236\232P~\236\232\060\rЙ\260Ȟ\232\070\223\236\232\240\276\236\232\250Ş\232\030Ş\232\bĞ\232\220Ğ\232\350Ǟ\232P\224\236\232\220\233\236\232\060\244\236\232\070\273\236\232",
          _max = 0x98104134 "\375\003", _size_in_bytes = 1004, _previous_handle_mark = 0x96bae084}
        link = {<StackObj> = {<No data fields>}, _thread = 0x84d4400, _handles = 0x84d49e0, _callee_method = 0x9a387a98,
          _receiver = 0xaca0b9e0, _anchor = {_last_Ja...

Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

No, it does not. The OpenJDK triggers segfault on start up on purpose:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2011-March/003981.html

Since Scilab is start a Java VM.

Julian Taylor (jtaylor)
Changed in scilab (Ubuntu):
status: Fix Released → New
Revision history for this message
Julian Taylor (jtaylor) wrote :

just running scilab leads to:
$ scilab
Cannot find /usr/lib/jvm/java-6-openjdk//bin/java

java-6 is gone in 14.04

maybe its because scilab-bin is underlinked:

$ ldd /usr/bin/scilab-bin 2>&1 | grep "not "
 libjava.so => not found
 libverify.so => not found
 libjvm.so => not found
 libjava.so => not found
 libverify.so => not found
 libjvm.so => not found
 libjava.so => not found
 libverify.so => not found
 libjvm.so => not found

possible workaround for 64 bit:
SCI=/usr/share/scilab/ LD_LIBRARY_PATH=/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/server/ /usr/bin/scilab-bin

Revision history for this message
Julian Taylor (jtaylor) wrote :

simpler workaround:
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/ scilab

Revision history for this message
Julian Taylor (jtaylor) wrote :

please forget what I said, I had a wrong JAVA_HOME set in my .bashrc I did not know about.
so the underlinking is fixed and I also can't reproduce the core dump on startup.

Revision history for this message
Sergio Benjamim (sergio-br2) wrote :

Me either, it seems it is fixed (well, sometimes scilab crashes when launch, but now it's a few times).

Julian Taylor (jtaylor)
Changed in scilab (Ubuntu):
status: New → Fix Released
Revision history for this message
Tobias Zawada (tobias.zawada) wrote :

Tried scilab in Ubuntu 14.04 (up to date on June, 2nd 2014) with standard installation. Got a solid gray window instead of the gui.
Typing in "quit();" followed by return worked with the expected result.

Installed java-6-openjdk-i386 after reading this thread and set

export JAVA_HOME=/usr/lib/jvm/java-6-openjdk-i386/

Now, scilab works as expected.

Revision history for this message
Norbert (nrbrtx) wrote :

I'm sorry if this is not correct place to ask questions or write comments, but I have "Segmentation fault" with latest Git-version of Scilab.

I'm on Ubuntu 12.04.5 amd64 with Nvidia driver (nvidia-331-updates: 331.113-0ubuntu0.0.0.3),
JAVA_HOME=/usr/lib/jvm/java-6-oracle.
I downloaded Git YaSP build of Scilab (scilab-branch-YaSp-1411733280.bin.linux-x86_64.tar.gz) and it crashes with "Segmentation fault".
Dear Sylvestre, how I can debug this issue?

The same version on Ubuntu 12.04.5 with integrated intel graphics works correctly.

Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

You should report a bug upstream.
http://bugzilla.scilab.org/

Changed in scilab (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.