Uh, it's *not* enabled by default? Is it carried over from Gutsy then? I
never had an issue with it until I dist-upgraded from Gutsy to Hardy,
but I sure didn't intentionally enable it. I have removed it after
finding this.
My problem: not a huge amount of code/text files in my home directory
(at
i can confirm this bug with version 0.6.6 and ubuntu 8.04 updated. When
I disconnect the cable the cpu keep indexing, even if the settings for
index-stop on battery state are marked.
--
Tracker should not be enabled by default until it doesn't clobber everything
Tracker isn't enabled by default in Hardy. This decision was made by the
Technical Board and will be reconsidered in the future.
** Changed in: tracker (Ubuntu)
Status: Fix Committed = Fix Released
--
Tracker should not be enabled by default until it doesn't clobber everything
UP!
I'm testing Tracker again on Hardy alpha.
I have about 100GB of data in my home... mixed videos,images,music and text
files.
I'm not a developer and I have disabled indexing of ~/Downloads/SRC that is the
folder where I keep sofware sources.
I've also removed .cache/tracker before starting
trackerd is niced +19 so cpu will nose dive to 1% if another app uses
cpu. Indexing needs lots of cpu which no indexer can escape from.
Switching to another will not change this (unless you consider slowing
indexing to such a crawl that it takes days to index which you can do
already in
...In any event, next version of tracker (due this week) now pauses
automatically during merges...
I'm pleased to read about this new feature, I've talked about this here:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/160646/comments/1
I really hope to see this working in Hardy.
Thanks
Jamie McCracken wrote:
trackerd is niced +19 so cpu will nose dive to 1% if another app uses
cpu. Indexing needs lots of cpu which no indexer can escape from.
Switching to another will not change this
(unless you consider slowing indexing to such a crawl that it takes
days to index which you
On Tue, 2008-02-19 at 17:40 +, Jamie Lokier wrote:
Jamie McCracken wrote:
trackerd is niced +19 so cpu will nose dive to 1% if another app uses
cpu. Indexing needs lots of cpu which no indexer can escape from.
Switching to another will not change this
(unless you consider slowing
Correction:
I meant Allocate on flush instead of pre-allocation
http://en.wikipedia.org/wiki/Allocate-on-flush
This stuff really rocks with indexers!
--
Tracker should not be enabled by default until it doesn't clobber everything
https://bugs.launchpad.net/bugs/132741
You received this bug
kdvolder: this is a little off topic, but you might like ack:
http://petdance.com/ack/
Lots of options for whittling down the search list, including regexps on
the filenames.
Matt
--
Tracker should not be enabled by default until it doesn't clobber everything
I'm having similar issues, they started after I began having files in my
home directory. (Before it was as good as empty and no big problems).
However, besides the performance bug, there's also a usability bug in tracker.
I can't use it because what I want most of the time, is simply search for a
This might be one of the contributors to the infamous Load_Cycle_Count bug (for
some people) :
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/17216
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695
--
Tracker should not be enabled by default until it doesn't clobber
I've had the same problem with both tracker and beagle and have removed
them both. Unfortunately the latest version of Nautilus requires tracker
to do any kind of searching. This is really unacceptable: It is totally
inadequate to limit searches to a directory small enough for tracker to
handle.
Hi,
I have a similar problem.
First, I'm new to Ubuntu and I have no technical knowledge whatsoever.
I upgraded to Gutsy from Feisty as soon as it was released and
everything was fine but yesterday I got a message at startup that the
disk volume at / is 100% full . After some research I
I installed the 0.6.3 version and indeed things seem to work better now,
as far as resource usage is concerned at least. It spent a couple of
hours indexing things, and has now stopped. It doesn't index my e-mails
(the setting to do so is turned on), and the stuff that it does index
isn't
It is still really annoying that I have no way of knowing how long it
will hog 50% of my CPU and use a lot of I/O.
using 0.6.3...
--
Tracker should not be enabled by default until it doesn't clobber everything
https://bugs.launchpad.net/bugs/132741
You received this bug notification
Xvani,
We are just about to release a new version with a notification icon that
shows progress, status, stats and allows manual pausing too.
hope that helps as soon as 0.6.4 hits repos...
--
Tracker should not be enabled by default until it doesn't clobber everything
My system remain painfully sluggish with tracker 0.6.3
--
Tracker should not be enabled by default until it doesn't clobber everything
https://bugs.launchpad.net/bugs/132741
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
tobias
did you killall -9 trackerd before running tracker 0.6.3? (old version
will still be running)
you would be the first to report sluggishness with 0.6.3 as a
significant number have confirmed it does not produce any significant
slowdowns
can you get me log file in ~/.local/share/tracker
Lars,
tracker 0.6.3 has just been added to gutsy - pls upgrade and retest and
confirm if ok
0.6.3 will automatically reindex for you
It is not in the *beta* version so you must upgrade to get it
--
Tracker should not be enabled by default until it doesn't clobber everything
I've just installed the gutsy beta on a laptop (Fujitsu-Siemens P7120,
1.2 GHz, 1 GiB of RAM), and until I removed tracker, it was unusably
slow: dragging a mail from one folder to another in Evolution would
routinely take 10-15 seconds, for example. After removing tracker, it's
happens in an
We have done lots of optimisations and index merging which should cure
this problem
Once tracker 0.6.3 is in gutsy pls retest and reopen bug if problems
persist
** Changed in: tracker (Ubuntu)
Status: Confirmed = Fix Committed
--
Tracker should not be enabled by default until it
My objection to the won't fix status is that fixing these problems may
be difficult. Until we know they are fixed, we don't know if it's
possible to fix them in time for the Gutsy general release. It's just
wishful thinking to say this will be in Gutsy final (soon) and the
performance issues
Emilio wrote:
iwe are shipping tracker because we can and we are fixing these bugs.
If we couldn't, we wouldn't ship it/i
That's great. If you could post a comment when you are happy with a
version in the Gutsy repository, that would be helpful. Those of us who
have a problem with the older
I see your point, and now I think I made a mistake closing it. We can
close this bug report as soon as those issues are fixed, and if they
aren't, then we should disable tracker, as this bug says.
Sorry for my error, it won't happen again.
** Changed in: tracker (Ubuntu)
Status: Won't Fix
We will notify you when its ready to confirm if this bug is fixed
To clarify a few issues:
1) we are reverting back to qdbm over sqlite for the index as its much faster
at inserts and causes less IO
2) The issue with fsync/sqlite no longer applies
3) we are increasing cache size such that each
I'm closing this bug report, since this is a development version of
Ubuntu, and it's likely to eat your dog or fire your house at some point
;)
Seriously, if something has a bug, the solution isn't to remove it from
the distro, but to fix it. And that's what we are going to do, instead
of
I'm closing this bug report, since this is a development version of
Ubuntu, and it's likely to eat your dog or fire your house at some point
;)
Gutsy beta freeze is happening in two days and general release is less
than a month away. The system should be stable and working properly for
most
Darik Horn wrote:
I'm closing this bug report, since this is a development version of
Ubuntu, and it's likely to eat your dog or fire your house at some point
;)
Gutsy beta freeze is happening in two days and general release is less
than a month away. The system should be stable and
The tracker team is committed to solving this issue and it is making
good progress...
If, at the end of the day, tracker does not provide a good enough
experience for the majority of users then it will have to be pulled (and
that is true for just about any package in ubuntu)
--
Tracker should
i have 75 mb in .cache/tracker --
--
suggestion:
for beagle an icon was added in the right down corner of the screen to switch
it off and on.
could you do something similar for tracker - and allow user to switch it off
immediately when they have the impression it is interfering. and then switch
Andrew,
Its highly unlikely that its tracker's fault with such a small db (if
you have 75mb free RAM then entire db would be cached in memory by the
kernel)
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/131094
hopefully the kernel devs can fix that as I dont think
i did not want to be negative in my comment - indexing is very
important, but also very difficult.
i tell you my experience yesterday (with version 0.6.2.0)
i was searching a mailbox in balsa - and it did not make progress
i was installing software (apg-get probably) and it seemed to stall such
balsa and other mboxes are not supported yet - they are planned
iowait times can stall your desktop - use vmstat 1 and look at last
column wa. This is the percentage of cpu thats idling waiting for IO -
consistently high values 90+ will stall other apps
high iowai could be due to the size of
i observe the same - tracker is running with nice 19, but it is still
hugging the system such that it is unusable when tracker starts. (my
indexing is seeming completely done )- but any start up the system is
unusable for a couple of minutes (this is especially when i sit there
and want to use
There is an index delay (default 45 secs) in tracker-preferences - feel
free to increase this as well as the cpu throttle
tracker 0.6.2 was a bit buggy (due to our new indexing backend) and
tends to eat all memory - we have fixed this and done some more tuning
and should have a new release soon
** Changed in: tracker (Ubuntu)
Importance: Undecided = High
Status: New = In Progress
--
Tracker should not be enabled by default until it doesn't clobber everything
https://bugs.launchpad.net/bugs/132741
You received this bug notification because you are a member of Ubuntu
Bugs,
A few corrections:
At startup we scan folders only not files - we need folders in order to
place inotify watches on them.
The parent folders mtime alwyas changes whenever a file underneath it
changes so we dont need to scan files unless folder has changed, When we
have a proper kernel
Jamie McCracken wrote:
A few corrections:
At startup we scan folders only not files - we need folders in order to
place inotify watches on them.
The parent folders mtime alwyas changes whenever a file underneath it
changes so we dont need to scan files unless folder has changed, When we
Ok 100Gb is no problem if majority is not text files, docs or source
code - size matters not in those cases
a non-dev will typically have loads of music and video files which will
have negligible footprint on any indexer.
A dev will likely have tons of source code and that will tax any
indexer.
40 matches
Mail list logo
