Bug 16106 - XDMCP broken in gdm-2.0beta2, needs beta4 version
Summary: XDMCP broken in gdm-2.0beta2, needs beta4 version
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gdm
Version: 7.1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard: Winston gold
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-13 19:02 UTC by John Cagle
Modified: 2008-05-01 15:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-08-14 01:44:12 UTC


Attachments (Terms of Use)

Description John Cagle 2000-08-13 19:02:44 UTC
The XDMCP implementation in "gdm-2.0beta2-35" is broken.  It will not manage remote
X Terminals even if "Enable=1" in the [xdmcp] section of /etc/X11/gdm/gdm.conf.

The beta4 version works for me.  Here's a note from it's ChangeLog:

1999-09-30   <mkp@mkp.net>

     * daemon/xdmcp.c (gdm_xdmcp_handle_query): Get XDMCP running again.

Please update this package to the beta4 version.  I downloaded mine from:

   ftp://spidermonkey.helixcode.com/pub/helix/distributions/RedHat-6/gdm-2.0beta4-0_helix_6.i386.rpm

Comment 1 Glen Foster 2000-08-13 20:18:32 UTC
This defect is considered MUST-FIX for Winston Gold-release

Comment 2 Owen Taylor 2000-08-14 01:44:10 UTC
I'm putting a new RPM into 7.0test that fixes this in testing.
I've asked Havoc to review the change, since it is a fix to
a fix of his, but I think it is correct.

(The Red Hat 2.0beta2 is a essentially a separate branch which
is considerably better than the stock 2.0beta4. Merging all
our patches to the stock 2.0beta4 would be impractical, and,
in any case, the maintainer has abandoned gdm2 and is now
working on gdm3.)

Comment 3 Havoc Pennington 2000-08-14 02:15:39 UTC
Owen's fix looks good to me.

Comment 4 John Cagle 2000-08-14 14:50:50 UTC
If you send me the fix, I'll be glad to test it.

Comment 5 John Cagle 2000-08-20 14:49:14 UTC
Tested gdm2.0-beta2-37 from Havoc.  Works for me!
Thanks!


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