Description of problem:
$ ma passwd
Command not found.
* Cancelling.. The search was cancelled as it was taking too long to complete.
You can increase the value of 'MaxSearchTime' in /etc/PackageKit/CommandNotFound.conf to change the timeout.
Version-Release number of selected component (if applicable):
PackageKit.i686 0.6.9-4.fc14 @updates-testing
PackageKit-command-not-found.i686 0.6.9-4.fc14 @updates-testing
Steps to Reproduce:
1. as above
as under Fedora 13:
$ ma passwd
bash: ma: command not found
I'm between a rock and a hard place with this functionality. Maybe cancelling should just be silent, I dunno. In rawhide, we'll be using zif for the lookup soon, and so we can do it always with cached data.
I remember a discussion on Fedora 13 mailing list about PackageKit interfering
with standard bash responses.
People were upset about it. It is not a good idea to have it at all.
So Richard and I talked about this today. The consensus we came to is this feature should take a more "zen-like" approach. When the functionality can work seamlessly, it will—making life a lot easier for the user in some cases.
On the other hand, in cases where it can't work seamlessly, it's going to try to act as transparent as possible. It won't print out error messages specific to its failed attempts to help the user, and it will try to mimic what the user would see if it wasn't installed at all.
So the two things mentioned in comment 0 are
1) the error message about MaxSearchTime
2) s/"Command not found"/"bash: %s: command not found"/
(In reply to comment #3)
> So Richard and I talked about this today. The consensus we came to is this
> feature should take a more "zen-like" approach. When the functionality can
> work seamlessly, it will—making life a lot easier for the user in some cases.
> On the other hand, in cases where it can't work seamlessly, it's going to try
> to act as transparent as possible. It won't print out error messages specific
> to its failed attempts to help the user, and it will try to mimic what the user
> would see if it wasn't installed at all.
> So the two things mentioned in comment 0 are
> 1) the error message about MaxSearchTime
> 2) s/"Command not found"/"bash: %s: command not found"/
Thanks from everybody.
Author: Richard Hughes <firstname.lastname@example.org>
Date: Mon Oct 11 14:39:55 2010 +0100
Make the output of command-not-found match the bash builtin. Fixes rh#641311
[hughsie@localhost ~]$ powerttop
bash: powerttop: command not found...
Similar command is: 'powertop'
[hughsie@localhost ~]$ java2c
bash: java2c: command not found...
[hughsie@localhost ~]$ xwrite
bash: xwrite: command not found...
Similar command is: 'write'
[hughsie@localhost ~]$ kwin
bash: kwin: command not found...
Install package 'kdebase-workspace' to provide command 'kwin'? [N/y]
PackageKit-0.6.10-2.fc14 has been submitted as an update for Fedora 14.
PackageKit-0.6.10-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update PackageKit'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/PackageKit-0.6.10-2.fc14
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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: