Bug 116438

Summary: Kfind crashes when trying to find file containing text
Product: [Retired] Red Hat Linux Reporter: Klyf Fenderson <klyf>
Component: kdebaseAssignee: Petr Rockai <prockai>
Status: CLOSED CANTFIX QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-18 18:11:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The Backtrace output from KDE Crash Handler. none

Description Klyf Fenderson 2004-02-21 01:18:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/3.0 (X11; Linux i686; U) Opera 7.23  [en]

Description of problem:
When I try to do a content search ("containing text") as either root 
or user with the file name as the wild card "*", kfind crashes.

The application KFind (kfind) crashed and caused the signal 11 
(SIGSEGV).

Output of the backtrace is attached.


Version-Release number of selected component (if applicable):
kdebase-3.1-15, kdeutils

How reproducible:
Always

Steps to Reproduce:
1.  Start kfind from either the start menu or a konsole.
2.  Put the wild card '*' in the "Named" field.
3.  Switch to the "Contents" tab, type a string of text in the 
"Containing text" field.
4.  Click on the "Find" button.
    

Actual Results:  Kfind crashes (disappears, rather than locking up) 
and the KDE Crash Handler pops up.

Expected Results:  It should have scanned for files containing the 
desired text string.

Additional info:

Comment 1 Klyf Fenderson 2004-02-21 01:20:46 UTC
Created attachment 97897 [details]
The Backtrace output from KDE Crash Handler.

Comment 2 Klyf Fenderson 2004-02-21 17:09:29 UTC
Okay, it seems to work okay if I use .* instead of * in the file name 
field.

Comment 3 Petr Rockai 2006-07-17 18:34:26 UTC
This bug is reported against old release of Red Hat Linux or Fedora Core 
that is no longer supported. Chances are that it has been already fixed in 
newer Fedora Core release. If you still experience the problem with 
current release of Fedora Core, please update the Version field (you may 
need to switch Product to Fedora Core first) in the bug report and put it 
back to NEW state.

Comment 4 Bill Nottingham 2006-10-18 18:11:13 UTC
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
http://www.redhat.com/rhel/migrate/redhatlinux/.

Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
If this issue is still present in a current Fedora Core release, please
open a new bug with the relevant information.

Closing as CANTFIX.