Marking as invalid for strigi, it only starts when you start one of its
clients.
** Changed in: strigi (Ubuntu)
Status: New = Invalid
--
[gutsy] trackerd vs. strigidaemon
https://bugs.launchpad.net/bugs/147017
You received this bug notification because you are a member of Ubuntu
Bugs,
Checked that with the latest updates, tracker is no longer started in
KDE. Thanks.
--
[gutsy] trackerd vs. strigidaemon
https://bugs.launchpad.net/bugs/147017
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Jonothan Riddle disabled tracker on KDE in a recent upload:
tracker (0.6.3-0ubuntu2) gutsy; urgency=low
.
* Add 02_no_kde_autostart.patch, don't autostart in KDE
since it already has a disk indexer
** Changed in: tracker (Ubuntu)
Status: Incomplete = Fix Released
--
[gutsy]
Could you tell us which tracker version do you have? If it is 0.6.2,
then it's a know issue, but it should be fixed (or at least improved a
lot) with tracker 0.6.3, which is already in the repositories.
So if you don't have tracker 0.6.3, update to it and let us know whether
responsiveness
** Changed in: tracker (Ubuntu)
Sourcepackagename: None = tracker
** Also affects: strigi (Ubuntu)
Importance: Undecided
Status: New
--
[gutsy] trackerd vs. strigidaemon
https://bugs.launchpad.net/bugs/147017
You received this bug notification because you are a member of Ubuntu
Bugs,
I updated earlier today so I now have 0.6.3, I'm not sure what i had
before, probably 0.6.2.
Not the problem isn't the responsiveness issue when tracker runs, I know about
that issue and that it's being worked on
separately.
The problem here is specifically that after an install of
I don't know how this could be solved.
One option for this would be to make tracker conflict with strigi, but I
don't think that's a good idea, since they aren't really conflicting
(there's no problem with having both, other than it might be useless).
Also, this would mean either removing strigi
Lowering as this isn't about responsiveness (there's another bug report
for that).
** Changed in: tracker (Ubuntu)
Importance: High = Medium
--
[gutsy] trackerd vs. strigidaemon
https://bugs.launchpad.net/bugs/147017
You received this bug notification because you are a member of Ubuntu
Bugs,
What is controlling launching/quitting of both of these ? They don't
seem to be services in /etc/init.d ...
Maybe best is some kind of script on launch of gnome/kde sessions that check if
both indexers are running,
and asks if the user wants to disable one of them (with an option to not
display
trackerd should be started by gnome-session so should only be started if
you are logged into gnome
likewise strigi should only be started if you log into kde. If you run
kde apps from gnome (or vice versa) then hopefully they wont start each
others indexers?
in the long term both strigi and
Allright, I did suspect the session thing (though I didn't find strigi in the
KDE service manager), but for some strange
reason, trackerd gets loaded on my kde sessions... could be when I launch a
gnome app as I have evolution auto
loaded, or could have been from saving a session where it was
Let us know when you check it.
** Changed in: tracker (Ubuntu)
Status: New = Incomplete
--
[gutsy] trackerd vs. strigidaemon
https://bugs.launchpad.net/bugs/147017
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
It's the file
/usr/share/autostart/trackerd.desktop
which autostarts trackerd for kde and
/etc/xdg/autostart/trackerd.desktop
which autostarts trackerd for GNOME/XFCE.
If Ubuntu doesn't want to autostart trackerd for KDE, simply remove
the former file from debian/tracker.install.
--
Why is
Check ~/.kde/Autostart, ~/.local/Autostart and another directory (cant
recall its name) within .kde
--
[gutsy] trackerd vs. strigidaemon
https://bugs.launchpad.net/bugs/147017
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
14 matches
Mail list logo
