Ask Your Question
1

Matlab doesn't startup on Fedora (Trial Version)

asked 2018-09-17 17:29:20 -0600

andrewnaguib gravatar image

The environment is:

Fedora 27
Awesome WM (tried it on GNOME desktop environment too)
Running it through the symbolic link (adds nothing but just saying).

I have followed the installation guide provided with the Matlab installation files. However, whenever I try to launch it through the terminal, nothing happens, it does not even show error. The only thing that happens (and is not understood to me) is generating a folder that is called:

"jetty-0.0.0.0-32415-laisserverimpl.jar-_-any-"

I have tried several solutions such as running the executable with different parameters: -nodesktop, -nojvm, or -nodisplay, but still cannot trace what is happening.

There is nothing really which I can search for or debug into.

edit retag flag offensive close merge delete

Comments

Which version are you trying to run? R2018b?

bob323 gravatar imagebob323 ( 2018-09-21 09:20:35 -0600 )edit

4 Answers

Sort by ยป oldest newest most voted
0

answered 2018-09-18 09:13:08 -0600

ed209 gravatar image

Being closed source and commercial, you should ask directly Matlab for support as others explained to you. I would suggest to install Octave GNU and work with that software instead. You could run the same programs running under Matlab.

edit flag offensive delete link more

Comments

I believe that is a solution. However, I have to use Matlab I am working on a research to examine its runtime behavior.

andrewnaguib gravatar imageandrewnaguib ( 2018-09-19 14:46:02 -0600 )edit
0

answered 2018-09-18 04:42:35 -0600

genodeftest gravatar image

As Matlab is closed source software, there is not very much we can do. If the following tips here do not help, please contact Matlab support. You are paying them so you can expect a working piece of software, right?

Some ideas:

  1. See https://uk.mathworks.com/matlabcentra... but please do NOT run your system with SELinux disabled permanently.
  2. Run Matlab within strace and have a look what Matlab did right before it crashed/exited. See man strace for many useful details, e.g. tracing child processes and filtering specific syscalls like strace -e trace=file to trace access to the filesystem.
  3. Find a logfile, either from the documentation or strace output.
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-09-17 17:29:20 -0600

Seen: 50 times

Last updated: Sep 18