Bug 994401

Summary: [abrt] nepomuk-core-4.10.5-1.fc19: Exiv2::ValueType<std::pair<unsigned int, unsigned int> >::toFloat: Process /usr/bin/nepomukindexer was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Patrik Schönfeldt <redhat-bugzilla>
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jreznik, kevin, kvolny, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c63346223f167a7d477d5d9a20f8f93da4d8a1c8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:37:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
file triggering the crash none

Description Patrik Schönfeldt 2013-08-07 08:20:52 UTC
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

Comment 1 Patrik Schönfeldt 2013-08-07 08:20:58 UTC
Created attachment 783719 [details]
File: backtrace

Comment 2 Patrik Schönfeldt 2013-08-07 08:21:02 UTC
Created attachment 783720 [details]
File: cgroup

Comment 3 Patrik Schönfeldt 2013-08-07 08:21:06 UTC
Created attachment 783721 [details]
File: core_backtrace

Comment 4 Patrik Schönfeldt 2013-08-07 08:21:10 UTC
Created attachment 783722 [details]
File: dso_list

Comment 5 Patrik Schönfeldt 2013-08-07 08:21:14 UTC
Created attachment 783723 [details]
File: environ

Comment 6 Patrik Schönfeldt 2013-08-07 08:21:18 UTC
Created attachment 783724 [details]
File: exploitable

Comment 7 Patrik Schönfeldt 2013-08-07 08:21:22 UTC
Created attachment 783725 [details]
File: limits

Comment 8 Patrik Schönfeldt 2013-08-07 08:21:31 UTC
Created attachment 783726 [details]
File: maps

Comment 9 Patrik Schönfeldt 2013-08-07 08:21:34 UTC
Created attachment 783727 [details]
File: open_fds

Comment 10 Patrik Schönfeldt 2013-08-07 08:21:38 UTC
Created attachment 783728 [details]
File: proc_pid_status

Comment 11 Patrik Schönfeldt 2013-08-07 08:21:42 UTC
Created attachment 783729 [details]
File: var_log_messages

Comment 12 Karel Volný 2013-11-06 16:03:12 UTC
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

Comment 13 Karel Volný 2013-11-06 16:06:25 UTC
Created attachment 820508 [details]
file triggering the crash

Comment 14 Karel Volný 2013-11-06 16:08:11 UTC
(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 :-/

Comment 15 Fedora End Of Life 2015-01-09 19:20:07 UTC
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.

Comment 16 Fedora End Of Life 2015-02-17 16:37:41 UTC
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.