From ArchWiki
(Redirected from Matlab)

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: unnecessarily verbose, sometimes written in in first person (Discuss in Talk:MATLAB)

From the official website:

MATLAB is a programming and numeric computing platform used by millions of engineers and scientists to analyze data, develop algorithms, and create models.


MATLAB is proprietary software produced by The MathWorks and requires a license to obtain, install, and activate. New versions of MATLAB are released twice a year, release names are composed of R, the year of the release and a or b. Since R2012b MATLAB has only been available for 64-bit Linux. Arch Linux is not officially supported. [1]


A complete copy of the MATLAB software must be obtained before it can be installed. The MATLAB software is available to licenses holders on both a DVD and through the The MathWorks website. In addition to the software a file installation key is required for installation. It is possible to install MATLAB either with the matlabAUR package or from the MATLAB installation software directly. The advantage of the matlabAUR package is that it manages dependencies and some of the nuances of the installation process while installing directly from the MATLAB installation software can be done by regular users to their home directories and works for any release of MATLAB (the matlabAUR package only works for releases including and after R2010b).

Installing from the MATLAB installation software

The MATLAB installation software is self contained and does not require any additional packages to install in silent mode. To install with the GUI a working Xorg graphical display is necessary. Wayland is not currently supported yet, at least not for the GUI; however, plotting seems to work. The installation is handled by the install script. You can run the script as root to install MATLAB system-wide or your user to install it only for you. On version R2020 the normal install script may not work, however, the legacy install script ISO-DIR/bin/glnxa64/install_unix_legacy does work [2].

MATLAB 2016a and earlier is not compatible with ncurses 6, so you must install the ncurses5-compat-libsAUR package. See #Segmentation fault on startup for more info.

During the installation, you are asked if you want symlinks to be created. If you did not choose to do so, you can now manually create a symlink in /usr/local/bin to make it easier to launch in terminal:

# ln -s /{MATLAB}/bin/matlab /usr/local/bin

Or you could add MATLAB install path to PATH environment variable.

Desktop entry

Optionally create a desktop entry. The MIME type of MATLAB files is text/x-matlab.

Start matlab with:

  • -desktop to run Matlab without a terminal.
  • -nosplash to prevent the splash screen from showing up.

In order for icons to appear correctly StartupWMClass needs to be set in the desktop entry. To find it out start MATLAB, run xprop | grep WM_CLASS and select the MATLAB window.

Example desktop entry (replace R2019a with your MATLAB version):

[Desktop Entry]
Exec=/usr/local/MATLAB/R2019a/bin/matlab -desktop
Comment=Scientific computing environment

If one need to set environment variable, one could prepend env in Exec, for example, to system's libfreetype:

Exec=env LD_PRELOAD=/usr/lib/ matlab

One might want to use the system's libstdc++.

Installing from the AUR package

The matlabAUR package is designed to allow MATLAB to be integrated into and managed by Arch. Note however, that the package does not contain the installation files, and you are expected to place them in the cloned package folder yourself. It can be problematic to build the package using AUR helpers, so you are expected to do so manually. You can obtain the actual MATLAB software using the installer from the MathWorks website.


The EULA for the proprietary MATLAB software is restrictive and it prohibits distribution and modification of the installation files. The installation method described in this section should only be performed on the system on which the software is going to be installed and the package should be deleted from the installation location and the pacman cache following installation. Redistributing the built package is a violation of the MATLAB EULA.

  • Clone the matlabAUR package and cd into it.
  • Download the zip file containing the MATLAB installer from MathWorks into the current directory. Extract the zip to the matlab subdirectory (replace the XXXXX with your release version):
$ bsdtar xC matlab -f
  • Run the extracted installer with:
$ ./matlab/install
  • The installer gives you a choice of either installing the software now or only downloading selected modules. Choose the second option.
  • The installer will give you an option to change the download path. You might want to change it to something temporary (like /tmp if you have big enough ram disk) as you will soon move the contents to a different location.
  • Wait for the download to finish and close the installer. Merge the downloaded archives into the extracted matlab subdirectory (replace YYYY_MM_DD_HH_MM_SS with your release code):
$ rsync -a /selected/download/folder/YYYY_MM_DD_HH_MM_SS/archives matlab
  • Then package the directory into a tarball:
