Also for some reason the image gives me serious Sam vibes.

That’s because it is!

Could you explain what these bugs are? I’m curious.

Well, in this scenario the image file had 512 bytes sections, each one is called a block. If you have a KiB (a kibibyte = 1024 bytes) it will occupy 2 blocks and so on…

Since this image file had a header with 512 bytes (i.e. a block) I could, in any of the relevant Linux mounting software (e.g. mount, losetup), choose an offset adding to the starting block of a partition. The command would look like this:

sudo mount -o loop,offset=$((header+partition)) img_file /mnt

Not a Linux problem per se, but I had a 128GB image disk in a unknown .bin format which belongs to a proprietary application. The application only ran on Windows.

I tried a few things but nothing except Windows based programs seemed able to identify the partitions, while I could run it in Wine, it dealt with unimplementend functions. So after a bit of googling and probing the file, it turns out the format had just a 512 bytes as header which some Windows based software ignored. After including the single block offset, all the tools used in Linux started working flawlessly.

You should edit that to say Gnome Software (aka Gnome App Store) instead of just Gnome. People are going to think you’re talking about the whole DE.

Yep, so that corroborates my comment. If you know someone british they may speak hegehmony.

I think US citizens say ‘Hedge-emony’ while the british say ‘Hegeh-emony’. At least that’s what google thinks lol.