Version-Release number of selected component: nepomuk-core-4.10.5-1.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/nepomukindexer /home/patrik/Bilder/import/114_PANA/P1140807.JPG crash_function: Exiv2::ValueType<std::pair<unsigned int, unsigned int> >::toFloat executable: /usr/bin/nepomukindexer kernel: 3.10.4-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 Exiv2::ValueType<std::pair<unsigned int, unsigned int> >::toFloat at value.hpp:1666 #1 Nepomuk2::(anonymous namespace)::toVariantFloat at /usr/src/debug/nepomuk-core-4.10.5/services/fileindexer/indexer/exiv2extractor.cpp:89 #2 Nepomuk2::Exiv2Extractor::extract at /usr/src/debug/nepomuk-core-4.10.5/services/fileindexer/indexer/exiv2extractor.cpp:234 #3 Nepomuk2::Indexer::fileIndex at /usr/src/debug/nepomuk-core-4.10.5/services/fileindexer/indexer/indexer.cpp:146 #4 Nepomuk2::Indexer::indexFile at /usr/src/debug/nepomuk-core-4.10.5/services/fileindexer/indexer/indexer.cpp:101 Potential duplicate: bug 971278
Created attachment 783719 [details] File: backtrace
Created attachment 783720 [details] File: cgroup
Created attachment 783721 [details] File: core_backtrace
Created attachment 783722 [details] File: dso_list
Created attachment 783723 [details] File: environ
Created attachment 783724 [details] File: exploitable
Created attachment 783725 [details] File: limits
Created attachment 783726 [details] File: maps
Created attachment 783727 [details] File: open_fds
Created attachment 783728 [details] File: proc_pid_status
Created attachment 783729 [details] File: var_log_messages
It just crashed somewhere in the background. I believe I have seen this already, but abrt doesn't offer any existing report (although it says it traces *a lot* of these). reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/nepomukindexer /home/kvolny/tests/php/Security/CVE-2011-4566-php-integer-overflow-in-exif-process-IFD-TAG/bug60150.jpg crash_function: Exiv2::ValueType<std::pair<unsigned int, unsigned int> >::toFloat executable: /usr/bin/nepomukindexer kernel: 3.11.6-200.fc19.x86_64 package: nepomuk-core-4.11.2-1.fc19 reason: Process /usr/bin/nepomukindexer was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Created attachment 820508 [details] file triggering the crash
(In reply to Karel Volný from comment #12) > but abrt doesn't offer any existing report cool that it found duplicate afterwards and just appended the comment, making it look a bit silly :-/
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.