Bug 246971

Summary:	Yast execute X while connected remotely with ssh
Product:	[openSUSE] openSUSE 10.2	Reporter:	Forgotten User nqeDWc8OMK <forgotten_nqeDWc8OMK>
Component:	YaST2	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Yast logs SaX log

Description Forgotten User nqeDWc8OMK 2007-02-20 15:57:56 UTC

I established a remote connection with ssh to openSUSE 10,2, I ran yast by command line, selects hardware/Graphics card config and it was freeze. I went to see the PC (it was next to me) and discovered that the sax test of graphical configuration had been executed.
I consider this would not have to happen when something is executed remotely.

I don't know if I explained clearly in english, here is my explanation in spanish:

Establecí una conexión remota con ssh a un openSUSE 10.2, ejecute yast por línea de comandos, seleccione hardware/configuración de tarjeta gráfica y quedó congelado.
Fui a ver la pc (que estaba cerca mio) y descubrí que se había ejecutado el sistema de prueba de configuración gráfica de sax.
Considero esto no debería suceder cuando algo se ejecuta en forma remota.

Best regards.

Comment 1 Cyril Hrubis 2007-02-20 17:19:13 UTC

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST


Thanks!

Comment 2 Forgotten User nqeDWc8OMK 2007-02-20 18:13:48 UTC

Created attachment 120173 [details]
Yast logs

I think this is the correct one because the time.

Comment 3 Forgotten User nqeDWc8OMK 2007-02-21 20:58:58 UTC

I connected with FreeNX and the same thing happended, after selecting Graphics Cards configuration on Yast the sax graphics test was executed on the host.

Comment 4 Marcus Schaefer 2007-02-26 10:42:41 UTC

could you reproduce this by simply calling

   sax2

from your desktop session ?

Comment 5 Forgotten User nqeDWc8OMK 2007-02-26 12:47:29 UTC

Created attachment 121041 [details]
SaX log

Did you mean remotely ? If so, yes I could.
I ran sax2 through freenx

SaX: Checking update status for radeon driver
SaX: initialization already done
SaX: call [ sax2 -r ] if your system has changed !

SaX: startup

Thats all. I went to check the computer and I found sax running.

Comment 6 Marcus Schaefer 2007-02-26 12:59:52 UTC

sax2 checks for X11 forwarded ports if the machine you run sax2 on
doesn't provide a X-Server instance. The problem is in case of NX
there is a X-Server, a special nxproxy/nxagent server. The call of
XOpenDisplay() fails on that server of course and so sax assumes there
is a server but I can't access it... so it starts its own server

I'm sorry but remote X11 configuration via NX protocol doesn't make much
sense to me :-) If you establish a ssh forwarded  X11 port you can do that
anyway:


ssh -X host

sax2
SaX: root Password: 
SaX: Checking update status for mga driver
SaX: initialization already done
SaX: call [ sax2 -r ] if your system has changed !

SaX: startup
SaX: X-Server: localhost:10.0 -> grant
SaX: importing current configuration...

Comment 7 Forgotten User nqeDWc8OMK 2007-02-26 13:12:09 UTC

I understand. But I'm not interested on running sax.
I think it's a bug, because, when a ran sax with ssh the remote session was freeze  and I had to close sax by going to the machine.
If it doesn't have an X-server instance, maybe it should show a warning or something.