Bug 147772 - kfind doesn't kill its process
Summary: kfind doesn't kill its process
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-11 03:36 UTC by Kim Lux
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-05-18 12:59:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Kim Lux 2005-02-11 03:36:25 UTC 
Description of problem: 
 
If one stops kfind before its search is done, it doesn't kill its 
process.  You have to use top or ps to find the process and then 
manually kill it.  
 
 
Version-Release number of selected component (if applicable): 
 
kfind -v 
Qt: 3.3.3 
KDE: 3.3.1-2.6.FC3 Red Hat 
KFind: 2.0 
 
How reproducible: 
 
every time ? 
 
Steps to Reproduce: 
1. start a search process with kfind. 
2. terminate kfind with the X button. 
3. run top or ps 
   
Actual results: 
 
kfind process is running, usually at high cpu utilization.  
 
Expected results: 
 
kfind shouldn't be running.  
 
Additional info:
Comment 1 Than Ngo 2005-05-18 12:59:57 UTC 
it's already fixed in kdebase-3.3.1-4.3.FC3.
Note You need to log in before you can comment on or make changes to this bug.