Bug 1031752

Summary: [abrt] tracker-0.16.2-4.fc20: type_get_qdata_L: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: 281094v, akurtako, brian, cam.avarley, dakingun, debarshir, devonjanitz, gopapado, hoihoi-p, ian.bertolacci, karl+rhbugzilla, liblit, lobocode, maleclukas, me, nick.korotysh, redhat, srikanth, stefano.manocchio, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1e88bb38f2333edcf77991123b7e312077e0a4bb
Whiteboard: abrt_hash:ace9091d1dd9a610dacbade4aa9b8eaba0be3323
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:58:42 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
Folder of error records none

Description Mikhail 2013-11-18 17:09:38 UTC
Version-Release number of selected component:
tracker-0.16.2-4.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: type_get_qdata_L
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.12.0-2.fc21.x86_64+debug
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
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

Comment 1 Mikhail 2013-11-18 17:09:45 UTC
Created attachment 825740 [details]
File: backtrace

Comment 2 Mikhail 2013-11-18 17:09:49 UTC
Created attachment 825741 [details]
File: cgroup

Comment 3 Mikhail 2013-11-18 17:09:52 UTC
Created attachment 825742 [details]
File: core_backtrace

Comment 4 Mikhail 2013-11-18 17:09:55 UTC
Created attachment 825743 [details]
File: dso_list

Comment 5 Mikhail 2013-11-18 17:09:58 UTC
Created attachment 825744 [details]
File: environ

Comment 6 Mikhail 2013-11-18 17:10:01 UTC
Created attachment 825745 [details]
File: exploitable

Comment 7 Mikhail 2013-11-18 17:10:04 UTC
Created attachment 825746 [details]
File: limits

Comment 8 Mikhail 2013-11-18 17:10:09 UTC
Created attachment 825747 [details]
File: maps

Comment 9 Mikhail 2013-11-18 17:10:12 UTC
Created attachment 825748 [details]
File: open_fds

Comment 10 Mikhail 2013-11-18 17:10:15 UTC
Created attachment 825749 [details]
File: proc_pid_status

Comment 11 Devon Janitz 2014-02-14 16:11:02 UTC
Created attachment 863326 [details]
Folder of error records

Just adding records from this error encase they add value.
Thanks, Devon

Comment 12 gopapado 2014-03-31 16:54:50 UTC
I think that the crush appeared after the use of the PeaZip utility (portable 64bit edition) for the decompression of a folder

Comment 13 gopapado 2014-03-31 16:55:08 UTC
I think that the crush appeared after the use of the PeaZip utility (portable 64bit edition) for the decompression of a folder.

Comment 14 Sean Sheedy 2014-07-03 22:07:34 UTC
Another user experienced a similar problem:

tarring a large number of files from one file system to another.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: type_get_qdata_L
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.14.9-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-miner-fs killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            20028

Comment 15 Fedora Admin XMLRPC Client 2014-07-26 17:12:39 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 16 Fedora Admin XMLRPC Client 2014-07-27 06:34:38 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 17 Brian J. Murrell 2014-07-27 17:12:53 UTC
This happens pretty much as soon as I log into the desktop.

Comment 18 Fedora End Of Life 2015-05-29 09:47:44 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 19 Fedora End Of Life 2015-06-29 12:58:42 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.