Description of problem:
KDE has it's own desktop search and indexer - nepomuk+strigi aka "semantic desktop". Tracker is redundant in KDE, just wasting resources.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.KDE log in
tracker processes started in KDE
no tracker processes started in KDE
please fix this!
Tracker in kde is just useless!
That's valid also on a fully updated fedora 16 installation.
This bug seems easy to fix. If you don't have enough time to fix it, let us know, so we can ask some provenpackager to commit necessary changes.
This bug (and all other) seems to be ignored. I checked the non-responsive maintainer process. So I checked vacation list, first. Then I checked activity in bugzilla. There are 375 bugs in NEW (a few are ASSIGNED because they were auto-closed and reopened). I searched for bugs with the same assignee (any state) with another condition "changed by = assignee" and maybe my searching skills are bad, but it returned empty result. So, if my search query was correct, there is no activity in bugzilla.
The only thing preventing me from starting non-responsive maintainer process is "After other 7 days (now 3 weeks total), the reporter posts a formal request to the Fedora devel list with the bug link, indicating all reasonable efforts to contact the maintainer have failed *and* *that* *they* *wish* *to* *take* *over* *the* *package*." I don't want to take over any package.
Anyway, there seems to be zero hope that this bug will get fixed. We'll need provenpackager for this.
Rex: Could you fix it for us?
I guess I can flex some provenpackager muscle if I have to, since this affects me (and my deployments @ work) directly too.
Deji, do you have any preference between implementing:
Tracking to make sure it's highlighted to be addressed prior to f18 release too
xfce/lxde chimed in not wanting this either, guess I'll go with the OnlyShowIn=GNOME; approach for now
and Fwiw, these autostart files currently contain:
so even easier fix.
Patched builds underway, please test:
tracker-0.14.2-2.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tracker-0.14.2-2.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This bug looks similar to bug 747689 which I opened nearly a year ago when I noticed tracker running in KDE.
tracker-0.14.2-2.fc17 has been submitted as an update for Fedora 17.
tracker-0.12.10-2.fc16 has been submitted as an update for Fedora 16.
tracker-0.14.2-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
tracker-0.14.2-3.fc17 has been submitted as an update for Fedora 17.
tracker-0.14.2-4.fc18 has been submitted as an update for Fedora 18.
tracker-0.14.2-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
I updated to tracker-0.14.2-3.fc17.x86_64 this morning and rebooted. Tracker is not running, so bug fix took care of the problem for me. Thanks.