Red Hat Bugzilla – Bug 1248234
Tracker-extract locks up on initial login
Last modified: 2015-12-02 13:14:52 EST
Description of problem:
When I first log in, /usr/libexec/tracker-extract is running (several copies, but only one is drawing >100% CPU) and accessing the hard drive many times per second (hard drive access lite basically is a strobe). Process must be killed; I typically use SIGHUP to do so.
Version-Release number of selected component (if applicable):
Easily repeatable (reboot, log in) for me; uncertain how reproducible it will be to others.
Steps to Reproduce:
2. Log in
Repeated disk access and full use of one processor until receipt of SIGHUP
Should exit quickly and/or use disk very little.
This system was upgraded relatively recently to Fedora 22 from Fedora 20 using fedup.
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.