Nautilus file search gives no results (but works as root)

[SB]

Binary package hint: nautilus

if i run nautilus as a normal user, the search feature does not work at all. no matter in which directory i am, the search engine does not find anything, it always has zero results. if i run nautilus as root, however, the search feature works just fine. so i'm guessing this must have something to do with permissions, but i don't really see how since it doesnt even work in my home directory...

this bug appeared after i upgraded from karmic to lucid beta yesterday. i'm using version 2.29.92.1 of nautilus.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.29.92.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Mar 28 00:29:24 2010
ExecutablePath: /usr/bin/nautilus
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: nautilus

[Sean McColgan (mccolgst-gmail)]

I cannot reproduce this error. I have version 2.30.0 in lucid beta. Perhaps having that version fixes the issue?

[SB (stefan-bommer)]

no, it doesn't. it's still impossible to do a search as a normal user, while the search as root works flawlessly.

are there any pieces of information i can provide you with other than what i have already posted that could help you figure out what's going on?

[SB (stefan-bommer)]

*bump*

[Pedro Villavicencio (pedro)]

Thanks for the report, please create a new user and test there, there's problem something broken on your user configuration rather than this being a bug. Please also attach your ~/.xsession-errors file to the report. thanks.

[SB (stefan-bommer)]

i've tried your suggestion with a new user but it didn't help: i wasnt able to search my folders through nautilus with a clean profile either.

i think i've isolated the error message: in both the old and the new profile, nautilus reports the following error in the xsession-errors file after trying to perform a search:

** (nautilus:1651): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed

this message doesnt occur when running nautilus as root.

[Gilles Daigle (gilles-daigle)]

I have the exact same problem. I haven't been able to use search since I updated.
Just tried nautilus as root and it works.
So now, this bug affect more than one person

[Jakob Unterwurzacher (jakobunt)]

Note that this is a regression from Karmic (i see it on my system that was updated a few days ago, in Karmic it worked).

[Chris Coulson (chrisccoulson)]

Are you using tracker by any chance?

[Jakob Unterwurzacher (jakobunt)]

Looks like i did. There were several *tracker* processes unning. I uninstalled tracker, now i'm getting some results again.

[SB (stefan-bommer)]

same here. i never used tracker but the daemon was running. after killing tracker, i get results again.

i'm still wondering why this never happened earlier because it seems to me like i'd seen tracker processes running in karmic as well without inhibiting the nautilus search...

anyway, thanks for the hint, i can now work productively with nautilus again!

[Chris Coulson (chrisccoulson)]

Nautilus changed in Lucid to use tracker for searching if it's installed (previously it was a build option that we disabled). Anyway, closing this, as it's not a Nautilus bug