Red Hat Bugzilla – Bug 1031752
[abrt] tracker-0.16.2-4.fc20: type_get_qdata_L: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:58:42 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 type_get_qdata_L at gtype.c:3646
#1 type_check_is_value_type_U at gtype.c:4116
#2 g_type_check_is_value_type at gtype.c:4143
#3 g_value_type_compatible at gvalue.c:498
#4 g_value_object_collect_value at gobject.c:3686
#7 enumerator_data_process at tracker-crawler.c:626
#8 file_enumerate_next_cb at tracker-crawler.c:713
#9 next_async_callback_wrapper at gfileenumerator.c:306
#10 g_task_return_now at gtask.c:1108
#11 complete_in_idle_cb at gtask.c:1117
Potential duplicate: bug 801515
Created attachment 825740 [details]
Created attachment 825741 [details]
Created attachment 825742 [details]
Created attachment 825743 [details]
Created attachment 825744 [details]
Created attachment 825745 [details]
Created attachment 825746 [details]
Created attachment 825747 [details]
Created attachment 825748 [details]
Created attachment 825749 [details]
Created attachment 863326 [details]
Folder of error records
Just adding records from this error encase they add value.
I think that the crush appeared after the use of the PeaZip utility (portable 64bit edition) for the decompression of a folder
I think that the crush appeared after the use of the PeaZip utility (portable 64bit edition) for the decompression of a folder.
Another user experienced a similar problem:
tarring a large number of files from one file system to another.
reason: tracker-miner-fs killed by SIGSEGV
runlevel: N 5
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This happens pretty much as soon as I log into the desktop.
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.