Comment 7 for bug 8195

Yes, that works. Thank you!

However when running sudo updatedb I got:

warning: updatedb: could not open database: /var/lib/slocate/slocate.db: No such
 file or directory

Then a slocate.db was created. There is a daily cronjob that runs updatedb. The
problem is that my box is a laptop so it isn't up 24/7 (it is usally up around
midnight when cronjobs traditionally get run). Still it seems that the updatedb
has not been run.

This results in behaviour that from a user perspective seems broken. In my
humble opinion this bug can be closed when:

A. Updatedb is certain to get run early on. Maybe with low nice post install?

or

B. The slower "show more options" search is run by default. Allthough it lists
files that contain the search string (instead of files that have the search
string in their name), it is intelligent enough to list the files that have the
search string in their name first. The user might think there is lots of "noise"
in the search but that is (again IMHO) better than not producing any results at
all.