As I said, this happens "sometimes" and was "here since tribe5", hence I think since tracker 0.6.1 at least.
"Sometimes", more precisely, means once every two or three days, and with reboots in between. The workaround, you're right, is to kill trackerd and restart it, but it's surely a bug. Maybe the running tracker daemon stayed there from an old session? If so, tracker should record the display and the pid of each instance in a temporary file, so that if you are going to start a new copy on the same display, you know you can kill it. -- tracker searches sometimes don't work, reporting "Process /usr/bin/trackerd exited with status 0" https://bugs.launchpad.net/bugs/148118 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
