Hi, I have no problem connecting my Suse Novell 10.0 box to an other distant Suse Novell 10.0 box, using ssh. Now, I would like to know what to do to use X through ssh. While using local display :0 for current local work, I dream to start the distant KDE on local display :1 and log on as I would be in front of the distant computer. I dont want to use the sharing destop ability of KDE, exepted if it is possible to do it through ssh. Starting by the logging screen or directly entering the user (used by ssh) KDE session, it does not matter wich way. Thant you for the attention paid to this mail, Sincerly, Patrick
Am Donnerstag, 30. März 2006 20:19 schrieb Patrick Serru:
Hi,
I have no problem connecting my Suse Novell 10.0 box to an other distant Suse Novell 10.0 box, using ssh. Now, I would like to know what to do to use X through ssh. While using local display :0 for current local work, I dream to start the distant KDE on local display :1 and log on as I would be in front of the distant computer. I dont want to use the sharing destop ability of KDE, exepted if it is possible to do it through ssh. Starting by the logging screen or directly entering the user (used by ssh) KDE session, it does not matter wich way.
Thant you for the attention paid to this mail, Sincerly, Patrick
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) <°)>><
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)
<°)>><
Hi Patrick, On Friday 31 March 2006 17:17, Patrick Serru wrote:
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).
Don't type ^C but switch to display :1. There should be an xterm running, but only until you type ^C on display :0. That worked here with 2 machines both running SUSE 9.2. Regards, Nils
Hi Nils, hi everybody, I well understood that! Further more in the text, I explained what appends not typing "^C" but "xterm -display :1" instead. As far as I understand, your mail means that this does not work on Suse 10.0. Would someone have an idea on the reason why ? Could it come from a (some how) "bad" upgrade of my Suse 9.2 (I made a misteak writing the NB). For exemple, on the remote machine, I upgraded from 9.2 to 10.0, and overthere, the user has now systematicaly a non fatal X error while rebooting the computer: somethink saying that there is allready a X server running. Life stay so, as long as the error is not fatal. Best regards, Patrick ------------------------------------------------------ Le Vendredi 31 Mars 2006 12:17, Nils Kassube a écrit :
Hi Patrick,
Don't type ^C but switch to display :1. There should be an xterm running, but only until you type ^C on display :0. That worked here with 2 machines both running SUSE 9.2.
Regards, Nils
Am Freitag, 31. März 2006 19:41 schrieb Patrick Serru:
Hi Nils, hi everybody,
I well understood that! Further more in the text, I explained what appends not typing "^C" but "xterm -display :1" instead. As far as I understand, your mail means that this does not work on Suse 10.0. Would someone have an idea on the reason why ?
Could it come from a (some how) "bad" upgrade of my Suse 9.2 (I made a misteak writing the NB). For exemple, on the remote machine, I upgraded from 9.2 to 10.0, and overthere, the user has now systematicaly a non fatal X error while rebooting the computer: somethink saying that there is allready a X server running. Life stay so, as long as the error is not fatal.
Best regards, Patrick
------------------------------------------------------
Le Vendredi 31 Mars 2006 12:17, Nils Kassube a écrit :
Hi Patrick,
Don't type ^C but switch to display :1. There should be an xterm running, but only until you type ^C on display :0. That worked here with 2 machines both running SUSE 9.2.
Regards, Nils
hi to all, i just found out that you have to disable the authorization in 10.0 when starting the xserver. this can be achieved by starting X with: X -ac :1 & the other steps should be working then. good luck... <°)>><
Le Vendredi 31 Mars 2006 16:11, Lynx a écrit :
Am Freitag, 31. März 2006 19:41 schrieb Patrick Serru:
Hi Nils, hi everybody,
I well understood that! Further more in the text, I explained what appends not typing "^C" but "xterm -display :1" instead. As far as I understand, your mail means that this does not work on Suse 10.0. Would someone have an idea on the reason why ?
Could it come from a (some how) "bad" upgrade of my Suse 9.2 (I made a misteak writing the NB). For exemple, on the remote machine, I upgraded from 9.2 to 10.0, and overthere, the user has now systematicaly a non fatal X error while rebooting the computer: somethink saying that there is allready a X server running. Life stay so, as long as the error is not fatal.
Best regards, Patrick
------------------------------------------------------
hi to all,
i just found out that you have to disable the authorization in 10.0 when starting the xserver. this can be achieved by starting X with:
X -ac :1 &
the other steps should be working then.
good luck...
Hi Lynx, hi to all, Thant you Lynx for this good idea, but no change. What other thing in your command line do you hide to me... please tell me, Lynx :-) Just copie and paste it, in german if you want :-) :-) Seriously, Nothing bad appends before I switche to the screen :1, especting to find an xterm on it. This action "kills" the :1 display. This appends after having typed "xterm..." command OR NOT. That is, typing "X -ac :1 &", "Ctrl+Alt+F7" then "Ctrl+Alt+F8" close the display :1. No necessity to type the command "xterm..." to get this error. Regards, Patrick
Am Freitag, 31. März 2006 23:59 schrieb Patrick Serru:
Le Vendredi 31 Mars 2006 16:11, Lynx a écrit :
Am Freitag, 31. März 2006 19:41 schrieb Patrick Serru:
Hi Nils, hi everybody,
I well understood that! Further more in the text, I explained what appends not typing "^C" but "xterm -display :1" instead. As far as I understand, your mail means that this does not work on Suse 10.0. Would someone have an idea on the reason why ?
Could it come from a (some how) "bad" upgrade of my Suse 9.2 (I made a misteak writing the NB). For exemple, on the remote machine, I upgraded from 9.2 to 10.0, and overthere, the user has now systematicaly a non fatal X error while rebooting the computer: somethink saying that there is allready a X server running. Life stay so, as long as the error is not fatal.
Best regards, Patrick
------------------------------------------------------
hi to all,
i just found out that you have to disable the authorization in 10.0 when starting the xserver. this can be achieved by starting X with:
X -ac :1 &
the other steps should be working then.
good luck...
Hi Lynx, hi to all,
Thant you Lynx for this good idea, but no change. What other thing in your command line do you hide to me... please tell me, Lynx :-) Just copie and paste it, in german if you want :-) :-)
Seriously, Nothing bad appends before I switche to the screen :1, especting to find an xterm on it. This action "kills" the :1 display. This appends after having typed "xterm..." command OR NOT. That is, typing "X -ac :1 &", "Ctrl+Alt+F7" then "Ctrl+Alt+F8" close the display :1. No necessity to type the command "xterm..." to get this error.
Regards, Patrick
hi patrick, do i get you right, that switching to :0 and back to :1 after calling X -ac :1 & doing nothing else inbetween kills the xserver on :1 ? you can check that with ps ax | grep X if this is the case then there might be a problem with your general graphics setup. maybe you can find some info in /var/log/Xorg.1.log normally you should be able to switch back and forth as often as you wish. good luck... <°)>><
Am Samstag, 1. April 2006 01:06 schrieb Lynx:
Am Freitag, 31. März 2006 23:59 schrieb Patrick Serru:
Le Vendredi 31 Mars 2006 16:11, Lynx a écrit :
Am Freitag, 31. März 2006 19:41 schrieb Patrick Serru:
Hi Nils, hi everybody,
I well understood that! Further more in the text, I explained what appends not typing "^C" but "xterm -display :1" instead. As far as I understand, your mail means that this does not work on Suse 10.0. Would someone have an idea on the reason why ?
Could it come from a (some how) "bad" upgrade of my Suse 9.2 (I made a misteak writing the NB). For exemple, on the remote machine, I upgraded from 9.2 to 10.0, and overthere, the user has now systematicaly a non fatal X error while rebooting the computer: somethink saying that there is allready a X server running. Life stay so, as long as the error is not fatal.
Best regards, Patrick
------------------------------------------------------
hi to all,
i just found out that you have to disable the authorization in 10.0 when starting the xserver. this can be achieved by starting X with:
X -ac :1 &
the other steps should be working then.
good luck...
Hi Lynx, hi to all,
Thant you Lynx for this good idea, but no change. What other thing in your command line do you hide to me... please tell me, Lynx :-) Just copie and paste it, in german if you want :-) :-)
Seriously, Nothing bad appends before I switche to the screen :1, especting to find an xterm on it. This action "kills" the :1 display. This appends after having typed "xterm..." command OR NOT. That is, typing "X -ac :1 &", "Ctrl+Alt+F7" then "Ctrl+Alt+F8" close the display :1. No necessity to type the command "xterm..." to get this error.
Regards, Patrick
hi patrick,
do i get you right, that switching to :0 and back to :1 after calling X -ac :1 & doing nothing else inbetween kills the xserver on :1 ? you can check that with ps ax | grep X
if this is the case then there might be a problem with your general graphics setup. maybe you can find some info in /var/log/Xorg.1.log
normally you should be able to switch back and forth as often as you wish.
found some info about signal 8. http://sysadminforum.com/t239534.html sounds not good... make sure you have the latest updates of xorg ;o)
good luck...
<°)>><
Just an idea:
... do i get you right, that switching to :0 and back to :1 after calling X -ac :1 & doing nothing else inbetween kills the xserver on :1 ? you can check that with ps ax | grep X
if this is the case then there might be a problem with your general graphics setup. maybe you can find some info in /var/log/Xorg.1.log ...
To check this maybe you can try the Xnest X server. This one starts an X11 server inside the existing (correctly running) server, see http://www.xfree86.org/4.2.0/Xnest.1.html Start Xnest instead of your full featured :1 server and redirect your remote X11 requests to that X11 server With this you can check if it is some hardware related problem of your local full featured X11 server or some software related authentication problem... Greetings, Dirk.
Hi Dirk, hi every body, Thank you for your respons, Dirk. I followd quick the link you gave. I will certainely trye it, but at the moment, I have a real harware problem. I left my usual 9 months old machin and used an older slower one. Disks, IDE contoller, CPU... big sh.. Unabled to start the Suse 9.2 DVD rescue linux nor Debian install DVD! And the worst: the old second boot MS W2000 is running anyway, explorer crash but runs after restart. What a mess. I keep this abelity in mind and will give the result of my tries on the list ASAP. Sincerly, Patrick ---------------------------------------------------- Le Mardi 04 Avril 2006 12:53, Dirk Osswald a écrit :
Just an idea:
... do i get you right, that switching to :0 and back to :1 after calling X -ac :1 & doing nothing else inbetween kills the xserver on :1 ? you can check that with ps ax | grep X
if this is the case then there might be a problem with your general graphics setup. maybe you can find some info in /var/log/Xorg.1.log ...
To check this maybe you can try the Xnest X server. This one starts an X11 server inside the existing (correctly running) server, see http://www.xfree86.org/4.2.0/Xnest.1.html Start Xnest instead of your full featured :1 server and redirect your remote X11 requests to that X11 server
With this you can check if it is some hardware related problem of your local full featured X11 server or some software related authentication problem...
Greetings, Dirk.
On Thursday 30 March 2006 20.19, Patrick Serru wrote:
Hi,
I have no problem connecting my Suse Novell 10.0 box to an other distant Suse Novell 10.0 box, using ssh. Now, I would like to know what to do to use X through ssh. While using local display :0 for current local work, I dream to start the distant KDE on local display :1 and log on as I would be in front of the distant computer. I dont want to use the sharing destop ability of KDE, exepted if it is possible to do it through ssh. Starting by the logging screen or directly entering the user (used by ssh) KDE session, it does not matter wich way.
Thant you for the attention paid to this mail, Sincerly, Patrick
You didn't mention how distant your suse boxes are, so we cannot offer alternative ways to get your KDE... The other alternatives are VNC (3 or 4 different ways) and Nx (NoMachine). Depending on the connection bandwidth and more important the network latency, you will find either of these more responsive. Jerry
participants (5)
-
Dirk Osswald -
Jerry Westrick -
Lynx -
Nils Kassube -
Patrick Serru