RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 867981 - gdm doesn't start when connecting to localhost using gdm via XDMCP
Summary: gdm doesn't start when connecting to localhost using gdm via XDMCP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gdm
Version: 6.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 19:06 UTC by Jiri Koten
Modified: 2013-02-21 10:02 UTC (History)
1 user (show)

Fixed In Version: gdm-2.30.4-39.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 10:02:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
slave.log (3.81 KB, text/plain)
2012-10-18 19:09 UTC, Jiri Koten 		no flags Details
slave.log.1 (11.11 KB, text/plain)
2012-10-18 19:10 UTC, Jiri Koten 		no flags Details
Work around xcb bug (6.49 KB, patch)
2012-10-23 18:17 UTC, Ray Strode [halfline] 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0381 0 normal SHIPPED_LIVE gdm bug fix and enhancement update 2013-02-20 20:52:09 UTC

Description Jiri Koten 2012-10-18 19:06:43 UTC 
Description of problem:
When I enable XDMCP in gdm and then try to connect from the same machine via XDMCP, i.e. using localhost, the greeter keep spinning and never shows up.

From greeter log:
No protocol specified

** (gnome-session:16605): WARNING **: Cannot open display:



When connecting from remote machine gdm starts normally.

Version-Release number of selected component (if applicable):
gdm-2.30.4-33.el6_2.1
gdm-2.30.4-33.el6_3.1

How reproducible:
100%

Steps to Reproduce:
1. Enable XDMCP in gdm; edit /etc/gdm/custom.conf and add Enable=true under [xdmcp] 
2. Restart gdm; # initctl restart prefdm
3. Login
4. Connect to localhost; $ Xephyr -query localhost :2
  
Actual results:
gdm not starting up

Expected results:
gdm properly starts up

Additional info:
This is a regression as no such issue exist in gdm-2.30.4-33.el6_2
Comment 1 Jiri Koten 2012-10-18 19:09:35 UTC 
Created attachment 629584 [details]
slave.log
Comment 2 Jiri Koten 2012-10-18 19:10:05 UTC 
Created attachment 629585 [details]
slave.log.1
Comment 4 Ray Strode [halfline] 2012-10-22 19:24:21 UTC 
Seems to be a problem with access control. If I use Xephyr -ac it works, if I remove the -ac it fails.

I'll investigate.
Comment 5 Ray Strode [halfline] 2012-10-22 22:13:56 UTC 
So the issue seems to be a problem with XCB.

It actually forces FamilyLocal when 

DISPLAY=localhost:something

(see xcb_auth.c:get_authptr)

this fails in XauGetBestAuthByAddr() on the client side since the cookie is FamilyInternet. (We used to use FamilyWild which would match fine since it's wild)

We'll probably either have to special case localhost here until xcb can be fixed or maybe add two entries.
Comment 6 Ray Strode [halfline] 2012-10-23 13:54:06 UTC 
Let's get the acks rolling for this, it's pretty bad.  I'm sure we have customers who use XDMCP to the local machine.
Comment 8 RHEL Program Management 2012-10-23 17:01:06 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Comment 9 Ray Strode [halfline] 2012-10-23 18:17:56 UTC 
Created attachment 632272 [details]
Work around xcb bug

This updated xauth patch fixes the original problem from bug 860645 but also

1) adds two additional auth entries for local connections to work around the xcb bug

2) fixes an uninitialized variable access that causes XDMCP to occasionally fail during testing.
Comment 14 errata-xmlrpc 2013-02-21 10:02:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0381.html
Note You need to log in before you can comment on or make changes to this bug.