$ tar -cvf matlab.tar matlab
  • Download your licence: Go to your MathWorks account and click on the licence number you want to use. Then, go to the Install and activate tab and select Activate to retrieve licence File. Follow the instructions and download the licence file needed for the installation. Name the file matlab.lic and place it in the AUR package directory. There will also be a File Installation Key (FIK) visible on the MathWorks website. Copy-paste it in a new file named matlab.fik and save it next to PKGBUILD just like you did with the matlab.lic.
  • Now, you will create a pacman package. You can customize the modules you want the package to contain by modifying the PKGBUILD or leave it at default:
# Limit products to lower size, set this to true to do a partial install
# Example list of products for a partial install; check for details
  #---MATLAB Product Family---#
  "Curve_Fitting_Toolbox"           # Math and Optimization
  "Database_Toolbox"              # Database Access and Reporting
  "MATLAB_Coder"                # Code Generation
  "MATLAB_Compiler"               # Application Deployement
  "Parallel_Computing_Toolbox"        # Parallel computing
  "Statistics_and_Machine_Learning_Toolbox"   # AI, Data Science, Statistics
  #---Application Products---#
  "Bioinformatics_Toolbox"          # Computational Biology
  "Image_Processing_Toolbox"          # Image Processing and Computer Vision
  "Signal_Processing_Toolbox"         # Signal Processing
  • Finally, use makepkg command to build and install the package:
$ makepkg -sri



The MATLAB software is bundled with a JVM and therefore it is not necessary to install Java. The JVM version supported by MATLAB is listed in System Requirements & Platform Availability or simply type version -java in MATLAB. One could set the MATLAB_JAVA environment variable to use custom JVM, for example, to specify the jre8-openjdk JRE, launch MATLAB with:

$ env MATLAB_JAVA=/usr/lib/jvm/java-8-openjdk/jre matlab

OpenGL acceleration

MATLAB can take advantage of hardware based 2D and 3D OpenGL acceleration. Support for hardware acceleration needs to be configured outside of MATLAB. Appropriate video drivers need to be installed along with the OpenGL utility library glu package. If X11 forwarding is being used, the video drivers need to be installed on both the client and server. To check if MATLAB is making use of hardware based OpenGL acceleration run:

$ matlab -nodesktop -nosplash -r "opengl info; exit" | grep Software

If "software rendering" is not "false", then there is a problem with your hardware acceleration. If this is the case make sure OpenGL is configured correctly on the system. This can be done with the glxinfo program from the mesa-utils package:

$ glxinfo | grep "direct rendering"

If "direct rendering" is not "yes", then there is likely a problem with your system configuration.

If glxinfo works but not matlab, you can try to run:

$ export LD_PRELOAD=/usr/lib/; export LD_LIBRARY_PATH=/usr/lib/xorg/modules/dri/; matlab -nodesktop -nosplash -r "opengl info; exit" | grep Software

If it works, you can edit Matlab launcher script to add:

export LD_PRELOAD=/usr/lib/
export LD_LIBRARY_PATH=/usr/lib/xorg/modules/dri/

If you experience a low-level graphics error, you can use a software implementation of OpenGL or use an older driver. According to this entry in the ArchWiki, in Mesa 20.0 the new Iris driver was promoted to be the default for Gen8+. You may disable it and revert to use the old i965 driver by setting the MESA_LOADER_DRIVER_OVERRIDE=i965 environment variable before starting Matlab or any OpenGL application. Alternatively, you can run Matlab with the following command:

$ env MESA_LOADER_DRIVER_OVERRIDE=i965 matlab -desktop

If it works, you can edit the Matlab launcher script to add:



To confirm that MATLAB is able to use the default soundcard to present sounds run:

$ matlab -nodesktop -nosplash -r "load handel; sound(y, Fs); pause(length(y)/Fs); exit" > /dev/null

This should play an except from Handel's "Hallelujah Chorus." If this fails make sure ALSA is properly configured. This can be done with the speaker-test program from the alsa-utils package from the official repositories:

$ speaker-test

If you do not hear anything, then there is likely a problem with your system configuration.

GPU computing

