I have used AESCrypt on Ubuntu 16.04 LTS for years without any issue.
After moving on Ubuntu 18.04 LTS, I can't install AESCrypt anymore:
the tar command I use says that the file AESCrypt-GUI-3.11-Linux-x86_64-Install.gz does not look like a tar archive !
Does anyone knew where the problem come from ?
Thank you for your help.
Sorry for my poor english.
AESCrypt install issue on Ubuntu 18.04 LTS
-
- Posts: 4
- Joined: Mon Nov 07, 2016 9:59 am
- paulej
- Posts: 593
- Joined: Sun Aug 23, 2009 7:32 pm
- Location: Research Triangle Park, NC, USA
- Contact:
Re: AESCrypt install issue on Ubuntu 18.04 LTS
That is just a compressed file, not a tar file.
Do this at the command line:
That should work. I discovered that lubuntu was missing zenity in a recent release. If that's missing on Ubuntu, you won't get a dialog box to enter your password. Hopefully, the latest Ubuntu still has it. If you run "aescrypt-gui" from the command-line, you should see the error about it if you have problems.
Do this at the command line:
Code: Select all
$ gunzip AESCrypt-GUI-3.11-Linux-x86_64-Install.gz
$ chmod 755 AESCrypt-GUI-3.11-Linux-x86_64-Install
$ ./AESCrypt-GUI-3.11-Linux-x86_64-Install
- paulej
- Posts: 593
- Joined: Sun Aug 23, 2009 7:32 pm
- Location: Research Triangle Park, NC, USA
- Contact:
Re: AESCrypt install issue on Ubuntu 18.04 LTS
As a follow-up, I just installed the software on Ubuntu 18.04. I had no trouble; worked fine.
Re: AESCrypt install issue on Ubuntu 18.04 LTS
I had the same (?) problem: the extracted installer did not run. The instructions above solved it, after I found out that I had to apply them in the folder where the compressed file was. it looks as the first extraction did not work properly. But I am guessing here.
- paulej
- Posts: 593
- Joined: Sun Aug 23, 2009 7:32 pm
- Location: Research Triangle Park, NC, USA
- Contact:
Re: AESCrypt install issue on Ubuntu 18.04 LTS
If the instructions worked, then everything is normal. You have to set the execution bit (chmod), which I assumed most people would know. When I have reason to publish a new update, I'll change the published file to a compressed tar file (tgz) so that the file permission is set properly.