xdmcp/gdmchooser breakage from 2.20.0-0ubuntu3 -> 4
Bug #152824 reported by
Alex Williamson
This bug report is a duplicate of:
Bug #152505: gdmgreeter segfaults when XRandR is not available.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu |
New
|
Undecided
|
Unassigned | ||
| gdm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Upgrading from gdm_2.20.0-0ubuntu3 to gdm_2.20.0-0ubuntu4 broken my xdmcp setup. I have the following in /etc/gdm/
[daemon]
RemoteGreeter=
[xdmcp]
Enable=true
On a remote system, I run:
Xnest -query <server> :1
With ubuntu3, this works fine. With ubuntu4, the Xnest flashes between the X root weave and a white background a few times, then dies. I also end up with a /var/crash/
Revision history for this message
| Alex Williamson (alex-williamson) wrote | #1 |
Revision history for this message
| Alex Williamson (alex-williamson) wrote | #2 |
To post a comment you must log in.
I applied the patch from 152505 and it does allow Xnest to connect, however, there's still a problem. I have a thin client running an nfs root installation of Fiesty. It connects to a gutsy server with xdmcp. This configuration still fails with 2.20.0-0ubuntu4 (plus 152505 patch), but works with ubuntu3. The client does support RandR, and I see this in the X output:
(==) RandR enabled
(II) Initializing built-in extension RANDR
If I remove patch 63 from ubuntu4, it works like ubuntu3. Also, if I comment out the RemoteGreeter line in my gdm.conf-custom file (RemoteGreeter=