MATLAB can take advantage of CUDA enabled GPUs to speed up applications. In order to take advantage of a supported GPU install the nvidia, nvidia-utils, ocl-icd, opencl-nvidia, and cuda packages from the official repositories. To check if MATLAB is able to utilize the GPU run:

$ matlab -nodesktop -nosplash -r "x=rand(10, 'single'); g=gpuArray(x); Success=isequal(gather(g), x), exit"  | sed -ne '/Success =/,$p'

Install supported compilers

In order to access the full functionality of MATLAB (e.g., to use Simulink, Builder JA, and MEX-file compilation), supported versions of the gcc, g++, gfortran, and jdk compilers must be installed. Details about the supported compilers for the current release and previous releases are available online. Many of the supported gcc, g++, jdk compiler versions for past MATLAB releases are available from the AUR (e.g., gcc43AUR, gcc44AUR, gcc47AUR, gcc49AURand jdk6AUR), while past versions of the gfortran compilers are not packaged.

To use previous versions of the the gcc, g++, and gfortran compilers with MEX files, edit ${MATLAB}/bin/ and replace all occurrences of CC='gcc' with CC='gcc-4.X', CXX='g++' with CXX='g++-4.X', and FC='gfortran' with FC='gfortran-4.X', where X is the compiler version appropriate for the particular MATLAB release.

Note: Newer versions of Matlab (at least 2017a) does not seem to respect the ${MATLAB}/bin/ customization. Instead it uses ${MATLAB}/bin/glnxa64/mexopts/LANG_glnxa64.xml file.
Note: Though, it is no officially supported, one could still use higher version of compiler, and ignore the warnings.

Help browser

The help browser uses valuable slots in the dynamic thread vector and causes competition with core functionality provided by libraries like the BLAS that also depend on the dynamic thread vector. The help browser can be configured to use fewer slots in the dynamic thread vector with

>> webutils.htmlrenderer('basic');

This is a persistent change and to reverse it use

>> webutils.htmlrenderer('default');

Garbled Interface

export J2D_D3D=false
export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk/jre

Serial port access

To successfully connect to any serial port, MATLAB expects to have write access directly to /var/lock which is not allowed on Arch Linux for security reasons. Instead of allowing this access just for MATLAB, you can work around this problem by redirecting device locking using lockdev-redirectAUR. All you have to do is executing MATLAB like this:

# lockdev-redirect /{MATLAB}/bin/matlab

If you have created a .desktop file as shortcut to MATLAB, then add "lockdev-redirect" as a prefix to your "Exec=" entry.

HiDPI and 4k



Warning: Initializing MATLAB Graphics failed

This error seems to happen on multi-monitor setups, see this forum post.

Blackscreen in help browser and livescripts

In order to use help browser and livescripts install libselinuxAUR.

Static TLS errors

MATLAB has a number of libraries that have been compiled with static thread local storage (TLS) including the help browser doc and the BLAS libraries. For example,

>> doc('help');
>> ones(10)*randn(10);
Error using  * 
BLAS loading error:
dlopen: cannot load any more object with static TLS

is related to the bugs:

A more general solution of recompiling glibc has also been suggested. [3]

MATLAB crashes when displaying graphics

To identify this error, start MATLAB with

LIBGL_DEBUG=verbose matlab

from the terminal and try to collect OpenGL information with opengl info from the MATLAB command prompt. If it crashes again and there is an output line like

