scilab-bin crashed with SIGSEGV in scirun_()

[Krzysztof]

SciLAB does not started.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: scilab-full-bin 5.5.0~beta-1+git~20140327-1135-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic i686
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
CurrentDesktop: XFCE
Date: Sun Apr 6 21:13:57 2014
Disassembly: => 0x35: Cannot access memory at address 0x35
ExecutablePath: /usr/bin/scilab-bin
InstallationDate: Installed on 2010-12-12 (1210 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/bin/scilab-bin -f
SegvAnalysis:
 Segfault happened at: 0x35: Cannot access memory at address 0x35
 PC (0x00000035) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: scilab
StacktraceTop:
 ?? ()
 scirun_ (startupCode=startupCode@entry=0x8b12688 "exec('SCI/etc/scilab.start',-1);;", startupCode_len=33) at src/c/scirun.c:52
 realmain (no_startup_flag_l=0, initial_script=0x0, initial_script_type=SCILAB_SCRIPT, memory=8000000) at src/c/realmain.c:168
 main (argc=<optimized out>, argv=0xbfb67c54) at modules/startup/src/c/mainscic.cpp:230
Title: scilab-bin crashed with SIGSEGV in scirun_()
UpgradeStatus: Upgraded to trusty on 2014-03-19 (17 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1299628, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.