remote requests make KDM dump core

[epf1 at cec.wustl.edu]

I have a FreeBSD 6.0 box that I access remotely using Cygwin/X
from time to time. I use XDMCP to connect up to it from my desktop.

Up till about a week ago this was working like a champ, but that has changed
since I ran portmanager. Now KDM dumps core the moment I probe it for a
connection from a remote box.

here is a bit from /var/log/messages:

Nov 21 13:56:42 jerseygirl kernel: pid 91116 (kdm), uid 0: exited on
signal 11 (core dumped)
Nov 21 13:56:42 jerseygirl kdm[630]: Unknown session exit code 0 (sig 11)
from manager process
Nov 21 13:56:42 jerseygirl kernel: pid 91128 (kdm), uid 0: exited on
signal 11 (core dumped)
Nov 21 13:56:42 jerseygirl kdm[630]: Unknown session exit code 0 (sig 11)
from manager process
Nov 21 13:56:44 jerseygirl kernel: pid 91140 (kdm), uid 0: exited on
signal 11 (core dumped)
Nov 21 13:56:44 jerseygirl kdm[630]: Unknown session exit code 0 (sig 11)
from manager process

KDM works fine from the console, I am able to log in just fine when I am
sitting in front of the box in question, but as soon as I try to connect
remotely KDM crashes & is promptly revived only to crash again. In Cygwin/X
on the remote box I get the traditional X windows gray hash screen & the
"X" cursor for a split second then KDM crashes & the process starts anew.

I have run into one other user who has the same problem. It presented itself
to them after upgrading from KDE 3.4.2 to 3.4.3. I noticed the issue after
portmanager rebuilt KDE after libidn (/usr/ports/dns/libidn) was moved from
/usr/ports/devel to /usr/ports/dns.

If you have the ability to check & seem if KDM is accepting remote requests
could you please do so to confirm the problem? Also, any advice on how to
track this issue down would be much appreciated!

-Will