libGL error: dlopen /usr/lib/xorg/modules/dri/ failed 
version `GLIBCXX_3.4.15' not found (required by /usr/lib/xorg/modules/dri/

then the problem is that MATLAB uses its own GNU C++ library, which is an older version than the up-to-date version on your Archlinux system. Make MATLAB use the current C++ library for your system by

cd /usr/local/MATLAB/R(your release)/sys/os/glnxa64
sudo unlink
sudo ln -s /usr/lib/

If MATLAB still crashes or corrupts graphics (during startup or when plotting), make sure Java's 2D OpenGL rendering is disabled. The environment variable _JAVA_OPTIONS should not contain -Dsun.java2d.opengl=true.

Blank/grey UI when using WM (non-reparenting window manager)

This is a common issue in a number of window managers. (DWM, Awesome, bspwm) Java does not play well with these window managers. There are two methods.

First try setting the environment variable by running


If Matlab works afterwards, export the variable in your .xinitrc.

If it does not resolve, you have to fool Java into thinking the WM is named LG3D. (It is an old, depreciated WM that Java applications ironically support) Clean the previous environment variable, install the wmname utility, and run.

wmname LG3D

Try running Matlab. If it works, put the fix in your starting script. (.xinitrc, bspwmrc and similar should be OK) Do note that other applications (such as neofetch, or tdrop) will think your WM is named LG3D, so you will have to configure them accordingly. Another solution is to run the command only before launching Matlab, and fixing the name after you are done with Matlab.

If it does not work, try the combination of both. (The second line works in bspwm) If it still does not work, try googling similar issues with java in general.

Garbled or invisible text

Set the environment variable J2D_D3D to false[4].

In newer versions of MATLAB (R2015b) [5] this also requires setting MATLAB_JAVA to something openjdk based. Example:

export J2D_D3D=false
./bin/glnxa64/install_unix -javadir /usr/lib/jvm/java-7-openjdk/jre

Corrupted text and fonts in menus and fields

If you notice that the menus or the input fields are corrupted or not appearing correctly then you can try to activate the "Use antialiasing to smooth desktop fonts" option in Matlab preferences, it seems to solve the problem. Go to Preferences -> Matlab -> Fonts and activate it. You will need to restart Matlab in order to take affect.

Installation dependencies missing

Matlab might complain that it cannot find a package. Look at the package name and install it with Pacman, or in the case of x86_64 there are some libraries only in AUR. matlabAUR and matlab-dummyAUR packages contain a list of up-to-date dependencies for the newest Matlab version.

If you get the following error when running the install script:

terminate called after throwing an instance of 'std::runtime_error'
  what():  Unable to launch the MATLABWindow application

this is solved by installing libselinuxAUR from the AUR.

Installation error: archive is not a ZIP archive

During the installation you can get:

The following error was detected while installing package_name: archive is not a ZIP archive 
Would you like to retry installing package_name? If you press No, the installer will exit without completing the installation. More information can be found at /tmp/mathworks_root.log

Matlab downloads all packages to /tmp/ directory which resides in RAM and is maximum size of half of available memory. In this case it is not enough for installation files and Matlab 2019a installer will warn you about this. If it did not, or if you ignored the warning, you will have got the above error.

You can either resize tmpfs (3,5 GB is not enough, 6 GB works), or remove packages from base install and add them later with built-in Matlab add-on installer.

Install-time library errors

  • Make sure that the symlink bin/glnx64/ is pointing to the correct version of (which is also in the same directory and has numbers where 'xx' is). By default, it may be pointing to an older (and nonexistent) version (different value for 'xx').
  • Make sure the device you are installing from is not mounted as noexec
  • If you downloaded the files from Mathworks' website, make sure they are not on an NTFS or FAT partition, because that can mess up the symlinks. Ext4 or Ext3 should work.

Resolving start warnings/errors

  • Even if all needed libraries are installed, Matlab when starting can still report some missing libraries. This is resolved by symbolic linking of needed libraries to directories that Matlab checks at start-up. For example, if Matlab triggers error/warning about missing /lib64/ library, this can be resolved by:
# ln -s /lib/ /lib64
  • Matlab R2011b with an up-to-date Arch Linux (as of March 12, 2012) fails on startup with the familiar "Failure loading desktop class." A solution is to point Matlab to the system JVM (confirmed to work with the jdk7-openjdk[broken link: package not found] package):
export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk/jre
  • Matlab R2017b with an up-to-date Arch Linux (as of September 30, 2017) fails on startup with the familiar "Failure loading desktop class." A solution is to install outdated versions of the libraries in the packages cairo (1.14.10 works) and harfbuzz (1.4.6 works) to a local directory and add them to the LD_LIBRARY_PATH for matlab (See also: [6]):
LD_LIBRARY_PATH="/opt/matlab/outdatedLibraries/:$LD_LIBRARY_PATH" /opt/matlab/R2017b/bin/matlab

Segmentation fault on startup

If Matlab (R2016a or earlier) stops working after upgrading ncurses to v6.x, install the ncurses5-compat-libsAUR package. See BBS#202575.

In newer versions (e.g. R2017b), the issue could also be due to a font display failing to load. Try moving the font display file in $MATLAB/bin/glnxa64/ to an 'exclude' directory; see BBS#231299.

ncurses compatibility layer is not required anymore for R2018a.

Hangs on rendering or exiting with Intel graphics

Some users have reported issues with DRI3 enabled on Intel Graphics chips. A possible workaround is to disable DRI3 and run MATLAB with hardware rendering on DRI2; to do so, launch MATLAB with the environment variable LIBGL_DRI3_DISABLE set to 1:


If the previous workaround does not work, the issue can be circumvented by selecting software rendering with the MATLAB command (beware, performance may be very poor when doing e.g. big or complex 3D plots):


See [7] and [8] for more.

Addon manager not working

This section is relevant for both R2017b and R2018a.

Addon manager requires the libselinuxAUR package to work.

Since upgrade from pango-1.40.5 to pango-1.40.6, the MATLABWindow application (responsible for Add-On Manager, Simulation Data Inspector and perhaps something else) cannot be started. FS#54257 A workaround is to point MATLAB shipping glib libraries to those glib libraries from your system. There are 5 of those libraries in matlabroot/R2017b/cefclient/sys/os/glnxa64, namely, as of R2017b:

Make it so that these symlinks are pointing to your system glib libraries instead of versions located in matlabroot/R2017b/cefclient/sys/os/glnxa64. On a standard arch install the local files reside in /usr/lib/.

Do not forget to update the *.0 links as well.

Relinking of "" is also necessary to open these interfaces. This is found in matlabroot/R2017b/bin/glnxa64/.

If the window opens but is blank, consider switching the html renderer to: " webutils.htmlrenderer('basic');" as described in #Help browser.

LiveScript errors

If you get the error when attempting to load or create a LiveScript:

 Viewing matlab live script files is not currently supported by this operating system configuration
  • It could be because of broken symlinks of libgcrypt and other dependencies, after system updates. On the first start of the Live Editor the components are extracted and these libary symlinks are created (if not existing).

A solution is to simply delete the whole folder containing the broken symlinks and the extracted components, which are in the installation directory (represented by $MATLABROOT) under:


Or if the installation directory is not user writable in:


Matlab will then regenerate the contents on the next Live Editor start.

A better option is to replace libgcrypt symlink in this extraction directory with a less precise one. For example, after extraction, this link to /lib64/ is created. Replace it with e.g. /lib64/

Matlab R2020 does not contain a chromium directory anymore. Relinking the library file with the system file can resolve the issue. It is located in:

  • Also the steps in #Addon manager not working may resolve the issue.
  • It can also happen due to missing gconf package. Make sure gconfAUR is installed.
  • If the above does not help, execute in the command window
>> com.mathworks.mde.liveeditor.widget.rtc.CachedLightweightBrowserFactory.createLightweightBrowser()

to get a more detailed error message.

  • A debugging console can be opened with
>> com.mathworks.mde.webbrowser.HtmlPanelDebugConsole.invoke;

Using webcam/video device

Make sure the correct support package addons are installed (webcam or OS Generic Video Interface for example). If running matlab as a user, make sure your user has write permissions to wherever the support packages are being downloaded and installed.

At least Matlab 2016b does not recognize webcams or imaq adapters correctly without gstreamer0.10. The gstreamer0.10 can be found in the aur and installed as a work around.

Since MATLAB R2017a, Image Acqusition Toolbox is using GStreamer library version 1.0. It previously used version 0.10.

In general, USB Webcam Support Package does a better job working with UVC and built-in cameras than OS Generic Video Interface Support Package.

Warning: As of 2018-08-15 updating gst from 1.14.0 to 1.14.2 breaks video device operation (MATLAB does not see the video device anymore). Downgrading fixes this.

MATLAB hangs for several minutes when closing Help Browser

Since upgrade of glibc from 2.24 to 2.25, MATLAB (at least R2017a) hangs when closing Help Browser. The issue is related to the particular version of jxbrowser-chromium shipped with MATLAB. This issue is still present with glibc 2.26 and MATLAB R2017b and R2018a.

To fix this issue, download the latest jxbrowser and replace the following jars from MATLAB:


MATLAB should automatically unpack those jars into matlabroot/sys/jxbrowser-chromium/glnxa64/chromium when first opening Help Browser. Remove matlabroot/sys/jxbrowser-chromium/glnxa64/chromium directory to make sure MATLAB uses the latest jxbrowser.

Unfortunately, this workaround does not work in R2017b anymore. Going deeper into investigation of this issue, it is related to a crash of one of jxbrowser-chromium processes. The parent process of jxbrowser-chromium then sits there and waits for response from a process that is already dead. This causes MATLAB main window to freeze. You can easily unfreeze MATLAB by manually killing all leftover jxbrowser-chromium processes.

I have come up with this simple script that uses inotify and waits for user to close Help browser in MATLAB. It triggers when user closes Help browser and sends kill signal to all leftover jxbrowser-chromium processes:


if [ -z "$1" ]; then

CMD="inotifywait -m -e CLOSE $JXPATH/resources.pak"

#Exit if the daemon is already active
if ! pgrep -f "$CMD" > /dev/null; then
	#Wait for user to close Help Browser, then killall leftover jxbrowser processes
	$CMD |
	while read line
		killall "$JXPATH/jxbrowser-chromium"

I run this script as part of my MATLAB start script like that:

~/bin/ R2017b &

To make sure that this background job is killed when I exit MATLAB, I use this in the beginning of MATLAB start script:

trap "trap - SIGTERM && kill -- -$$" SIGINT SIGTERM EXIT

Some dropdown menus cannot be selected

In some interfaces - such as Simulation Data Inspector or Simulink Test Manager - nothing happens when choosing an item in dropdown menu (for example, when trying to change a number of subplots in Simulation Data Inspector). To work around this issue, hold down the Shift key while clicking the item in dropdown menu.

Not starting - licensing error

In case MATLAB will not start from a desktop environment by the call of its desktop file one should see the output as you start it from the terminal.

For a Licensing error such as:

# matlab
MATLAB is selecting SOFTWARE OPENGL rendering.
License checkout failed.
License Manager Error -9
This error may occur when: 
-The hostid of this computer does not match the hostid in the license file. 
-A Designated Computer installation is in use by another user. 
If no other user is currently running MATLAB, you may need to activate.

Troubleshoot this issue by visiting:

Diagnostic Information:
Feature: MATLAB 
License path: /home/<USER>/.matlab/R2017a_licenses/license_<NUM>_R2017a.lic:/home/<USER>/.matlab/R2017a_licenses/lice
Licensing error: -9,57.

A re-activation might solve the problem.

/usr/local/MATLAB/R2017a/bin/ -javadir /usr/lib/jvm/java-8-openjdk/jre/

MATLAB crashes with "Failure loading desktop class" on startup

In case MATLAB will not start and starting it from command line gives you the following error:

$ matlab
Fatal Internal Error: Internal Error: Failure occurs during desktop startup. Details: Failure loading desktop class.

and you have the option set in your _JAVA_OPTIONS environment variable, start MATLAB with

$ _JAVA_OPTIONS= matlab

If this works, add the line


to your MATLAB launcher script. Optionally re-add other Java options.

Unable to type in text fields of interfaces based on MATLABWindow

Since R2018a, it is not possible to type text in interfaces based on MATLABWindow - like Signal Editor, Add-Ons Explorer and others. MATLABWindow and MATLAB's webwindow infrastructure is based on Chromium Embedded Framework, and it looks like a known and long standing bug:

One possible workaround is to switch focus from the MATLABWindow to another window and then switch back - so that you can type.

To elaborate more on this workaround (since the problem is still there in R2018b), here is what i did in my Openbox config (note that the A-Middle keybinding already exist in default config):

    <mousebind button="A-Middle" action="Press">
       <action name="Unfocus"/>
       <action name="Focus"/>

Now, whenever it is not possible to type in a text field, I press Alt+Mouse middle mouse and then I can type again.

This problem is critical during installation. After one clicks some elements in the installation window, he will not be able to type into any textbox anymore and switching between windows does not always work. To circumvent the issue, one shall only use key-press, instead of mouse click during installation. MATLAB installer has a poor support on Wayland, one may also consider using other WM instead during installation.

Installer crashes with "Unable to launch the MATLABWindow application"

In MATLAB version R2020a Update 5 (and possibly older), the installer crashes before the splash in shown.

$ ./install 
 terminate called after throwing an instance of 'std::runtime_error'
   what():  Unable to launch the MATLABWindow application
 Aborted (core dumped)

The problem is solved by removing (or hiding) the libgl* libraries of the MATLAB installer, as suggested for an older issue [9]

$ cd matlab_R2020a_glnxa64/cefclient/sys/os/glnxa64/
$ mkdir exclude
$ mv* exclude/

Add-on manager does not start in R2020a

In MATLAB version R2020a Update 5 (and possibly older), the Add-on manager does not start. Instead, the following error is shown

 Error using matlab.internal.cef.webwindow (line 385)
 MATLABWindow application failed to launch. Unable to launch the MATLABWindow application
 Error in matlab.internal.webwindow/createImplementation (line 288)
                 implObj = matlab.internal.cef.webwindow(varargin{:});
 Error in matlab.internal.webwindow (line 144)
             obj.impl = obj.createImplementation(varargin{:});
 Error in matlab.internal.addons.AddOnsWindow/launch (line 51)
                 obj.webwindow = matlab.internal.webwindow(char(url), obj.debugPort, obj.normalWindowPosition);
 Error in matlab.internal.addons.Explorer/loadUrlForNavigateToMessage (line 125)
                 obj.addOnsWindowInstance.launch(url, obj.windowStateUtil.getExplorerWindowMaximizedSetting);
 Error in matlab.internal.addons.Explorer/show (line 56)
 Error in matlab.internal.addons.launchers.showExplorer (line 128);

The problem is solved by removing (or hiding) the libgl* and libgio* libraries of MATLAB, as suggested for an older issue [10]

$ cd {MATLAB INSALLATION FOLDER}/cefclient/sys/os/glnxa64/
$ mkdir exclude
$ mv** exclude/

Cannot verify university login during installation

For total headcount license users, MATLAB will pop-up a window asking the user to login with his credentials in a web browser. However, if run with sudo, most browsers (especially chromium) will not run. To circumvent this problem, one shall 'active the computer' through MATLAB's website using a browser by a normal user. See this issue

Running installer as root does not launch the GUI

If you run the installer as root and the GUI does not appear (but does appear without launching as root), try allowing the root user to access the X Server by running the following command and running the installer again:

$ xhost +SI:localuser:root

Otherwise, install MATLAB as a local user. See this support answer.

MATLAB crashes when opening Simulink

When running from terminal the error message is:

Inconsistency detected by ../elf/dl-tls.c: 597: _dl_allocate_tls_init: Assertion `listp != NULL' failed!

