Red Hat Bugzilla – Bug 1018368
[abrt] tracker-0.16.2-1.fc19: __strncmp_sse42: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:37:13 EDT
Description of problem:
I have no idea. I was simply greeted with the dialog box informing me that tracker had encountered a problem.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 __strncmp_sse42 at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:164
#1 file_node_data_equal_or_child at tracker-file-system.c:186
#2 file_tree_lookup at tracker-file-system.c:263
#3 tracker_file_system_unset_property at tracker-file-system.c:814
#4 crawl_directories_start at tracker-file-notifier.c:579
#5 file_notifier_traverse_tree at tracker-file-notifier.c:298
#6 g_cclosure_marshal_VOID__BOOLEANv at gmarshal.c:188
#7 _g_closure_invoke_va at gclosure.c:840
#10 tracker_crawler_stop at tracker-crawler.c:914
#11 process_func at tracker-crawler.c:548
Created attachment 811347 [details]
Created attachment 811348 [details]
Created attachment 811349 [details]
Created attachment 811350 [details]
Created attachment 811351 [details]
Created attachment 811352 [details]
Created attachment 811353 [details]
Created attachment 811354 [details]
Created attachment 811355 [details]
Created attachment 811356 [details]
Created attachment 811357 [details]
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 972464 has been marked as a duplicate of this bug. ***
*** Bug 1026037 has been marked as a duplicate of this bug. ***
*** Bug 1021515 has been marked as a duplicate of this bug. ***
Removing private flag so that those CCed on the duplicate bugs can follow.
The backtrace does contain a few lines from the files that the miner-fs was reading at the time of the crash, but the harm caused by exposing them to the public appears to be less than the harm caused by excluding others from following this bug.
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'
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.