Appimage cannot execute binary file exec format error

Hi «Brew01»,

Welcome to the wonderful world of Linux Mint and its excellent forum !

I just read your post and the good replies to it. Here are my thoughts on this as well.

It would help to know more about your system setup. If you run «inxi -Fxzd» from the console terminal prompt, highlight the results, copy and paste them back here, that should provide enough information.

In order to run applications packaged as an AppImage file (something.AppImage), you need to have the «fuse» package installed. I thought the «fuse» package was already installed in most Linux Mint versions. You can install it through the Software Manager or Synaptic Package Manager (SPM), or by using the console terminal command below.

And as was already stated, you have to have permission to run the file, if it was not packaged that way. You can right click the AppImage file, select properties, permissions tab, make sure to check the allow executable or executable, click apply, okay. Then, you can just double click the AppImage file to launch it, run it. You can also create new menu items and or desktop shortcut launchers; some AppImages will create these for you, others won’t.

How To Use AppImage in Linux [Complete Guide], October 27, 2017
https://itsfoss.com/use-appimage-linux/

«AppImages require FUSE to run. Filesystem in Userspace (FUSE) is a system that lets non-root users mount filesystems.»
https://github.com/AppImage/AppImageKit/wiki/FUSE

Note: Some software was specifically designed for a certain version of Linux, like Linux Mint 18 which is based on Ubuntu 16.04, so it might not work on Linux Mint 17.x based on Ubuntu 14.04. BUT, I have personally found out that most AppImages designed for the newer Linux Mint 18.x will run on my Linux Mint 17.x system.

Hope this helps …

The UltiMaker S7 is built on the success of the UltiMaker S5 and its design decisions were heavily based on feedback from customers.

 
 
So what’s new?
The obvious change is the S7’s height. It now includes an integrated Air Manager. This filters the exhaust air of every print and also improves build temperature stability. To further enclose the build chamber the S7 only has one magnetically latched door.

 
The build stack has also been completely redesigned. A PEI-coated flexible steel build plate makes a big difference to productivity. Not only do you not need tools to pop a printed part off. But we also don’t recommend using or adhesion structures for UltiMaker materials (except PC, because…it’s PC). Along with that, 4 pins and 25 magnets make it easy to replace the flex plate perfectly – even with one hand.

 
The re-engineered print head has an inductive sensor which reduces noise when probing the build plate. This effectively makes it much harder to not achieve a perfect first layer, improving overall print success. We also reversed the front fan direction (fewer plastic hairs, less maintenance), made the print core door magnets stronger, and add a sensor that helps avoid flooding.

 
The UltiMaker S7 also includes quality of life improvements:
Reliable bed tilt compensation (no more thumbscrews) 2.4 and 5 GHz Wi-Fi A 1080p camera (mounted higher for a better view) Compatibility with 280+ Marketplace materials Compatibility with S5 project files (no reslicing needed) And a whole lot more  
Curious to see the S7 in action?
We’re hosting a free tech demo on February 7.
It will be live and you can ask any questions to our CTO, Miguel Calvo.
Register here for the Webinar

Photo by Jivacore/Shutterstock.com

Linux has been reworked heavily since it first came out to the point that it’s no longer an OS for terminal kings. Just about everyone can use it now thanks to the much better user interfaces that we see in modern Linux distros. However, that doesn’t mean it can’t be frustrating at times. 

In this article, we’re taking a look at the “cannot execute binary file: exec format error” issue and giving you a few solutions on how to get rid of the problem. 

Also read: How to make a file executable in Linux?

Check the architecture

The first thing you should do is ensure you’ve got the right bin file. Binary files made for 32-bit systems won’t work on 64-bit systems and vice-versa. You can check the architecture of any file by using the command below.

file filename

If the architecture doesn’t match between your file and the PC you’re running it on, try running the corresponding binary file for the matching architecture. 

Check the file

Binary files can be run on Windows, Linux and macOS. However, binaries made for one OS won’t run on the others. Generally, these files have different file formats to help users distinguish between them. If you’re trying to run a binary file made for Windows on a Linux distro, it’s obviously not going to work. 

If you must run the binary on Linux however, we recommend downloading Wine and using it to run the file. Wine is a compatibility layer capable of running Windows applications on POSIX-compliant operating systems, including Linux and macOS. 

Install GCC and Gfortran

GCC and Gfortran are required for several binary files to compile and execute properly. You can install them by typing the command below in your terminal. 

sudo apt-get install gfortran && sudo apt-get install build-essential

Now try running your binary file again and it should run without a problem — fixing the ‘cannot execute binary file’ error.

Uncompress the file

Sometimes binary files are compressed to make them easier to share over the internet. Try uncompressing the file to see if that helps you run it fine. Run the following commands on at a time. 

xz -d ./filename
chmod +x ./filename
./filename

Check file permissions

Another potential reason for your binary file not running could be that the user doesn’t have permission to change or read the file. You can fix this by typing the following command in the terminal. 

chmod +x filename

Once the permissions are set, you can run the file by typing this.

./filename

Use Dos2unix

The Dos2unix command can sometimes help binaries made for DOS to run on UNIX systems. Try using the following command to see if your file runs or not. 

dos2unix filename.bin

If we’ve missed out on any fixes that helped you solve the ‘cannot execute binary file’ error, please comment down below with the fix.

Also read: What does ./ mean in Linux?

Dear community, I am having trouble installing ImageJ on the Raspberry Pi 4 Model B+ 4GB running on Ubuntu 64. However, a month ago, I have installed ImageJ on Ubuntu on my desktop PC, and it is running fine.
Now I have tried to run ImageJ for Linux on Ubuntu 64 on my Raspberry, and I get the following error.

bash: ./ImageJ: cannot execute binary file: Exec format error

After a bit of googling, I found out that this error is typically related to the OS if it is 64 or 32 Bit, but Ubuntu is 64 Bit, so it should be fine.
I have tried executing with java 8 and 11, but I get the same error in both cases.

I compared the ImageJ folders on my Pi and my PC, and in the folder, on my PC, I have two additional files that I do not have on the Raspberry. So I have marked the files in the picture below.

Just after downloading the ImageJ from the webpage, the folder on my PC has the same files as the one on the Raspberry. So, I have done something so that these two additional files on my PC appear, but unfortunately, I cannot remember what.

I really appreciate any help you can provide.

Best regards,
Georgi