install command on linux doesn't bring up installer - again
6 views (last 30 days)
I'm having the same problem that others have had (same summary) but the solution did not work.
I download the zip file. I unzip using:
unzip -X -K matlab_R2020a_glnxa64.zip -d matlab_2020a_installer
per this recommendation from Mathworks. Per the same recommendation, I sudu su, and then
The install script has execute permissions. But what happens is that the install script does not appear to do anything - it just hangs. The terminal shows that I've hit the enter key, but no install script appears. Frustrating. Same result if I DON'T sudo su first, but then just sudo ./install.
I added the required /usr/local/MATLAB and /usr/local/MATLAB/R2022a and chmodded 777 them both. No luck.
But if I try to run install WITHOUT root privileges, the script runs but then fails later when it doesn't have permission to write files. I can start install either with ./install in the terminal, OR by double clicking on the icon in Nautilus (ubuntu's folder viewer). Same thing: I get the installer running but failure when it actually tries to write files.
I've installed about four versions of Matlab in ubuntu and Windows. The ubuntu install has never worked without issues. Not once. Would appreciate both an immediate answer and a more bomb-proof linux/ubuntu install. Thanks!
PS The above sounds a little snippy - sorry. Didn't mean for it to be so. In fairness, too, there are so many ways to install stuff in various versions of linux. My experience is that an awful lot of answers to linux questions start with "There are at least seven different ways." Then a way is given that is not relevant to your flavor of linux, involving the installation of four or five software packages, several reboots, and then the instructions finish with something like "Then all you have to do is sudo numpy, porcupine your yaml, and have your sysadmin refactor your code base". Then.... (wait for it) you get an "easy peasy!". </rant>
Seriously, I'd appreciate you help in getting the software up and running. The help I've received from the support staff has always been spot on and helpful.
More Answers (1)
Rik on 28 Aug 2022
The 'solution' is to run the installer as normal user (no sudo) and make the current user the owner of the install directory with chown. That has always worked for me so far.
I personally view this strange workflow as a bug, as long as it isn't properly documented how you should do this.