bash command not found

[Richard Hughes]

On 2 June 2011 12:35, Chris Tyler <chris at tylers.info> wrote:
> - If pk-c-n-f times out on fetching file list metadata, it seems to
> silently stop trying to suggest packages. I've seen this on slow
> connections and disconnected machines. IIRC, fetching recent metadata
> (e.g., by using yum to find a file-level dependency) restores pk-c-n-f's
> operation.

This is by design. I lost count of the number of bugs opened against
PackageKit-command-not-found where yum would happily go and download
the latest metadata and take 3 minutes to return to the bash prompt,
even when yum is told to work from a cache.

If you want the old behaviour back, just up the timeout in
/etc/PackageKit/CommandNotFound.conf

# Controls how long we should allow the user to wait when searching for
# additional packages.
# This can be set to very small numbers to avoid distracting the user, although
# some entries may not be found if the caches need refreshing or metadata
# downloading.
#
# Value is the number of milliseconds to allow.
#
# default=2000
MaxSearchTime=2000

Richard