Bug 1098731

Summary: [abrt] nepomuk-core: isEmpty(): Process /usr/bin/nepomukindexer was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Brandon Amaro <omega13a>
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: brunorobertozanuzzo, jreznik, kevin, ltinkl, omega13a, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5d60dbf9548b8f5ecfe79f58beb8c9abd16b9c4e
Whiteboard: abrt_hash:24da8dd3092bd76697382861afa173e9669b7005
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:40:39 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

Description Brandon Amaro 2014-05-17 19:21:25 UTC
Version-Release number of selected component:
nepomuk-core-4.11.3-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/nepomukindexer /home/omega13a/Documents/ch-bb/CH/templates/subSilver/ucp
crash_function: isEmpty
executable:     /usr/bin/nepomukindexer
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 isEmpty at ../../src/corelib/tools/qlist.h:99
 #2 QCoreApplication::translate at kernel/qcoreapplication.cpp:1967
 #4 QMetaObject::tr at kernel/qmetaobject.cpp:307
 #5 tr at ../../src/corelib/plugin/qlibrary.h:64
 #6 QLibraryPrivate::resolve_sys at plugin/qlibrary_unix.cpp:312
 #7 resolve at plugin/qlibrary.cpp:457
 #8 QLibrary::resolve at plugin/qlibrary.cpp:1144
 #9 qt_initIcu at tools/qlocale_icu.cpp:94
 #10 QLocalePrivate::updateSystemPrivate at tools/qlocale.cpp:529
 #11 systemPrivate at tools/qlocale.cpp:540

Comment 1 Brandon Amaro 2014-05-17 19:21:32 UTC
Created attachment 896645 [details]
File: backtrace

Comment 2 Brandon Amaro 2014-05-17 19:21:35 UTC
Created attachment 896646 [details]
File: cgroup

Comment 3 Brandon Amaro 2014-05-17 19:21:40 UTC
Created attachment 896647 [details]
File: core_backtrace

Comment 4 Brandon Amaro 2014-05-17 19:21:45 UTC
Created attachment 896648 [details]
File: dso_list

Comment 5 Brandon Amaro 2014-05-17 19:21:48 UTC
Created attachment 896649 [details]
File: environ

Comment 6 Brandon Amaro 2014-05-17 19:21:52 UTC
Created attachment 896650 [details]
File: exploitable

Comment 7 Brandon Amaro 2014-05-17 19:21:57 UTC
Created attachment 896651 [details]
File: limits

Comment 8 Brandon Amaro 2014-05-17 19:22:00 UTC
Created attachment 896652 [details]
File: maps

Comment 9 Brandon Amaro 2014-05-17 19:22:02 UTC
Created attachment 896653 [details]
File: open_fds

Comment 10 Brandon Amaro 2014-05-17 19:22:04 UTC
Created attachment 896654 [details]
File: proc_pid_status

Comment 11 Brandon Amaro 2014-05-17 19:22:07 UTC
Created attachment 896655 [details]
File: var_log_messages

Comment 12 Bruno Roberto Zanuzzo 2014-07-04 00:57:30 UTC
Another user experienced a similar problem:

After installing Fedora 20 x64 with KDE on my laptop, connected via the Internet and konqueror downloaded a picture with the dolphin entered the directory where it was downloaded and modified the image name then applied on the desktop. 

How was newly installed operating system, the disk was probably being indexed when I modified the downloaded image. 

For the record, I was also updating the system ('# yum-y update') in the meantime. 

After a few moments the application 'nepomukindexer was killed by signal 11

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/nepomukindexer /home/xmrbrz/Pictures/redhat-ladie.jpg
crash_function: isEmpty
executable:     /usr/bin/nepomukindexer
kernel:         3.11.10-301.fc20.x86_64
package:        nepomuk-core-4.11.3-1.fc20
reason:         Process /usr/bin/nepomukindexer was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Fedora End Of Life 2015-05-29 11:52:37 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 14 Fedora End Of Life 2015-06-29 20:40:39 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.