Bug 750857

Summary:	Mistake on command line results in searching yum db
Product:	[Fedora] Fedora	Reporter:	Lukáš Czerner <lczerner>
Component:	PackageKit	Assignee:	Richard Hughes <hughsient>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	fedora, hughsient, jonathan, rvitale, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 14:34:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lukáš Czerner 2011-11-02 15:07:26 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. Apparently this is caused by function command_not_found_handle distributed in package PackageKit-command-not-found . I would be nice to not have this installed by default since it is causing more pain than it is useful.

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 Russell Harrison 2012-02-11 19:38:54 UTC

If you uninstall the PackageKit-command-not-found package this search will not happen.

Comment 2 Lukáš Czerner 2012-02-12 10:56:09 UTC

How about removing this nonsense from the default configuration ? :)

-Lukas

Comment 3 Fedora End Of Life 2013-01-16 13:42:14 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 14:34:38 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.