Remote XDMCP session failure

[Paul Pace]

Binary package hint: gdm

1) Ubuntu 8.04

2) Synaptic->GDM 2.20.6-0ubuntu2

3) From Xming in Windows XP or from another Ubuntu machine, GDM should load as normal in a remote session.

4) After getting the login screen remotely and logging in, the loading screen hangs for a very long time with flat orange background, then after a few minutes a gray box appears in the upper left hand corner, and a few minutes later the gray box becomes readable with the error message below. The desktop is visible but cannot be interacted with and there are no panels.

There was an error starting GNOME settings Daemon.

Some things, such as themes, sounds, or background settings may not work correctly.

The last error message was:

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

GNOME will still try to restart the Settings Daemon next time you log in.

[Sebastien Bacher (seb128)]

thank you for your bug report, does starting a session locally works correctly? does starting an another session over xdmcp works correctly?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[bmjbmj (bmjbmj)]

Login works locally, it works from other kubuntu/ubuntu clients and from LTSP clients.

If you wait long enought (3-20 minuts) you get the error in the attached picture

The problem is dicused her to: "http://ge.ubuntuforums.com/showthread.php?t=796042&s=4f6a2242c40b19fe804b6ff13b23210e&"

[Sebastien Bacher (seb128)]

Could you try if that's still an issue in jaunty?

[rannsaicher (rannsaicher)]

I upgraded one of my machines from hardy to intrepid to jaunty on 1 aug 2009.
prior to this i could xdmcp to my other machine (still running hardy).
Now i cant, so the answer to the question is Yes, this is now an issue in Jaunty.

Selecting the remote host from the jaunty login screen on the local host simply returns me to that screen on the local host.