Bug 750802 - Mistake on command line results in searching yum db
Summary: Mistake on command line results in searching yum db
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Roman Rakus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 12:08 UTC by Lukáš Czerner
Modified: 2014-01-13 00:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-02 13:35:20 UTC
Type: ---


Attachments (Terms of Use)

Description Lukáš Czerner 2011-11-02 12:08:53 UTC
Description of problem:

Every time when I make an mistake when writing command on the command like, it will try to search this "obviously" non-existing command in the repository. It will take several seconds to finish, resulting in unwanted annoying behaviour.

How reproducible:

just type command which does not exist on your system.

Actual results:

It will lag for several seconds, trying to find the command in the repository.

Expected results:

finish immediately with "command not found" error without doing any time consuming operation on background.

Additional info:

Please, this is highly annoying behaviour. 99.9% of the time I hit this is caused just by misspelling error when typing the command. There is really no need to have something which is in most cases absolutely useless. Thanks.

Comment 1 Roman Rakus 2011-11-02 13:35:20 UTC
It's due to command_not_found_handle function. It is distributed in package `PackageKit-command-not-found'.

Comment 2 Lukáš Czerner 2011-11-02 15:04:44 UTC
Well, I still think it is a bug. To be more specific, the fact that this feature is obviously enabled by default is a bug, since it is causing more pain than it is useful.

The bug should have been transferred to the PackageKit component, rather than closed.


Note You need to log in before you can comment on or make changes to this bug.