[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#187148: marked as done (xdm: only answers one XDMCP request and then shuts down socket)

Your message dated Thu, 01 Mar 2007 23:16:05 +0100
with message-id <45E750A5.8050505@ens-lyon.org>
and subject line Bug#187148: xdm: only answers one XDMCP request and then shuts down socket
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xdm
Version: 4.2.1-6

Hi,

after doing the lastest sid upgrade, my xdm doesn't work
properly anymore. I have an Xserver with option -indirect to 
the host itself, where xdm provides a chooser, presenting the
host itself and all other machines willing to serve. That worked
well for several years. Now, the chooser still appears, but the
login service is unavailable.

Debugging showed that the xdm is (in contrast to older versions)
willing to answer only one xdmcp request and then shuts down 
the xdmcp socket (i.e. binds the socket to the Xserver, so it
doesn't accept other packets anymore). Since this first available
request is already taken by the chooser query, all subsequent 
queries are dropped. 

Even when starting a new xdm without the Xserver, it answers only
exactly one xdmcp request from other hosts.

regards
Hadmut

--- End Message ---
--- Begin Message --- 
Closing since the submitter never replied to the ping about testing a
new release.

Brice

--- End Message ---
Reply to: