Your message dated Sat, 3 Oct 2026 11:43:56 -0400
with message-id <[email protected]>
and subject line Re: xdm does not just work
has caused the Debian Bug report #630778,
regarding xdm does not just work
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
630778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630778
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xdm
Version: 1:1.1.10-3
See bug #76929 in particular PAM.
Trying a Wyse Winterm with XDMCP direct. I see the login widget then it
dies. (The Wyse Winterm then starts up and can then RDP login to xrdp
package I have running on system. Really should do X to a Linux box.
Wyse Winterm can not do ssh -X due to a problem with it. This like RDP
carries an unnecessary overhead for properly managed LAN. The X
client-server model is far superior.)
Looks like quite a few more files now need to be changed before xdm
will work. Would be nice if it just worked.
/var/log/xdm.log: --
> Fri Jun 17 10:23:58 2011 xdm info (pid 2232): Starting
> Fri Jun 17 16:23:37 2011 xdm error (pid 2232): Cannot convert Internet
> address 10.253.0.200 to host name
> Fri Jun 17 16:23:40 2011 xdm info (pid 2232): Starting X server on
> 10.253.0.200:2
Should I really need to put DHCP pool in the DNS? This is a test
machine and some one else looks up reverse for 10.in-addr.arpa.
> 0 items in XFree86_VT property!
> Fri Jun 17 16:23:40 2011 xdm info (pid 3901): sourcing /etc/X11/xdm/Xsetup
My config files were patched similar to original post, but I also do
not use xdm for local display.
Xaccess (had to uncomment these): --
* #any host can get a login window
* CHOOSER BROADCAST #any host can get a chooser
These were originally commented out on my install.
xdm-config (had to comment this out): --
!DisplayManager.requestPort: 0
This was not originally commented out on my install.
Xservers (commented this out as not needed): --
#:0 local /usr/bin/X :0 vt7 -nolisten tcp
Then tried patching /etc/security/pam_env.conf too: --
REMOTEHOST DEFAULT=localhost OVERRIDE=@{PAM_RHOST}
DISPLAY DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}
These were originally commented out on my install.
Now get login, but don't get session. Goes back to login.
The remote display is 10.253.0.20.
Does xrdb conflict with this package!?
~/.xsession-errors: --
> Xsession: X session started for andrewb at Fri Jun 17 16:49:49 GMT-8 2011
> Client is not authorized to connect to Serverxrdb: Resource temporarily
> unavailable
> xrdb: Can't open display '10.253.0.200:0.0'
> Client is not authorized to connect to Serverxrdb: Resource temporarily
> unavailable
> xrdb: Can't open display '10.253.0.200:0.0'
> Client is not authorized to connect to ServerClient is not authorized to
> connect to Server/usr/bin/xsetroot: unable to open display '10.253.0.200:0.0'
> Client is not authorized to connect to Server/usr/bin/twm: unable to open
> display "10.253.0.200:0.0"
> Client is not authorized to connect to Server/usr/bin/xterm Xt error: Can't
> open display: 10.253.0.200:0.0
> Xsession: X session started for andrewb at Fri Jun 17 16:49:58 GMT-8 2011
> Client is not authorized to connect to Serverxrdb: Resource temporarily
> unavailable
> xrdb: Can't open display '10.253.0.200:0.0'
> Client is not authorized to connect to Serverxrdb: Resource temporarily
> unavailable
> xrdb: Can't open display '10.253.0.200:0.0'
> Client is not authorized to connect to ServerClient is not authorized to
> connect to Server/usr/bin/xsetroot: unable to open display '10.253.0.200:0.0'
> Client is not authorized to connect to Server/usr/bin/twm: unable to open
> display "10.253.0.200:0.0"
> Client is not authorized to connect to Server/usr/bin/xterm Xt error: Can't
> open display: 10.253.0.200:0.0
> Xsession: X session started for andrewb at Fri Jun 17 16:50:15 GMT-8 2011
> Client is not authorized to connect to Serverxrdb: Resource temporarily
> unavailable
> xrdb: Can't open display '10.253.0.200:0.0'
> Client is not authorized to connect to Serverxrdb: Resource temporarily
> unavailable
> xrdb: Can't open display '10.253.0.200:0.0'
> Client is not authorized to connect to ServerClient is not authorized to
> connect to Server/usr/bin/xsetroot: unable to open display '10.253.0.200:0.0'
> Client is not authorized to connect to Server/usr/bin/twm: unable to open
> display "10.253.0.200:0.0"
> Client is not authorized to connect to Server/usr/bin/xterm Xt error: Can't
> open display: 10.253.0.200:0.0
/var/log/xdm.log: --
> Fri Jun 17 16:46:57 2011 xdm error (pid 3901): fatal IO error 11 (Resource
> temporarily unavailable)
> Fri Jun 17 16:47:11 2011 xdm error (pid 2232): Cannot convert Internet
> address 10.253.0.200 to host name
> Fri Jun 17 16:47:14 2011 xdm info (pid 2232): Starting X server on
> 10.253.0.200:2
> 0 items in XFree86_VT property!
> Fri Jun 17 16:47:14 2011 xdm info (pid 3980): sourcing /etc/X11/xdm/Xsetup
> Fri Jun 17 16:49:06 2011 xdm info (pid 2232): Shutting down
> Fri Jun 17 16:49:06 2011 xdm info (pid 2232): Exiting
> Fri Jun 17 16:49:12 2011 xdm info (pid 4003): Starting
> Fri Jun 17 16:49:12 2011 xdm error (pid 4003): Cannot convert Internet
> address 10.253.0.200 to host name
> Fri Jun 17 16:49:12 2011 xdm info (pid 4003): Starting X server on
> 10.253.0.200:2
> 0 items in XFree86_VT property!
> Fri Jun 17 16:49:12 2011 xdm info (pid 4032): sourcing /etc/X11/xdm/Xsetup
> Fri Jun 17 16:49:49 2011 xdm info (pid 4032): sourcing /etc/X11/xdm/Xstartup
> Fri Jun 17 16:49:49 2011 xdm info (pid 4046): executing session
> /etc/X11/xdm/Xsession
> Fri Jun 17 16:49:49 2011 xdm info (pid 4032): sourcing /etc/X11/xdm/Xreset
> Fri Jun 17 16:49:49 2011 xdm error (pid 4003): Cannot convert Internet
> address 10.253.0.200 to host name
> Fri Jun 17 16:49:50 2011 xdm info (pid 4003): Starting X server on
> 10.253.0.200:2
> 0 items in XFree86_VT property!
> Fri Jun 17 16:49:50 2011 xdm info (pid 4116): sourcing /etc/X11/xdm/Xsetup
> Fri Jun 17 16:49:58 2011 xdm info (pid 4116): sourcing /etc/X11/xdm/Xstartup
> Fri Jun 17 16:49:58 2011 xdm info (pid 4125): executing session
> /etc/X11/xdm/Xsession
> Fri Jun 17 16:49:58 2011 xdm info (pid 4116): sourcing /etc/X11/xdm/Xreset
> Fri Jun 17 16:49:58 2011 xdm error (pid 4003): Cannot convert Internet
> address 10.253.0.200 to host name
> Fri Jun 17 16:49:59 2011 xdm info (pid 4003): Starting X server on
> 10.253.0.200:2
> 0 items in XFree86_VT property!
> Fri Jun 17 16:49:59 2011 xdm info (pid 4194): sourcing /etc/X11/xdm/Xsetup
> Fri Jun 17 16:50:08 2011 xdm error (pid 4194): pam_authenticate failure:
> Authentication failure
> Fri Jun 17 16:50:15 2011 xdm info (pid 4194): sourcing /etc/X11/xdm/Xstartup
> Fri Jun 17 16:50:15 2011 xdm info (pid 4203): executing session
> /etc/X11/xdm/Xsession
> Fri Jun 17 16:50:15 2011 xdm info (pid 4194): sourcing /etc/X11/xdm/Xreset
> Fri Jun 17 16:50:15 2011 xdm error (pid 4003): Cannot convert Internet
> address 10.253.0.200 to host name
> Fri Jun 17 16:50:16 2011 xdm info (pid 4003): Starting X server on
> 10.253.0.200:2
> 0 items in XFree86_VT property!
> Fri Jun 17 16:50:16 2011 xdm info (pid 4273): sourcing /etc/X11/xdm/Xsetup
--- End Message ---
--- Begin Message ---
notfound 630778 1:1.1.10-3
thanks
On Fri, 17 Jun 2011 17:34:27 +0800 Andrew Buckeridge <[email protected]> wrote:
> Package: xdm
> Version: 1:1.1.10-3
>
> See bug #76929 in particular PAM.
>
> Trying a Wyse Winterm with XDMCP direct. I see the login widget then it
> dies. (The Wyse Winterm then starts up and can then RDP login to xrdp
> package I have running on system. Really should do X to a Linux box.
> Wyse Winterm can not do ssh -X due to a problem with it. This like RDP
> carries an unnecessary overhead for properly managed LAN. The X
> client-server model is far superior.)
>
> Looks like quite a few more files now need to be changed before xdm
> will work. Would be nice if it just worked.
>
> /var/log/xdm.log: --
> > Fri Jun 17 10:23:58 2011 xdm info (pid 2232): Starting
> > Fri Jun 17 16:23:37 2011 xdm error (pid 2232): Cannot convert Internet
address 10.253.0.200 to host name
> > Fri Jun 17 16:23:40 2011 xdm info (pid 2232): Starting X server on
10.253.0.200:2
>
> Should I really need to put DHCP pool in the DNS? This is a test
> machine and some one else looks up reverse for 10.in-addr.arpa.
>
> > 0 items in XFree86_VT property!
> > Fri Jun 17 16:23:40 2011 xdm info (pid 3901): sourcing /etc/X11/xdm/Xsetup
>
> My config files were patched similar to original post, but I also do
> not use xdm for local display.
>
> Xaccess (had to uncomment these): --
> * #any host can get a login window
> * CHOOSER BROADCAST #any host can get a chooser
>
> These were originally commented out on my install.
>
> xdm-config (had to comment this out): --
> !DisplayManager.requestPort: 0
>
> This was not originally commented out on my install.
>
> Xservers (commented this out as not needed): --
> #:0 local /usr/bin/X :0 vt7 -nolisten tcp
>
> Then tried patching /etc/security/pam_env.conf too: --
> REMOTEHOST DEFAULT=localhost OVERRIDE=@{PAM_RHOST}
> DISPLAY DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}
>
> These were originally commented out on my install.
>
> Now get login, but don't get session. Goes back to login.
>
> The remote display is 10.253.0.20.
>
> Does xrdb conflict with this package!?
>
> ~/.xsession-errors: --
> > Xsession: X session started for andrewb at Fri Jun 17 16:49:49 GMT-8 2011
> > Client is not authorized to connect to Serverxrdb: Resource temporarily
unavailable
> > xrdb: Can't open display '10.253.0.200:0.0'
> > Client is not authorized to connect to Serverxrdb: Resource temporarily
unavailable
Hi,
Looking at the logs you sent, xdm was managing the display 10.253.0.200:2, but
all clients in ~/.xsession-errors tried to open 10.253.0.200:0.0. That value
comes
from the line you added to /etc/security/pam_env.conf
(DISPLAY DEFAULT=${REMOTEHOST}:0.0): xdm passes the PAM environment
to the session after setting DISPLAY itself, so that line overrode the
correct value. Please remove the DISPLAY/REMOTEHOST lines from
pam_env.conf; xdm sets DISPLAY correctly for XDMCP displays on its own.
The other changes you made (enabling the Xaccess entries and
commenting out DisplayManager.requestPort) are the documented way to
enable XDMCP. It is disabled by default purposely, since XDMCP is
unencrypted and lets any host on the network ask for a login screen;
that default won't change due to security reasons.
I'm now closing this report. If XDMCP sessions still fail with a current
xdm (1:1.1.17) with an unmodified pam_env.conf, please reopen with
/var/log/xdm.log and ~/.xsession-errors.
Thanks,
Boyuan Yang
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
