Running unstable. Trying to get XDMCP working via KDM. On the local host,
everything works. KDM gives me a graphical login prompt, and KDE loads when
I log in. From a remote machine, however, I get what appears to be a pure X
session with no Windows manager running. I get the hollow X cursor, and am
able to move it with the mouse. However, neither left nor right clicks do
any thing - no menu or anything. Clicking and dragging doesn't generate a
dotted outline selection. No key presses appear to do anything. Not sure
where to go from here. Hints and suggestions welcome.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, 28 Apr 2007, Daniel D Jones wrote:

> Running unstable. Trying to get XDMCP working via KDM. On the local host,
> everything works. KDM gives me a graphical login prompt, and KDE loads when
> I log in. From a remote machine, however, I get what appears to be a pure X
> session with no Windows manager running. I get the hollow X cursor, and am
> able to move it with the mouse. However, neither left nor right clicks do
> any thing - no menu or anything. Clicking and dragging doesn't generate a
> dotted outline selection. No key presses appear to do anything. Not sure
> where to go from here. Hints and suggestions welcome.

Checkout /etc/kde3/kdem/Xaccess to see what sorts of xdmcp access you
are allowing. At the least you want to offer:


* #any host can get a login window

You may also want to allow:


* CHOOSER BROADCAST #any indirect host can get a chooser

Also you need to enable xdmcp in kdmrc:

# Whether KDM should listen to incoming XDMCP requests.
# Default is true
Enable=true

Restart kdm at this point.

Make sure you backup kdmrc before making any changes so you can rollback
if you break it.

One more thing: There is a reported but unfixded bug in kdm in
Debian/Ubuntu going back a long way which is causing some xdmcp
configurations to fail when they really are ok. If you look in your logs
you'll see reports of kdm_greet getting memory corruption if you are
getting this problem. As a result of this problem I recently migrated a
bunch of thin client servers to use gdm instead of kdm.

Cheers,

Rob

--
Robert Brockway B.Sc. Phone: +1-905-821-2327
Senior Technical Consultant Urgent Support: +1-416-669-3073
OpenTrend Solutions Ltd Email: support@opentrend.net
Web: www.opentrend.net
Contributing Member of Software in the Public Interest


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Saturday 28 April 2007 15:23, Robert Brockway wrote:

Thanks for the response.

> On Sat, 28 Apr 2007, Daniel D Jones wrote:
> > Running unstable. Trying to get XDMCP working via KDM. On the local
> > host, everything works. KDM gives me a graphical login prompt, and KDE
> > loads when I log in. From a remote machine, however, I get what appears
> > to be a pure X session with no Windows manager running. I get the hollow
> > X cursor, and am able to move it with the mouse. However, neither left
> > nor right clicks do any thing - no menu or anything. Clicking and
> > dragging doesn't generate a dotted outline selection. No key presses
> > appear to do anything. Not sure where to go from here. Hints and
> > suggestions welcome.
>
> Checkout /etc/kde3/kdem/Xaccess to see what sorts of xdmcp access you
> are allowing. At the least you want to offer:
>
>
> * #any host can get a login window
>
> You may also want to allow:
>
>
> * CHOOSER BROADCAST #any indirect host can get a
> chooser

root@Luke:/etc/kde3/kdm# cat Xaccess | grep ^[^#]
* #any host can get a login window
* CHOOSER BROADCAST #any indirect host can get a chooser

> Also you need to enable xdmcp in kdmrc:
>
> # Whether KDM should listen to incoming XDMCP requests.
> # Default is true
> Enable=true

root@Luke:/etc/kde3/kdm# cat kdmrc | grep ^[^#]
[General]
ConfigVersion=2.3
StaticServers=:0
ReserveServers=:1,:2,:3
ServerVTs=-7
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
PidFile=/var/run/kdm.pid
[Xdmcp]
Enable=true
Willing=/etc/kde3/kdm/Xwilling
[Shutdown]
[X-*-Core]
Setup=/etc/kde3/kdm/Xsetup
Startup=/etc/kde3/kdm/Xstartup
Reset=/etc/kde3/kdm/Xreset
Session=/etc/kde3/kdm/Xsession
AllowRootLogin=false
AllowNullPasswd=false
AllowShutdown=Root
ClientLogFile=.xsession-errors-%s
[X-*-Greeter]
LogoArea=Logo
LogoPixmap=/usr/share/apps/kdm/pics/kdelogo.png
AntiAliasing=true
MinShowUID=1000
MaxShowUID=29999
Preloader=/usr/bin/preloadkde
Theme=@@@ToBeReplacedByDesktopBase@@@
[X-:*-Core]
ServerCmd=/usr/bin/X -br
ServerArgsLocal=-nolisten tcp
AllowNullPasswd=true
AllowShutdown=All
[X-:*-Greeter]
PreselectUser=Previous
FocusPasswd=true
LoginMode=DefaultLocal
AllowClose=true
[X-:0-Core]
ClientLogFile=.xsession-errors
[X-:0-Greeter]


