Bug 206518

Summary:	when I access to xdmcp via exceed, my x server hangs
Product:	Red Hat Enterprise Linux 3	Reporter:	Claudio Pera <cpera>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.8	CC:	andre.tenbohmer, cpera
Target Milestone:	---
Target Release:	---
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2007-0411	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-06-11 18:53:53 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:
Bug Depends On:	198257
Bug Blocks:

Description Claudio Pera 2006-09-14 19:55:07 UTC

Description of problem:when I access to my red hat linux 3.8 ws via exceed, and
logout that remote xdm, when I want to login to my console via graphics
gdmgreeter I can't access. the sames occurred if I am into the console in gnome,
I can't run any other program. But, if I run (for example xclock) the command
xclock with the display option activated (xclock -display `hostname`:0) the
command is succesfull. can you help me?


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


How reproducible: always


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Andre ten Bohmer 2006-10-19 15:22:24 UTC

Simmular Exceed, gdm and xdmcp problems on a Red Hat Enterprise Linux AS release
3 (Taroon Update 8) x86_64 (AMD Opteron) HP DL-145-G1 server :
]# cat .xsession-errors
XIO:  fatal IO error 104 (Connection reset by peer) on X server
"bc000001253.x.x:0.0" after 240 requests (236 known processed) with 0 events
remaining.
Clients are able to connect and work without any problems on a HP DL-380-G3 x86
Red Hat Enterprise Linux AS release 3 (Taroon Update 8) with simmular X/gdm
configuration

Comment 2 Ray Strode [halfline] 2006-10-19 16:03:14 UTC

Hi guys,

This problem has been identified and the fix is currently being evaluated for
potential inclusion in a future Red Hat Enterprise Linux 3 update.

Comment 7 Red Hat Bugzilla 2007-06-11 18:53:53 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0411.html