Matlab R2017b crashes on Simulink (Fedora 28)

1 view (last 30 days)
Marius Pfeffer
Marius Pfeffer on 2 Oct 2018
Commented: Orestz on 25 May 2019
I've installed Matlab R2017b on a Fedora 28 machine with Gnome. Matlab starts without a problem but when I try to start simulink it crashes:
------------------------------------------------------------------------
Segmentation violation detected at Tue Oct 2 20:22:32 2018
------------------------------------------------------------------------
Configuration:
Crash Decoding : Disabled - No sandbox or build area path
Crash Mode : continue (default)
Current Graphics Driver: Unknown software
Current Visual : 0x24 (class 4, depth 24)
Default Encoding : UTF-8
Deployed : false
GNU C Library : 2.27 stable
Host Name : f28len
MATLAB Architecture : glnxa64
MATLAB Entitlement ID: 4212000
MATLAB Root : /home/neo/MATLAB/R2017b
MATLAB Version : 9.3.0.713579 (R2017b)
OpenGL : software
Operating System : Linux 4.18.10-200.fc28.x86_64 #1 SMP Wed Sep 26 09:48:36 UTC 2018 x86_64
Processor ID : x86 Family 6 Model 60 Stepping 3, GenuineIntel
Virtual Machine : Java 1.8.0_121-b13 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
Window System : Fedora Project (11906000), display :0
Fault Count: 1
Abnormal termination:
Segmentation violation
Register State (from fault):
RAX = 00007fb600000000 RBX = 00007fb5929f9300
RCX = 0000000000000000 RDX = 0000000000000006
RSP = 00007ffd31e06810 RBP = 00007ffd31e06840
RSI = 0000000000000000 RDI = 0000000000d83a50
R8 = 0000000000000000 R9 = 00007fb64e5b5700
R10 = 00007fb677c7d010 R11 = 0000000000000206
R12 = 00007ffd31e068f0 R13 = 00007fb5929f9300
R14 = 0000000000de9850 R15 = 0000000000de97f0
RIP = 00007fb4fb96f85e EFL = 0000000000010206
CS = 0033 FS = 0000 GS = 0000
Stack Trace (from fault):
[ 0] 0x00007fb4fb96f85e /home/neo/MATLAB/R2017b/bin/glnxa64/libQt5Core.so.5+00686174 _ZN7QThread13currentThreadEv+00000014
[ 1] 0x00007fb4fbb55109 /home/neo/MATLAB/R2017b/bin/glnxa64/libQt5Core.so.5+02674953 _ZN16QCoreApplication36qt_set_current_thread_to_main_threadEv+00000009
[ 2] 0x00007fb501cc1a16 bin/glnxa64/libmwglee.so+01726998
[ 3] 0x00007fb65c2e5368 bin/glnxa64/libmwmcr.so+00582504
[ 4] 0x00007fb65c2e6714 bin/glnxa64/libmwmcr.so+00587540
[ 5] 0x00007fb65c2e6a93 bin/glnxa64/libmwmcr.so+00588435 _Z12mcr_run_mainRKN5boost9function0IiEEbb+00000243
[ 6] 0x00007fb65cf7f5a8 bin/glnxa64/libmwMVMLocal.so+00427432
[ 7] 0x00007fb67749c38d bin/glnxa64/libmwmvm.so+02507661
[ 8] 0x00007fb67749c85e bin/glnxa64/libmwmvm.so+02508894
[ 9] 0x0000000000406070 /home/neo/MATLAB/R2017b/bin/glnxa64/MATLAB+00024688
[ 10] 0x00007fb6756df11b /lib64/libc.so.6+00143643 __libc_start_main+00000235
[ 11] 0x0000000000406231 /home/neo/MATLAB/R2017b/bin/glnxa64/MATLAB+00025137
[ 12] 0x0000000000000000 <unknown-module>+00000000
If this problem is reproducible, please submit a Service Request via:
http://www.mathworks.com/support/contact_us/
A technical support engineer might contact you with further information.
Thank you for your help.
Any ideas what the problem could be?

Answers (1)

Marius Pfeffer
Marius Pfeffer on 3 Oct 2018
Had to delete libfreetype ($(matlabroot)/bin/glnxa64/) and libglib ($(matlabroot)/cefclient/sys/os/glnxa64/) to get it to work fully.
Appears to work without a problem now.

Categories

Find more on Introduction to Installation and Licensing in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!