On Monday 03 March 2003 10:14, Richard Bos wrote:
Op maandag 3 maart 2003 09:48, schreef Leendert Meyer:
On Monday 03 March 2003 09:22, Richard Bos wrote:
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed....
You won't find anything changed there... ;-P
Well, I was told by the kdm maintainer.... And it seems obvious that something must change to allow people, remote access.
I agree. I have a "Start New Session" menu entry in my K-menu. That is to start a local X login session. Another button to start remote X login sessions.
No it is not in the user session/kmenu. It is in the login manager screen.
Could not find it. Could you send me a screenshot in private mail? [...]
BTW, any luck with remote X login sessions like I suggested in my previous mail?
Still the same story. I now checked with ethereal and I know for sure that XDMCP protocal is established and I would say even works. I e.g. see an Xwilling pkg that shows the load of the machine. I've seen this in an Xwilling script. After that an xdmcp manage message is sent (so no firewall problems too).
1. Try it without the firewall. If you use a local network, set IP_FORWARD="yes" in /etc/sysconfig/sysctl and run SuSEconfig. 2. Try it with xdm login instead of kdm login.
So the Xsession seems to be transferred to from the remote machine to the local machine, but no more. Could it be that startkde is not run (also because to the local machine I obtain the grey Xsession background, the bg when X is started).
X :1.0 -once -query 192.168.0.2 -- works -- I get a kdm login dialog X :1.0 -indirect 192.168.0.2 -- does not work, should get a chooser, but X comes 5 times up -- have to kill X with <Ctrl>+<Alt>-<Backspace> X :1.0 -once -broadcast -- works -- I get a watch mouse cursor first, then the kdm login dialog Will check these with xdm login after I've sent this mail. Cheers, Leen