Bug 800727 - PackageKit-command-not-found not working in F17?
Summary: PackageKit-command-not-found not working in F17?
Keywords:
Status: CLOSED DUPLICATE of bug 643778
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 05:07 UTC by Jens Petersen
Modified: 2012-10-31 15:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-31 15:19:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jens Petersen 2012-03-07 05:07:41 UTC 
Description of problem:
PackageKit-command-not-found doesn't seem to be doing anything
for me excepting slowing down "command not found errors".

Version-Release number of selected component (if applicable):
PackageKit-command-not-found-0.7.3-1.fc17

How reproducible:
every time

Steps to Reproduce:
1. install Fedora 17 Nightly Live
2. $ fedpkg
  
Actual results:
bash: fedpkg: command not found

Expected results:
PK to to offer to install fedpkg

Additional info:
I still feel it might be better not to install
PackageKit-command-not-found by default.
Comment 1 sashker 2012-05-08 12:14:52 UTC 
To resolve this error - you need edit /etc/Package/CommandNotFound.conf and change MaxSearchTime parameter. In my case - I set this parameter to 15000, and PackageKit-command-not-found now works fine, but very slow. PackageKit-command-not-found is not use yum cache and searching all names from the network.
Comment 2 Elad Alfassa 2012-10-31 15:19:41 UTC 

*** This bug has been marked as a duplicate of bug 643778 ***
Note You need to log in before you can comment on or make changes to this bug.