Bug 76153

Summary:	Errors starting gedit from command line
Product:	[Retired] Red Hat Linux	Reporter:	Gary Fidler <gfidler>
Component:	fam	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-11-30 15:39:38 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:

Description Gary Fidler 2002-10-17 16:56:23 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
Starting gedit from the command line (gnome-terminal), I get 21 lines on the
console like the following:

FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
...

The editor seems to work correctly after that.

Version-Release number of selected component (if applicable):
gedit-2.0.2-5

How reproducible:
Always

Steps to Reproduce:
1. Type gedit from the command line
2.
3.
	

Actual Results:  FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0
FAMOpen failed, FAMErrno=0


Expected Results:  No console output

Additional info:

Comment 1 Alexander Larsson 2002-11-05 12:19:08 UTC

try upgrading to the xinetd errata and see if that fixes it.

Comment 2 Gary Fidler 2002-11-05 16:09:28 UTC

How would I do this?  RHN says my system is up-to-date.  RPM shows xinetd-2.3.7-2.

Comment 3 Alexander Larsson 2002-11-06 08:15:46 UTC

Hmmm. Strange. I was sure there had been an xinetd errata.
There is a bug with xinetd that fails to start fam if you've enabled
tcp-wrappers. If this is that problem you should have gotten some log messages
about not being able to get peer address.

Other possible causes: You disabled one of portmap, fam, xinetd. You've
firewalled off one of the above apps for local access.

Comment 4 Alexander Larsson 2003-08-12 12:36:10 UTC

Have you verified this is not one of the possible causes listed above?

Comment 5 Daniel Veillard 2004-11-30 15:39:38 UTC

This is more than one year old and I didn't got any error report
about this since, I think this can safely be closed.

Daniel