Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 85524 - konqueror does not cause fam to be started
Summary: konqueror does not cause fam to be started
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kdebase
Version: phoebe
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-03 22:19 UTC by Michael Wardle
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-03-03 23:10:19 UTC


Attachments (Terms of Use)

Description Michael Wardle 2003-03-03 22:19:42 UTC
Description of problem: 
Konqueror can (and should?) use FAM to find out when a file has changed 
and immediately refresh the file list.  When I log in to a KDE session and 
start Konqueror, "ps" does not show FAM as having been started, despite 
the portmap, xinetd, and fam services all being enabled.  When a file is 
changed, Konqueror takes a few seconds to reflect this change. 
 
Version-Release number of selected component (if applicable): 
fam-2.6.8-9 
portmap-4.0-52 
xinetd-2.3.10-4 
kdelibs-3.1-7 
kdebase-3.1-7 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. Install Phoebe 3 
2. Start a KDE session 
3. Open Konqueror 
     
Actual results: 
fam is not shown in the process list 
 
Expected results: 
fam is shown in the process list 
(it should be started on demand using xinetd) 
 
Additional info: 
This is a mostly default install of Red Hat Linux 8.0.94 (Phoebe 3). 
The FAM configuration has not been changed, and FAM works fine 
in conjunction with Nautilus.

Comment 1 Ngo Than 2003-03-03 23:10:19 UTC
Fam is disable in KDE by default. It has caused many problem in earlier KDE
version. KDirWatch works fine in KDE. 


Note You need to log in before you can comment on or make changes to this bug.