GNOME Bugzilla – Bug 681587
Searching in nautilus produces no results
Last modified: 2012-10-29 12:50:19 UTC
In the nautilus search bar if I type the name of a file (or part of that name) and press enter (or wait) I get no results in the window. This seems to happen in any folder. Installed Packages Name : nautilus Arch : x86_64 Version : 3.5.4 Release : 3.fc18
This should be fixed already in 3.5.5. Can you confirm please?
I see this if I select All Files for the search (using 1:3.5.5-0ubuntu3), but it works ok within the current folder. See downstream bug https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1035091
The originally reported issue is now fixed with 3.5.5. However like Colin "All Files" mode produces exactly the same results as searching within the current folder.
I seem to be hitting a similar bug – or at least similar symptoms (no results, stuck on "Searching..." forever) in 3.5.5, 3.5.91 and even 3.6 ... Nautilus also prints the following to stderr: (nautilus:1202859): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:1202859): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (nautilus:1202859): CRITICAL **: nautilus_search_provider_set_query: assertion `NAUTILUS_IS_SEARCH_PROVIDER (provider)' failed ** (nautilus:1202859): CRITICAL **: nautilus_search_provider_start: assertion `NAUTILUS_IS_SEARCH_PROVIDER (provider)' failed ** (nautilus:1202859): CRITICAL **: nautilus_search_provider_stop: assertion `NAUTILUS_IS_SEARCH_PROVIDER (provider)' failed ** (nautilus:1202859): CRITICAL **: nautilus_search_provider_set_query: assertion `NAUTILUS_IS_SEARCH_PROVIDER (provider)' failed ** (nautilus:1202859): CRITICAL **: nautilus_search_provider_start: assertion `NAUTILUS_IS_SEARCH_PROVIDER (provider)' failed Note that I do not have Tracker installed, but if I understand things correctly, Nautilus should use its built-in search provider anyway. [Should this go in a separate bug report?]
@Mantas: yes, please file that as a separate bug report, possibly with a backtrace before the first warning (set the environment variable G_DEBUG=fatal_warnings before running it in gdb to make it break at the first warning). @Stef: can you still see the bug you mention in comment #3 with 3.6.0 or git master?
I believe this can be closed as FIXED now.