Red Hat Bugzilla – Bug 600303
[abrt] crash in tracker-0.8.4-1.fc13: OJPEGReadBufferFill: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-02 23:29:46 EDT
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/tracker-extract component: tracker crash_function: OJPEGReadBufferFill executable: /usr/libexec/tracker-extract global_uuid: 2dd5c2bcad80788a089abc993d7712fb46ac1978 kernel: 2.6.33.5-112.fc13.x86_64 package: tracker-0.8.4-1.fc13 rating: 4 reason: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created attachment 421215 [details] File: backtrace
The attached backtrace indicates the crash occured in a libtiff function.
Need to see the input TIFF file that caused the crash in order to have much hope of doing anything with this.
Wow, that was 2 weeks ago. I have no idea which file it was. Sorry.
It is "file:///home/dan/Pictures/The%20Baileys%20of%20Braybooke/dsc04898.arw".
I tried to attach the file, but it kept crashing my browser! Both Chrome and Firefox. I have uploaded it here: http://danieljamesscott.org/images/dsc04898.arw Thanks, Dan
Yeah, all that stuff depends on libtiff for reading TIFFs, so the crashes aren't surprising. Thanks for uploading the file. [ ... looks at it ... ] My goodness, that was produced by some incompetent programmers, wasn't it :-( Multiple violations of the TIFF spec. The crash cause seems to be a duplicate of bug #603024, so I can get it to not crash, but I'm afraid actually extracting the image might be problematic.
*** Bug 606549 has been marked as a duplicate of this bug. ***
Not my camera! :) Sony Alpha DSLR-A100 - belongs to a relative of mine. Personally I stay away from Sony stuff... now I have another reason! Strangely, ufraw and The GIMP don't complain about it - I've had no problem viewing it. Thanks for your help.
*** Bug 600539 has been marked as a duplicate of this bug. ***
*** Bug 595903 has been marked as a duplicate of this bug. ***
*** Bug 608275 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.