On Thu, 02 Dec 2021 at 21:43:30 +0000, Ian Campbell wrote: > On Tue, 2021-11-30 at 11:03 +0000, Simon McVittie wrote: > > It seems that this bug occurs when GtkSearchEngineModel is the only > > backend returning results, so a workaround is to have have a second > > search backend available (I don't know what this means specifically, but > > presumably a full GNOME desktop might have a second backend, otherwise > > this failure mode would have been seen more often). > > There seems to be a network filesystem component too, which I'd guess > reduces the likelihood of it being seen quite so often as it would > otherwise be.
I think it might work something like this: * it is sufficient to have a single working backned; * if you're on a "full" GNOME desktop, then you have Tracker, which provides a separate search backend; * or if you're on a local filesystem, then GTK's built-in GtkSearchEngineSimple can be used (it disables itself automatically on remote filesystems because that would be slow); * but if you're on NFS *and* you don't have Tracker, then you can experience this bug smcv