Linux - unable to install 13.9

[prich]

Hi all,

I am a regular FreeFileSync user and like to keep my version up to date.
I have just received notification of the upgrade to 13.9
ALL attempts to install this version using ',,,,,install.run' do not work. I find that I am unable to change ANY of the permissions (even with sudo) and thus cannot set the file to executable.
I have tried on Mint 21.3 and 22 (XFCE)
All attempts result in 'command not found'.
(Much to my annoyance, the Windows version installs as expected).

Any assistance in solving this problem will be greatly appreciated.

regards
peter

[bgstack15]

Reality check: when running a program by name, you have to specify a directory as part of the command, unless the program is in one of the directories listed in your PATH environment variable. For example, if you want to run install.run from the current directory (also known as "."), you would have to type in:

./install.run


This is NOT recommended, but you could choose to add "current directory" (wherever your shell is currently looking when you run "ls") to the PATH with the following:

export PATH="${PATH}:."


The above would add the current directory as the last entry in the PATH list, which is colon-separated. So, don't do that. You might notice that "echo $PATH" would show you entries like /usr/bin, /usr/local/bin, /home/username/bin and so on.
You don't need to add whatever path to PATH just to run this one install program. You would want to run:

/home/username/Downloads/install.run


Also, you want to make sure the program is executable, so that the shell knows what on earth to do with this program:

chmod +x /path/to/install.run


Do the chmod (change mode) before trying to then execute it.

If any of these steps fail, show me the output from when you try.

[prich]

Hi bgstack15
Thanks for your response. I have not tried you export Path... method. I usually use your method
[...path to file...]/install.run
ALL attempts to run the file result in 'command not found'.
ALL attempts to change permissions with or without sudo (including File Manager, CLI and Midnight Commander) fail to make ANY change to the permissions of the file.
As additional piece of information, I have been using FreeFileSync for several years (not sure how many versions) and have donated to the cause.
In the past I have made a suggestion for improvement in the user interface and the programmers chacked AND implemented the change.
This is the first time I have had a problem installing.
regards
peter

[therube]

Just to be clear, when you say " [...path to file...]/install.run", you mean,
[...path to file...]/FreeFileSync_13.9_Install.run ?

[pal]

..I just right-clicked the .._install.run file in the nemo gui; then the terminal opened; answered 'y' for yes proceed and voila .. installed.