See upstream bug report here:

MATLAB in a systemd-nspawn

MATLAB can be run within a systemd-nspawn container to maintain a static system and avoid the library issues that often plague matlab installs after significant updates to libraries in Arch. Refer to Systemd-nspawn for detailed information on setting up such containers.

The following instruction is to get a MATLAB R2021b installation running in a minimal Debian 11 environment. It assumes MATLAB is already installed as normal in "/usr/local/MATLAB/R2021b".

Use Xhost to allow the nspawn environment to use the existing X server instance, see also Systemd-nspawn#Use an X environment.

Create a minimal Debian environment in a directory ("deb11" here) with:

$ debootstrap --include=systemd-container --components=main,contrib bullseye deb11

Set a password for the root user and create regular user:

$ systemd-nspawn -D deb11
useradd -m username

and then boot the environment with:

$ systemd-nspawn --bind-ro=/dev/dri --bind-ro=/tmp/.X11-unix --bind=/dev/shm --bind=/usr/local/MATLAB --setenv=DISPLAY=:0 --setenv=MESA_LOADER_DRIVER_OVERRIDE=i965 -b -D deb11

Install the following packages to have the required libraries in the nspawn environment for MATLAB:

"mesa-utils" and dependencies needs to be installed to support graphics acceleration. "usbutils" can be installed to support usb interfaces for I/O with MATLAB.

Install the matlab-support (from contrib source) package in the environment for some convenient integration.

$ apt-get install matlab-support

MATLAB can be launched from within the environment normally by using the binary at $MATLABROOT/bin.

Another way is to add something like

-u username -a /usr/local/MATLAB/R2021b/bin/matlab -nosoftwareopengl -useStartupFolderPref

to the systemd-nspawn command above.