Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error reading some JPG file #119

Open
matianfu opened this issue Nov 1, 2017 · 3 comments
Open

Error reading some JPG file #119

matianfu opened this issue Nov 1, 2017 · 3 comments

Comments

@matianfu
Copy link

matianfu commented Nov 1, 2017

img_20171101_182436
For some jpg file, the detectFile function returns an error, such as following:

Error: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=13, datetime=2017:11:01 18:24:35, GPS-Data, model=Nexus 6P, resolutionunit=2, height=0, yresolution=199, orientation=upper-left, software=angler-user 7.0 NBD90X 3254009 release-keys, xresolution=251, manufacturer=Huawei, width=0] name use count (30) exceeded

The problem is exactly the same as this bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=1201630

The built-in file command (Ubuntu server amd64 16.04 LTS) won't emit such an error. So I guess your source code of libmagic should be updated.

@mscdex
Copy link
Owner

mscdex commented Nov 1, 2017

The version of libmagic currently in this repo is already the latest as of this writing (5.32) and that message still appears with the libmagic's master branch as of this writing. Unfortuately the upstream bug tracker is currently down so we will have to wait before this issue can be reported there.

@matianfu
Copy link
Author

matianfu commented Nov 2, 2017

Dear @mscdex , is it possible to change the upstream to libmagic source package of a distro, such as Ubuntu or Fedora. I found no problem for the built-in file command in those distros.

@mscdex
Copy link
Owner

mscdex commented Nov 2, 2017

Not really, right now I have to manually apply changes to upstream to get various things to work appropriately. I do not have actual patches for these changes at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants