actually very impressive

"""
Unfortunately I believe the XDMCP problem is still in Feisty and Gutsy (i.e. the one where GDM
listens only on udp6 socket, not on IPv4, so XDMCP doesn't work at all).
"""

No.  It works fine in both current Gutsy and Hardy.  I have no Feisty with which to test.

Fedora's is still broken in F8.  Haven't tested F9.  What is particularly irritating about
that is that it is not the sort of bug which only occurs  on specific hardware and is hard for
the devs to reproduce.  Someone rewrote a major part of gdm and forgot to have it read in
values from the config files.  Any dev who cared enough could quite easily fire up some XDMCP
vnc sessions and reproduce the problem.  Though I'm sure that if I complained too much,
someone would tell me that the devs can't fix it unless I help them more.  In fact, the bug I
filed is still sitting as "unconfirmed" and "need more info".  With that kind of developer
attitude to such a serious problem I prefer not to waste my time spoon feeding them "more
info" regarding a trivially reproduceable snafu that I have already hard coded and recompiled
around for my customers bitten by it.  And the upstream bug report has not done any better
than the Fedora one.

So all this "actually very impressive" stuff regarding the 2 week slip does not really impress
me at all.