After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685014 - No search results returned (if Tracker supported but not running)
No search results returned (if Tracker supported but not running)
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File Search Interface
3.6.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-28 02:08 UTC by Mantas Mikulėnas (grawity)
Modified: 2012-09-28 15:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mantas Mikulėnas (grawity) 2012-09-28 02:08:27 UTC
In recent Nautilus releases (3.5.x, 3.6.0, up to the latest Git version 302fb4d), entering anything into the search box returns no results; the status bar forever remains at "Searching..."

Nautilus also prints the following messages 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

(In reply to bug 681587 comment #5)
> @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).

The first warning, unfortunately, is about failure to connect to Tracker, so "nautilus_search_provider" functions are not reached with fatal_warnings enabled. (I have libtracker-sparql installed, but not Tracker itself.)

If I recompile with --enable-tracker=no, simple search starts working fine...
Comment 1 Cosimo Cecchi 2012-09-28 15:30:33 UTC
Pushed a fix for this to git master now, thanks for the report.