Re: [suse-amd64] xterm will not open a windows

What is the client that you are trying to open a window on ? Starting with about Suse 9.3, the X server by default starts with the option "-nolisten tcp", which means that the X server will not even listen for connections over TCP. So, if you did a default install of Suse 9.3-Suse 10.1 on a workstation, the default behavior of that workstation is to not listen for incoming X connections. Loggin in to a remote machine, setting the DISPLAY, and launching an application will result in "nothing" happening. Check your local X server by "ps -ef | grep X" - if you see something like this, you X server will not allow incoming connections. /usr/X11R6/bin/X -br -nolisten tcp :0 vt7 ssh will work, but the X you grew up with (at least us older guys :) will not... If you want to turn off this security feature, you will have to modify /usr/X11R6/lib/X11/xdm/Xservers # use such a line to enable the console login option in the kdm menu #:0 local@tty1 /usr/X11R6/bin/X vt7 # "reserve" means that the X server gets only started on request (only kdm) :0 local /usr/X11R6/bin/X -nolisten tcp -br vt7 Remove the "-nolisten tcp" option, and reboot... Kevin Kevin Gassiot Advanced Systems Group Visualization Systems Support Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot@veritasdgc.com José Luis Ricardo Chávez 07/28/2006 07:31 AM To suse-amd64@suse.com cc Subject Re: [suse-amd64] xterm will not open a windows I rather think the problem is related to the way X Windows manages security. In principle, xauth stores a key in ~/.Xauthority whenever the user grants permission to a host (display) to connect to the X server but sometimes the user's key changes and the connection could not be stablished unless the .Xauthority file is deleted or recreated. I had forgotten that some time ago I had a similar problem while trying to set up my network (nfs) account after installing a new SuSE version. Cheers. - José Luis On Fri, 28 Jul 2006 13:41:07 +0200, Dr.Peer-Joachim Koch wrote:

Well,

the behavior seem's to be related to (my ?) network wide settings.

Using local account on my machine with ssh -X to_the_host -l username everything IS working.

So it's not (only?) a problem of the xterm, but might be related to personal settings. However, the home is located on a NFS share.

Can this be the reason ? (locking the same file ?)

José Luis Ricardo Chávez schrieb:

...

This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows?

- José Luis

-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com