Why MATLAB can not start on Ubuntu 18.04?

When I run sudo /usr/local/MATLAB/R2018a/bin/matlab, MATLAB always stay on the startup screen, and I got a matlab_crash_dump.21147-1 file in my home forder.

I attach the content here:

Would you please help me.

--------------------------------------------------------------------------------

Segmentation violation detected at Wed Mar 20 08:33:14 2019 +0800

--------------------------------------------------------------------------------

Configuration:

Crash Decoding : Disabled - No sandbox or build area path

Crash Mode : continue (default)

Default Encoding : UTF-8

Deployed : false

GNU C Library : 2.27 stable

Graphics Driver : Unknown hardware

Java Version : Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode

MATLAB Architecture : glnxa64

MATLAB Entitlement ID : 6257193

MATLAB Root : /usr/local/MATLAB/R2018a

MATLAB Version : 9.4.0.813654 (R2018a)

OpenGL : hardware

Operating System : Ubuntu 18.04 LTS

Process ID : 21147

Processor ID : x86 Family 6 Model 85 Stepping 4, GenuineIntel

Session Key : 53b14e16-999a-4f7c-837b-f4070452873d

Static TLS mitigation : Disabled: Cannot load X11

Window System : The X.Org Foundation (11906000), display :1

Fault Count: 1

Abnormal termination

Register State (from fault):

RAX = 001065b2a0b2fa50 RBX = 0000000000000001

RCX = 0000000000000002 RDX = 00007f340000007f

RSP = 00007f340cf83eb0 RBP = 0000000000000001

RSI = 0000000000000001 RDI = 00007f328a363a80

R8 = 0000000000000000 R9 = 0000000000000000

R10 = 00000000000000f0 R11 = 0000000000000206

R12 = 00007f342d3c3718 R13 = 0000000000002bce

R14 = 00007f342d3c8628 R15 = 00007f32a0b2ea70

RIP = 00007f342d01aff6 EFL = 0000000000010206

CS = 0033 FS = 0000 GS = 0000

Stack Trace (from fault):

[ 0] 0x00007f342d01aff6 /lib/x86_64-linux-gnu/libc.so.6+00274422

[ 1] 0x00007f342d01b13a /lib/x86_64-linux-gnu/libc.so.6+00274746

[ 2] 0x00007f340edd2d48 /usr/lib/x86_64-linux-gnu/libX11.so.6+00261448 _XIOError+00000088

[ 3] 0x00007f340edd059d /usr/lib/x86_64-linux-gnu/libX11.so.6+00251293 _XEventsQueued+00000125

[ 4] 0x00007f340edc21d9 /usr/lib/x86_64-linux-gnu/libX11.so.6+00192985 XEventsQueued+00000105

[ 5] 0x00007f340daf744e /usr/lib/x86_64-linux-gnu/libXt.so.6+00185422 _XtWaitForSomething+00002638

[ 6] 0x00007f340daf8265 /usr/lib/x86_64-linux-gnu/libXt.so.6+00189029 XtAppNextEvent+00000229

[ 7] 0x00007f340e122383 bin/glnxa64/libmwuix.so+00168835

[ 8] 0x00007f340e122a25 bin/glnxa64/libmwuix.so+00170533

[ 9] 0x00007f341b593e93 bin/glnxa64/libmwbridge.so+00163475

[ 10] 0x00007f341b59480c bin/glnxa64/libmwbridge.so+00165900

[ 11] 0x00007f341b59db23 bin/glnxa64/libmwbridge.so+00203555

[ 12] 0x00007f341b59e209 bin/glnxa64/libmwbridge.so+00205321

[ 13] 0x00007f341b59e81c bin/glnxa64/libmwbridge.so+00206876 _Z8mnParserv+00000620

[ 14] 0x00007f341d617bb8 bin/glnxa64/libmwmcr.so+00641976

[ 15] 0x00007f342a733e9f bin/glnxa64/libmwmlutil.so+06524575 _ZNSt13__future_base13_State_baseV29_M_do_setEPSt8functionIFSt10unique_ptrINS_12_Result_baseENS3_8_DeleterEEvEEPb+00000031

[ 16] 0x00007f342b789827 /lib/x86_64-linux-gnu/libpthread.so.0+00063527

[ 17] 0x00007f342a734126 bin/glnxa64/libmwmlutil.so+06525222 _ZSt9call_onceIMNSt13__future_base13_State_baseV2EFvPSt8functionIFSt10unique_ptrINS0_12_Result_baseENS4_8_DeleterEEvEEPbEJPS1_S9_SA_EEvRSt9once_flagOT_DpOT0_+00000102

