nautilus search doesn't find things in certain directories

hmmm... more weirdness

if i search my Desktop for "ogg", nautilus DOES find my only Ogg file, myvi.ogg.

if i search my Desktop for "jpg", nautilus doesn't find any of my .jpg files. it also won't find .pdf files. searching other parts of the name of the pdf & jpg files doesn't work either.

searching my Desktop for "t", nautilus finds a file down inside of a subdirectory of ~/Desktop.

You would get better results with something like *.ogg

searching ~/Desktop for "*.ogg" doesn't find anything while searching for "ogg" does find myvi.ogg

i booted the Ubuntu 6.10 CD and got similar results when i mounted my hard disk and started searching it

then, i rebooted to my hard disk and noticed that i wasn't booting the latest kernel by default (i've recently updated /boot/grub/menu.lst and the default was wrong)

using the latest kernel, 2.6.17-11-generic, instead of the previous one, 2.6.17-10-generic, solves the problem

hmmm...

it appears to be a problem involving truecrypt

if i have a truecrypt volume mounted, nautilus search doesn't work properly (e.g. searching for "jpg" finds nothing in my home directory)
if no truecrypt volume is mounted, nautilus search finds all my jpg files just fine

locate is a nice utility
Fire up the terminal, and type in; 'locate log'
or whatever you want to look up.

yes... there's usually a CLI work-around for any problem... i'm particularly fond of the find command, something i used to be a whiz at back in the olden days... why do people bother with GUIs anyways?

my goal is "to use nautilus to search for files."

nautilus doesn't appear to be working as i expect, based on the gnome desktop help page "Searching For Files".

i'm not looking for a work-around (CLI or GUI), i'm reporting a problem, which is why i reported the problem via the nautilus help menu. and the problem report ended up here.

i'm hoping someone can either tell me there's a bug or educate me as to the true functionality of nautilus searching.

i've upgraded to feisty and i'm still getting inconsistent results.

i think i've figured it out

after more investigation it appears to be a bug

the search stops when it reaches a directory that it can't read

and the search appears to be run in directory order, so what files are found depends on exactly where the first unreadable directory exists in the directory

lol: actually, this is the bug report i filed

http://bugzilla.gnome.org/show_bug.cgi?id=433105

i think it might be related to #347386

Hi Marlon Nelson,

So what is the disposition: Nautilus bug exists, but what is the workaround.
Thx, <email address hidden>

Joseph,

How are you reproducing the bug?

Long ago, I submitted a patch that fixed the problem I was having. It was committed, but I don't know if the code survived. A major subsystem was being rewritten/replaced at that time (GVFS?).

Presently, I'm having trouble reproducing the problem. At first, I thought it still existed but then I stopped using wildcards (e.g. *.txt) in the search pattern, search results started appearing. Maybe wildcards should work, but that would be a different bug to report.

Marlon

I have *.JPG files that nautilus does not find...
I select a specific folder having said files & nautilus does not report...\
It will find the files with the full name search, but not with the wildcard
(*)
usage...So I suppose the wildcard processing seems to be the issue...Joseph
==============================================================

On Tue, Apr 20, 2010 at 6:15 AM, Marlon Nelson <
<email address hidden>> wrote:

> Question #5168 on nautilus in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/nautilus/+question/5168
>
> Marlon Nelson posted a new comment:
> Joseph,
>
>
> How are you reproducing the bug?
>
> Long ago, I submitted a patch that fixed the problem I was having. It
> was committed, but I don't know if the code survived. A major subsystem
> was being rewritten/replaced at that time (GVFS?).
>
> Presently, I'm having trouble reproducing the problem. At first, I
> thought it still existed but then I stopped using wildcards (e.g. *.txt)
> in the search pattern, search results started appearing. Maybe
> wildcards should work, but that would be a different bug to report.
>
>
> Marlon
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

Joe Giuliano has chosen to send you a free movie ticket, up to $10 value.

Sit back, relax, and enjoy! In an effort to spread the word about our great products we are allowing our members to send free movie tickets to their selected friends at no charge to our members. This time Joe Giuliano chose you! To redeem your movie ticket and receive deal notifications follow the link below.

http://homerun.com/email_gift/b5f27d7859?_e=0cd1ca75

Enjoy, this one is on us.

The HomeRun Team

If you prefer not to get promotional email from HomeRun, visit http://homerun.com/unsubscribe?_e=0cd1ca75

Brought to you by HomeRun, PO Box 26049, San Francisco, CA, 94126, USA