exiftool CLI works on the same file in Windows, not in Linux

[ForumUserSoftwareEngineer]

Hi! The same file works perfectly in Windows, giving 180 rows of metadata as expected.

But in Ubuntu (Virtualbox) the identical file, up to the byte (in aVirtualBox shared folder), just gives an output like the following:

Code Select Expand

exiftool  DJI_20240000000000_0000_W.JPG
ExifTool Version Number        : 12.73
File Name                      : DJI_20230000000000_0000_W.JPG
Directory                      : .
File Size                      : 8.0 MB
File Modification Date/Time    : 2024:00:00 00:00:00+00:00
File Access Date/Time          : 2024:00:00 00:00:00+00:00
File Inode Change Date/Time    : 2024:00:00 00:00:00+00:00
File Permissions                : -rwxrwx---
Error                          : File is empty
so basically only outputs basic metadata. The files is not empty, I do not know why it says that.

Exiftool Version Number is 12.73 in both Windows and Linux


The file opens succesfully in both Linux and Windows, so it does not seem corrupted or broken at all.

[Phil Harvey]

What is the command you used?  Try adding -a to see if you also get a Seek Error.

- Phil

Edit: I don't recall ever seeing this problem before.  Somehow the file is opened OK, but it can't be read.  Hopefully you see more errors with -a, but I'll add an extra error message to 12.74 that may diagnose this.  I don't know if it is possible to have permission to open the file for reading, but not permission to actually read it?

[StarGeek]

The "Other" permissions are set so it can't be read.  Is the shell running as owner or the same group?  Or maybe I'm reading it wrong, Linux isn't my strong suit.

[ForumUserSoftwareEngineer]

The command I ran was

exiftool  DJI_20240000000000_0000_W.JPG

The same output is also given by adding -a:
exiftool -a  DJI_20240000000000_0000_W.JPG

I think this is an issue with VirtualBox shared folders actually. I was wrong, the file content does not open in Ubuntu actually