> Restart kdm at this point.

I verified the settings you mentioned, and all were correct. I restarted kdm
just to ensure that I hadn't neglected to restart it after changing one of
the above when I was doing the initial configuration. No change.

> Make sure you backup kdmrc before making any changes so you can rollback
> if you break it.
>
> One more thing: There is a reported but unfixded bug in kdm in
> Debian/Ubuntu going back a long way which is causing some xdmcp
> configurations to fail when they really are ok. If you look in your logs
> you'll see reports of kdm_greet getting memory corruption if you are
> getting this problem. As a result of this problem I recently migrated a
> bunch of thin client servers to use gdm instead of kdm.

You didn't specify which log but I didn't find any such errors in either
kdm.log or Xorg.0.log, nor did I find any other related errors in the log.
Maybe I'll try switching to xdm just to see.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, 29 Apr 2007, Daniel D Jones wrote:

>> One more thing: There is a reported but unfixded bug in kdm in
>> Debian/Ubuntu going back a long way which is causing some xdmcp
>> configurations to fail when they really are ok. If you look in your logs
>> you'll see reports of kdm_greet getting memory corruption if you are
>> getting this problem. As a result of this problem I recently migrated a
>> bunch of thin client servers to use gdm instead of kdm.
>
> You didn't specify which log but I didn't find any such errors in either
> kdm.log or Xorg.0.log, nor did I find any other related errors in the log.
> Maybe I'll try switching to xdm just to see.

It depends on how you have syslog configured. I recommend running a debug
log to catch all the info. You can grep for the following error coming
from kdm_greet:

"Internal error: memory corruption detected"

Cheers,

Rob

--
Robert Brockway B.Sc. Phone: +1-905-821-2327
Senior Technical Consultant Urgent Support: +1-416-669-3073
OpenTrend Solutions Ltd Email: support@opentrend.net
Web: www.opentrend.net
Contributing Member of Software in the Public Interest


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Brockway wrote:
> On Sun, 29 Apr 2007, Daniel D Jones wrote:
>
>>> One more thing: There is a reported but unfixded bug in kdm in
>>> Debian/Ubuntu going back a long way which is causing some xdmcp
>>> configurations to fail when they really are ok. If you look in your
>>> logs
>>> you'll see reports of kdm_greet getting memory corruption if you are
>>> getting this problem. As a result of this problem I recently migrated a
>>> bunch of thin client servers to use gdm instead of kdm.
>>
>> You didn't specify which log but I didn't find any such errors in either
>> kdm.log or Xorg.0.log, nor did I find any other related errors in the
>> log.
>> Maybe I'll try switching to xdm just to see.
>
> It depends on how you have syslog configured. I recommend running a
> debug log to catch all the info. You can grep for the following error
> coming from kdm_greet:
>
> "Internal error: memory corruption detected"
>
> Cheers,
>
> Rob
>
I will just input that I was having a big issue with KDM and XDMCP with
Etch a few days ago. The solution I found was to switch the host (X
Client, the one doing the work) to GDM instead of KDM. Then it just sort
of worked. I still do not know why KDM didn't.

The X Server runs KDM and connects to the GDM X Client (XDMCP Server?)
just fine.

- --
Please do not use HTML mail for fully-textual messages.
Matthew K Poer <matthewpoer@gmail.com>
Location: GA, USA Web: http://matthewpoer.freehostia.com
GnuPG Public Key: 4DD0A9A6 Keyserver: subkeys.pgp.net
Thinkpad 600: Debian Sarge Sony VAIO PCV-RS 520: Debian Etch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org

iD8DBQFGNUb9kRdiiE3QqaYRAk9YAJ0f6fKFM6gUtY783PtPUH 6NAc1/HACfeNta
Aie/0IXhBcMkMqdZEaTYbEU=
=u/sO
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org