Bug 1013268

Summary: [abrt] tracker-0.16.2-2.fc20: _g_log_abort: Process /usr/libexec/tracker-miner-fs was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Vadim Rutkovsky <vrutkovs>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: afarrag, andrelib, brpocock, bucky, cam.avarley, dakingun, ddkroyal001, debarshir, deepjyotimukherjee.suman, digilabtec, ezwen-redhatbugzilla, filipesbim, giuseppemfusco, heyveld, ifoolb, jairoarbey, jd1008, jeroen, jjardon, jonandmykaela, kevin.chopra, legoktm, marcel.buchholz, marco.guazzone, markgerlach.mobile, moez.roy, mohdright, Mustafa.vantom, pablo, p.malishev, pmutha, redhat-bugzilla, robert, roberzguerra, serega.belarus, sir.ade, skurtsev, starparodia, tcfxfzoi, Tylcharob, vaaghoofdharry, yanglifu90, yiorgos-lists, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:103894ae0315e1baf73536ecb9381f27be7fe159
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:29:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Vadim Rutkovsky 2013-09-28 23:23:21 UTC 
Version-Release number of selected component:
tracker-0.16.2-2.fc20

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: _g_log_abort
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.11.1-300.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:255
 #4 tracker_file_notifier_init at tracker-file-notifier.c:1278
 #5 g_type_create_instance at gtype.c:1868
 #6 g_object_new_internal at gobject.c:1746
 #7 g_object_new_valist at gobject.c:2002
 #9 tracker_file_notifier_new at tracker-file-notifier.c:1334
 #10 tracker_miner_fs_init at tracker-miner-fs.c:584
 #11 g_type_create_instance at gtype.c:1862
 #12 g_object_new_internal at gobject.c:1746
 #13 g_object_new_valist at gobject.c:2002

Potential duplicate: bug 1004140
Comment 1 Vadim Rutkovsky 2013-09-28 23:23:27 UTC 
Created attachment 804553 [details]
File: backtrace
Comment 2 Vadim Rutkovsky 2013-09-28 23:23:33 UTC 
Created attachment 804554 [details]
File: cgroup
Comment 3 Vadim Rutkovsky 2013-09-28 23:23:39 UTC 
Created attachment 804555 [details]
File: core_backtrace
Comment 4 Vadim Rutkovsky 2013-09-28 23:23:45 UTC 
Created attachment 804556 [details]
File: dso_list
Comment 5 Vadim Rutkovsky 2013-09-28 23:23:50 UTC 
Created attachment 804557 [details]
File: environ
Comment 6 Vadim Rutkovsky 2013-09-28 23:23:55 UTC 
Created attachment 804559 [details]
File: limits
Comment 7 Vadim Rutkovsky 2013-09-28 23:24:01 UTC 
Created attachment 804560 [details]
File: maps
Comment 8 Vadim Rutkovsky 2013-09-28 23:24:06 UTC 
Created attachment 804561 [details]
File: open_fds
Comment 9 Vadim Rutkovsky 2013-09-28 23:24:12 UTC 
Created attachment 804562 [details]
File: proc_pid_status
Comment 10 Rober Guerra 2014-05-28 23:06:27 UTC 
Another user experienced a similar problem:

at system startup I logged in gnome, after gnome logoff, I logged in and Cinnamon, then error occurred.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: _g_log_abort
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.13.10-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-miner-fs killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 11 Jeroen Beerstra 2014-06-17 19:43:57 UTC 
Another user experienced a similar problem:

Starting Cinnamon in run level 5 -> tracker craches at startup

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: _g_log_abort
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.14.6-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-miner-fs killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 kevin.chopra 2014-06-27 12:39:46 UTC 
Another user experienced a similar problem:

Recent Update

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: _g_log_abort
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.14.8-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-miner-fs killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Fedora Admin XMLRPC Client 2014-07-26 17:12:25 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 14 Fedora Admin XMLRPC Client 2014-07-27 06:34:21 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 15 harry 2014-10-15 20:12:22 UTC 
Another user experienced a similar problem:

after starting lightdm and logging in, all desktop icons disappeared after a couple of seconds and the pc became unresponsive to mouseclicks, after restarting lightdm via tty2 problem was solved

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-miner-fs
crash_function: _g_log_abort
executable:     /usr/libexec/tracker-miner-fs
kernel:         3.16.4-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-miner-fs killed by SIGABRT
runlevel:       N 3
type:           CCpp
uid:            1000
Comment 16 Fedora End Of Life 2015-05-29 09:28:32 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 17 Fedora End Of Life 2015-06-29 12:29:24 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.
Comment 18 Debarshi Ray 2015-09-30 16:18:59 UTC 

*** This bug has been marked as a duplicate of bug 924558 ***