Bug 215235 (daniel-magarzo)
Summary: | The Search function in Nautilus 2.16.2 doesn't work for files living in the home dir | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | M Daniel Rodriguez Magarzo <4.magarzo> |
Component: | beagle | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-22 10:58:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
M Daniel Rodriguez Magarzo
2006-11-12 18:34:25 UTC
Did the beagle first indexing run have time to finish on the problematic machine? (In reply to comment #1) > Did the beagle first indexing run have time to finish on the problematic machine? Sorry, but I don't catch what is exactly what you mean in your question..; do you mean whether beagle finds anything (on the laptop)? If that's the question, the answer is _yes_, it finds mostly web pages (visited) that I suppose it is indexing, but not files (nor anything) placed in my $HOME. Did you mean that? If not, please, suggest me the exact commands, etc. and I'll be pleased to do it. p.s.-I'm not familiar with beagle (commands) at all. Daniel First of all, upgrade to the new beagle update that fixes a hang in beagle. Then, after log in and a search doesn't finish, use beagle-index-info and beagle-status to see what beagle is doing and if it has finished the first indexing run it does after login. Before that is done (the first time) you won't get all results. Well, well.. The system was updated yesterday with yum, that update involved the beagle_update one you announced. A search using the nautilus embebed applet did not give any variation with respect to the older behaviour. Then, I've shut down the laptop with no more tries. That was yesterday at midnight. Today, after booting again, and doing through yum a new general update available (nothing to do with beagle this time), I tried again with the same procedure..., and yes! Now it finds whatever it should. BTW, also beagle by itself is now able to find files in my $HOME, as the Nautilus Search applet does, everything speedy, alright. The only thing I did was to wait for the new version of the package in the _core_ repo (instead of to take it from _testing_), and to update the system regularly. With the command "beagle-index-info", the output shows me that it is working OK, RSS readers, evolution mails, etc,.. E.g. I suppose this one is completely OK: ---------------------- Name: documentation Count: 21231 Indexing: False -------------------------------- And with the command "beagle-status", it gives me thins like this: ----------------------------- Scheduler: Count: 575 Status: Waiting for the next trigger time Pending Tasks: Scheduler queue is empty. Future Tasks: Maintenance 0 (22/11/2006 0:45:22) Optimize EvolutionMailIndex Hold until 22/11/2006 20:38:56 -------------------------------------- Summarizing, I think that the issue was solved with the arrival of the new version. Yeah, i think the indexing progress just hanged for you before due to the X thing. So, how do you explain that from a new FC install would behave in that way? And why that didn't happen on my desktop system, also with a FC6 fresh install? Ummmmm...???:-| Thank you. How is a new install different? There was a thread race that sometimes caused beagle to hang and stop indexing. |