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 2594 - gdm does not support XDMCP
Summary: gdm does not support XDMCP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gdm
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
URL:
Whiteboard:
: 2270 2538 3927 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-05-06 10:07 UTC by havlik
Modified: 2008-05-01 15:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-10-21 19:01:07 UTC


Attachments (Terms of Use)

Description havlik 1999-05-06 10:07:30 UTC
gdm 1.0.0-35 from the RH 6.0 distribution does not support
XDMCP.

Host running the RH 6.0 + gdm does not appear on chooser
lists of other computers.
Also starting the X with options -indirect <HOSTNAME> or
-query <HOSTNAME> has no effect.


PS. although the gdm is supposed to listen to port 177, this
port is closed.

Comment 1 Michael K. Johnson 1999-05-10 22:54:59 UTC
*** Bug 2538 has been marked as a duplicate of this bug. ***

When trying to access my machine from another using exceed,
it refuses to connect.  If I use xdm it works.

Running Netstat -an shows that port 117 is not being
answered and after a few moment the Recv-Q is quite high.

Chz

Andrew

Comment 2 Michael K. Johnson 1999-05-10 22:56:59 UTC
*** Bug 2270 has been marked as a duplicate of this bug. ***

stock 5.9 installation, gdm starts by default.
attempt to run

Xnest :1 -query localhost from an xterm

results in blank Xnest.

Same command on 5.2 brings Xnest with login prompt.

according to the gdm config file, remote access is enabled.

more clues:

$ netstat -a | grep 177
udp    11152      0 *:177                   *:*

number '11152' is a queue length which increases with every
Xnest attempt. looks like requests are igonored.

------- Additional Comments From s348842@student.uq.edu.au  05/05/99 05:31 -------
It works if debugging is enabled in /etc/X11/gdm/gdm.conf.  However
logout doesn't work.

Comment 3 Michael K. Johnson 1999-05-11 18:27:59 UTC
The current workaround is to turn on debugging in gdm.conf

Comment 4 Adam Spiers 1999-07-20 18:18:59 UTC
The proposed workaround of enabling debugging does not work for me.

Comment 5 Elliot Lee 1999-08-31 19:15:59 UTC
*** Bug 3927 has been marked as a duplicate of this bug. ***

I can not connect with exceed nor X-WinPro with xdmcp from
another host. (xdm instead of gdm seemed to work, so there
seems to be a bug in gdm)


------- Additional Comments From sopwith@redhat.com  08/31/99 15:12 -------
Just fixing the title, and verifying.

Comment 6 Elliot Lee 1999-08-31 22:45:59 UTC
Just to add more comments on the bug that has languished too long (and
to get mkp into the Cc: list)...

gdm2, currently in development, will support xdmcp and will have a few
less problems than gdm 1.x - if you're interested in helping the
author test, please let him know at mkp@mkp.net

Comment 7 Elliot Lee 1999-08-31 23:12:59 UTC
assign to mkj for now, since he's the current point man for gdmassign to mkj for now, since he's the current point man for gdm

(doh, actually click the right radio button)

Comment 8 jwitford 1999-09-02 06:43:59 UTC
Enabling debug doesn't always cure the problem.
Moving the gdm_debug() call in gdm_xdmpcp_send_accept() to before
the XdmcpFlush() mysteriously cures the problem even with debug off.
The problem is that the XdmcpFlush() doesn't flush the XDMCP packet.
Either something weird in NLS gettext() or something in kernel.

Comment 9 Elliot Lee 1999-10-20 16:58:59 UTC
The gdm included in RHL 6.1 should do a better job of this - are you
up to giving it a try?

Comment 10 Elliot Lee 1999-10-21 19:01:59 UTC
Bug reporter has indicated this works in RHL 6.1


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