Hi Shriramana, Hi everybody, Thank you very much for the response. Reading it, I felt that it should be a good way. Unfortunatly, it does not work. And more unfortunatly, I dont understand why. Typing: ----------------------------------------------------------------- « X :1 & This starts pretty well a server on display :1 with swapping from display :0 to display :1. Sometime I can see the splash screen of the display board chip manufacturer. Then, switching back to display :0, I can see the following (not so bad) message: » X Window System Version 6.8.2 » Release Date: 9 February 2005 » X Protocol Version 11, Revision 0, Release 6.8.2 » Build Operating System: SuSE Linux [ELF] SuSE » Current Operating System: Linux ... 2.6.13-15.7-default ... x86_64 » Build Date: 07 October 2005 » Before reporting problems, check http://wiki.X.Org » to make sure that you have the latest version. » Module Loader present » Markers: (--) probed, (**) from config file, (==) default setting, » (++) from command line, (!!) notice, (II) informational, » (WW) warning, (EE) error, (NI) not implemented, (??) unknown. » (==) Log file: "/var/log/Xorg.1.log", Time: Fri Mar 31 08:49:59 2006 » (==) Using config file: "/etc/X11/xorg.conf" » The XKEYBOARD keymap compiler (xkbcomp) reports: » > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 »symbols » > Ignoring extra symbols » Errors from xkbcomp are not fatal to the X server » Then typing: ------------------------------------------------------------ » xterm -display :1 ------ As user, the shell I typed this line in waits normaly. If I type ^C, the display is switched to :1 and nothing append (the display :1 is not closed). If I Switch to display :1 (as you explained and rather than killing xterm process), I see the X gray screen with X mouse cursor in the middel, but shortly because it dies so soon, and the message in the shell is: » *** If unresolved symbols were reported above, they might not » *** be the reason for the server aborting. » » Fatal server error: » Caught signal 8. Server aborting » » Please consult the The X.Org Foundation support » at http://wiki.X.Org » for help. » Please also check the log file at "/var/log/Xorg.1.log" for additional »information. ------ As root, the message is » AUDIT: Fri Mar 31 09:23:50 2006: 22192 X: client 1 rejected from local »host » Xlib: connection to ":1.0" refused by server » Xlib: No protocol specified » » Warning: This program is an suid-root program or is being run by the »root user. » The full text of the error...removing the suid bit on the executable. » xterm Xt error: Can't open display: %s And if I Switch to display :1, the result is the same as above (X dies in :1 "Fatal server error: Caught signal 8. Server aborting"). If you have a suggestion, it will be welcome. Best regards, Patrick NB: Shriramana, can you tell me the version of Suse you currently use, please. I mentioned X comportment differences after version 8.2 (did not buy 8.3 but 9.1, after 8.2), may be due to passage from XFree to XOrg ?. ---------------------------------------------------------------------- Le Vendredi 31 Mars 2006 03:07, Lynx a écrit :
Am Donnerstag, 30. März 2006 20:19 schrieb linux Serru:
... linux
Hi, these are the steps i take for doing so:
X :1 & ( switch back to :0 ) xterm -display :1 (in the xterm on :1) ssh -X user@maschine startkde
ther you go ;o)
<°)>><