Bug 196018 - graphics/exif 0.6.21 has several problems with handling photos
Summary: graphics/exif 0.6.21 has several problems with handling photos
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Walter Schwarzenfeld
Depends on:
Reported: 2014-12-16 09:56 UTC by james.a.mcguire01
Modified: 2020-02-03 09:05 UTC (History)
1 user (show)

See Also:
james.a.mcguire01: maintainer-feedback+

Problem photo (111.50 KB, image/jpeg)
2014-12-16 09:56 UTC, james.a.mcguire01
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description james.a.mcguire01 2014-12-16 09:56:41 UTC
Created attachment 150627 [details]
Problem photo

* Unable to clear Exif data from photographs using exif --remove * although I could apparently clear the longitude field manually by specifying the tag.

* Unable to see latitude field when using exif --l <filename>

* Exif complains of exif structure of picture, it was complaining about unrecognised fields but I cannot recall which specific command syntax revealed that message:

exif --remove DSCN0439-50.jpg
Corrupt data
The data provided does not follow the specification.
ExifLoader: The data supplied does not seem to contain EXIF data.

The photo is not the original, the sequence of events were:
Photo taken on Nikon Coolpix S9700
Photo transferred to Android Motorola XT890 using Nikon App (rescaled)
Photo reduced in size by 50% using Win7 MS Paint. 

* I also took shots directly on the XT890 and was experiencing similar problems, no latitude field when using the -l parameter against the photo, unable to clear meta data.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-12-17 00:06:27 UTC
Create a correct Summary and assign.
Comment 2 Walter Schwarzenfeld freebsd_triage 2018-01-11 18:34:17 UTC
Is this still relevant? No maintainer feedback till now!
Comment 3 Walter Schwarzenfeld freebsd_triage 2019-08-08 09:51:50 UTC
Comment 4 Walter Schwarzenfeld freebsd_triage 2020-01-31 18:57:06 UTC
This is a very old bugreport. I close here with feedback timeout. If there still same problems, please reopen.
Comment 5 james.a.mcguire01 2020-02-03 09:05:25 UTC
What an atrocious way to handle a bug.  6 years after reporting the issue no action is taken.  It would have taken you 5 minutes to deploy the software and test the behaviour which I reported.  Instead after 6 years you just sweep the issue under the rug like it never existed.  Tell me, why should I waste my time reporting anything in the future.