tracker-search-tool gets no response

Bug #130937 reported by Matthew Garrett
10
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: tracker

Trackerd is still indexing my drive. I started tracker-search-tool and performed a search. It provided a number of results. Clicking on the emails and text categories worked, but when I clicked on "All Files" I got the following in the console:

META_TILE_ERROR : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
META_TILE_ERROR : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (tracker-search-tool:26050): CRITICAL **: set_snippet: assertion `error == NULL' failed

and a dialogue box saying

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Revision history for this message
Matthew Garrett (mjg59) wrote :

Retrying this (ie, clicking "emails" and then on "All files" again) worked fine.

Revision history for this message
Jamie McCracken (jamiemcc-blueyonder) wrote :

The original happened because of a dbus timeout and the indexer was probably being flushed and mutex lock would temporarily prevent a search from occuring (not much we can do about this but its only likely to happen while attempting a search during initial indexing)

I guess a nicer error msg would suffice for this?

Changed in tracker:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
gagarine (gagarine) wrote :

I confirm this bug.

When you modify the indexing speed (via System-> preferences -> tracker preferences -> performance) to a low value of speed (I test with 17) the result of search comme up very slow and some times (~70% ) this message show up:

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I reduce this value because I'm not interesting by a speed indexing but this value change apparently the speed of search significantly.

Changed in tracker:
status: Incomplete → Confirmed
Revision history for this message
gagarine (gagarine) wrote :

Mmmmh perhaps is not the indexing speed option (because i have this problem after too..).

Revision history for this message
Jamie McCracken (jamiemcc-blueyonder) wrote :

gagarine,

I take it this only occurs during heavy indexing?

(use tracker-status to determine if its indexing)

Revision history for this message
gagarine (gagarine) wrote :

Strange tracker-status:

gagarine@area42:~$ tracker-status
Tracker daemon's status is Idle.
gagarine@area42:~$ sudo tracker-status
tracker-status : aucune connexion au démon Tracker <- no connexxion on tracker demon
Assurez-vous que « trackerd » est lancé avant de saisir cette commande. <- please run trackerd before run this command
gagarine@area42:~$

But i have trackerd on my processus.

How can i restart trackerd manually? Is not on /etc/init.d ?

Revision history for this message
Jamie McCracken (jamiemcc-blueyonder) wrote :

gagarine,

killall -9 trackerd

dbus-launch trackerd

Revision history for this message
gagarine (gagarine) wrote :

Jamie, i can't restart trackerd with the dbus-launch trackerd commande this return a error. But if i kill the deamon and run tracker-search-tool this automatically start the deamon. I don't understand what the deamon is not automatically restarted after any change in preference panel... but this is another bug.

So it not depend of indexing or not (I enabled it and disabled... no very change). If i don't manualy disabled indexing the deamon alway indexing files... (I have ~ 40'000 files and a "fresh" install)

With a speed indexing at 1 and more allowed memory I don't have to much error.

Anyway, if I do a search i have quickly result but if I select a categories like Text or image i wait ~5s to 30s. In this time if I run tracker-status command they return status after ~5 to 30s to.

uname -a:
Linux area42 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux

Revision history for this message
Erdal Ronahi (erdalronahi) wrote :

I can confirm this, too, on several different computers.

Revision history for this message
antani (alessandro-paggi) wrote :

Same problem for me.

Revision history for this message
Rob Frohne (frohro) wrote :

Hi All,

I found this happening soon after I restarted my computer and it would never ever be able to connect until I killed trackerd and then started it up again with tracker-status. After it started I had a little time when I could connect to trackerd that I used to shut off indexing of my Evolution email account. I have about 10 Gigs of email, and get a lot everyday. After doing that, tracker seems to work again. I have also observed slow downs opening a file using any gnome application after this happens. It is as though the application was waiting for the timeout before it would bring up the open dialog window. I suspect this was related. I have had some difficulties with Evolution itself handling my email.

Rob

Revision history for this message
mlaverdiere (mlaverdiere) wrote :

Still the same problem on Intreprid. I don't know what are the cause and what is the solution for this problem, but I doubt that a "nicer error message" would be sufficient if we want to keep up with the "it's just work" orientation.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Is this still a problem in focal or later?

Changed in tracker (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tracker (Ubuntu) because there has been no activity for 60 days.]

Changed in tracker (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.