Comment 39 for bug 131983

I agree, trackerd should NOT be enabled by default. However nice it might be in theory, right now it's much too buggy and hogs too much memory and disk.

Frankly I'm amazed that it got into a default install of Gutsy in this state. Jamie McCracken, do you not care about all the users who complain about it? Would you not rather disable it by default until it's stable and people are happy with it, than breaking the Ubuntu experience for millions of innocent users and giving trackerd a VERY bad name? (search Google for trackerd if you don't believe me)

I don't think Ubuntu releases are a good place to beta-test new software on anyone, especially not if it's been tested in testing and people have asked for it to be removed from the final release and those requests have been ignored.

On our first Gutsy system I discovered trackerd eating 100% cpu... by sitting in a loop of continuous SIGSEGV. Catching SIGSEGV is usually a bad idea, and then reinstalling the signal handler is even worse. Please fix that.

[pid 13171] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 13171] sigreturn() = ? (mask now [])
[pid 13171] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 13171] sigreturn() = ? (mask now [])
[pid 13171] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 13171] sigreturn() = ? (mask now [])
[pid 13171] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 13171] sigreturn() = ? (mask now [])
[pid 13171] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 13171] sigreturn( <unfinished ...>