[ 18] 0x00007f341d6179d3 bin/glnxa64/libmwmcr.so+00641491

[ 19] 0x00007f342ef6d1a2 bin/glnxa64/libmwmvm.so+03367330 _ZN14cmddistributor15PackagedTaskIIP10invokeFuncIN7mwboost8functionIFvvEEEEENS2_10shared_ptrINS2_13unique_futureIDTclfp_EEEEEERKT_+00000082

[ 20] 0x00007f342ef6d4e8 bin/glnxa64/libmwmvm.so+03368168 _ZNSt17_Function_handlerIFN7mwboost3anyEvEZN14cmddistributor15PackagedTaskIIP10createFuncINS0_8functionIFvvEEEEESt8functionIS2_ET_EUlvE_E9_M_invokeERKSt9_Any_data+00000024

[ 21] 0x00007f341dc21e6c bin/glnxa64/libmwiqm.so+00867948 _ZN7mwboost6detail8function21function_obj_invoker0ISt8functionIFNS_3anyEvEES4_E6invokeERNS1_15function_bufferE+00000028

[ 22] 0x00007f341dc2197f bin/glnxa64/libmwiqm.so+00866687 _ZN3iqm18PackagedTaskPlugin7executeEP15inWorkSpace_tagRN7mwboost10shared_ptrIN14cmddistributor17IIPCompletedEventEEE+00000447

[ 23] 0x00007f341dbffab1 bin/glnxa64/libmwiqm.so+00727729

[ 24] 0x00007f341dbe2ac8 bin/glnxa64/libmwiqm.so+00608968

[ 25] 0x00007f341dbdd8bf bin/glnxa64/libmwiqm.so+00587967

[ 26] 0x00007f342e09fa05 bin/glnxa64/libmwservices.so+03262981

[ 27] 0x00007f342e0a0ff2 bin/glnxa64/libmwservices.so+03268594

[ 28] 0x00007f342e0a18fb bin/glnxa64/libmwservices.so+03270907 _Z25svWS_ProcessPendingEventsiib+00000187

[ 29] 0x00007f341d618fc3 bin/glnxa64/libmwmcr.so+00647107

[ 30] 0x00007f341d6196a4 bin/glnxa64/libmwmcr.so+00648868

[ 31] 0x00007f341d6123f1 bin/glnxa64/libmwmcr.so+00619505

[ 32] 0x00007f342b7816db /lib/x86_64-linux-gnu/libpthread.so.0+00030427

[ 33] 0x00007f342d0f988f /lib/x86_64-linux-gnu/libc.so.6+01185935 clone+00000063

[ 34] 0x0000000000000000 <unknown-module>+00000000

[Anders Glent Buch]

In my case, I got something similar because MATLAB wasn't able to create folders in the user directory, which was only given super user rights during installation. I resolved it using the following in a terminal:

sudo chown $USER:$USER ~/.matlab/R2019b -R

Of couse, you would replace R2019b by R2018a in your case.

Answer 1

[Cam Salzberger]

Hello Ye,

This answer provides a good starting point for troubleshooting these types of issues. Beyond that, contacting MathWorks technical support is usually a good step.

My suspicion, based on the crash dump, is that you are using X11 forwarding to run MATLAB on a remote machine, but still view the window. You could try the startup option -softwareopengl, though I am unsure if that will work. I would suggest an alternative remote-access solution, or using SSH to access the machine and running MATLAB in -nodesktop mode (terminal only). MATLAB does not play well with X11 forwarding.

-Cam

[Ye Cao]

Very grateful.

Actually, I installed MATLAB locally and run it from a local shell.

Some people boil this down to the libc version. They suggect soft link the libstdc++ to MATLAB.

Is it reasonable?

[Cam Salzberger]

I haven't heard of that, or tried anything like that myself, so I really can't speak for its effectiveness. Tech support's probably the next logical step.

Just out of curiosity, if you start MATLAB without "sudo", does it have the same issue? And does it work if you try running it with the -nodesktop flag?

[Ye Cao]

I can run matlab with -nodesktop flag in a terminal.

I have another computer with Ubuntu 16.04, where Matlab works well.

If Matlab can run with GUI environment of Linux?

I installed Ubuntu 18.04 with minimal installation setting. Do you think this is the reason?