Xnest woes
 

Using Slack 10.2, KDE 3.4.3, Xorg 6.8.2-4.

I have two boxes networked together. Networking, ssh, scp, samba, etc. all function just fine. There are no issues with name resolving, hosts files, etc.

I boot into KDE, either from runlevel 3 or 4. From Box2 running on display :0, I type:

Xnest -query Box1 :1

I also tried Xnest -query localhost :1

Nada.

A window opens and all I see is black. When I hover the mouse pointer over the new window all I see is the top one-third of the mouse. I tried typing some commands "blind" hoping that something was actually there but no dice.

I do have the KDM config file tagged to watch for XDMCP so that is not the issue when I run KDE from runlevel 4.

Everything Xnest related I read online was written by Pollyanna---all I am supposed to do is type Xnest -query Box1 :1. But that does not work and I don't know why!

Any ideas?

does Box2 have permission to access Box1's X server?

Yes. Second sentence of my original post:

I have two boxes networked together. Networking, ssh, scp, samba, etc. all function just fine. There are no issues with name resolving, hosts files, etc.

I figured out the problem last last night. My problem was conceptual. The user controls the new Xnest window with command line commands from within the original shell window that launched the Xnest window, not the new Xnest window. So by default the Xnest window is supposed to open with nothing in it. I haven't figured out anything past that meager triumph, however.

When the Xnest window opened I mentally focused on that window, but that is not how this silly tool works. Shame on me for thinking like a human being instead of a geek!

i saw the list the first time...
doesn't mention anything about X server permissions.