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