[SOLVED] Xserver in fedora 17, displaying from remote server.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Xserver in fedora 17, displaying from remote server.
I'm working on switching from win* to linux as my desktop at work. The only thing I'm struggling with is how I get a servers display to mine. I'd run Xserver client in win*, from cmdline of linux server, I'd export the display to my desktop and launch away.
There is -X in ssh but I find it not working after several jump boxes. I find articles to modify the Xaccess file, but I'm not finding that. I have x11-server (and other x11-packages), gdm and Xdmcp installed. Am I just missing a package or did something change from the days of Xaccess settings?
I'd prefer to continue with the method of setting access restrictions since it's now an open port, if not start/stop a service for when required. I'd like to continue to set the display on the remote machine for sending displays back. I just feel I'm missing something that I'm not terming right for google/LQ.
It doesn't when I ssh from server to server. I use -X on each one and it's not following the pathway back. I do the same thing on a win* VM and export display and it works using mochaX. I'm sure it's possible, but I can't find any Xaccess file on my fedora or how to make it to say, listen for inbound.
works fine for me. No DISPLAY setting, nothing at all, through a chain of 6 different Linux machines running a combination of Fedora and CentOS.
Could you use ssh -v to print more debugging output? What are the error messages you get when you try to launch an X application? Perhaps you placed something in your shell startup scripts to hard-code the DISPLAY for your previous win client?
If verbose ssh helps, I'll run that. Here's the quick snip-it without.
[mmcc0912@desktop ~]$ ssh -X firstname.lastname@example.org
Last login: Wed Jan 30 10:39:38 2013 from IP
[me@ogismgmt1 ~]$ ssh -X root@oraapps1-test
Last login: Tue Jan 29 20:47:19 2013 from IP
[root@oraapps1-test ~]# xclock
Error: Can't open display: localhost:0.0
[root@oraapps1-test ~]# echo $DISPLAY
There are some things that I'm just not familiar with yet, I've spent all my time without a GUI. The method has always been to export the DISPLAY and send it where I wanted to see it. Everything I can find so far is the same as above link. Maybe I'm not searching with the correct words.
Ok, I misread your initial question, missing the fact you're ssh-ing from one point to another.
I just tried it here, and don't have a solution, but got a slightly different message:
root@serenity:~# emacs /etc/ssh/ssh_config
X11 connection rejected because of wrong authentication.
Display localhost:10.0 unavailable, simulating -nw
I don't know what you were thinking of, but rereading your question and following posts, you mention it works fine under Win. I was thinking the problem was at the server end, but perhaps it is at the local end. I hope this suggestion is of help to you.
Did you try doing the same using -Y instead of -X, just to see if it works?
It would have to be listening in some means to to accept connections. The remote server above is a RHEL 4.8 where my system is fedora17. I setup the remote system and installed nothing special, just Xserver and gnome.
Thanks for the attention to my post. I appreciate it. I've been googling it for some time and just haven't found the how do I make X listen that's applicable.
Interesting, on my installation that comes set as yes as default.
I had missed that before, mmcc0912 in your case you're going to have to check the server config on every server along the way. Only one server having that set to "no" or commented out somewhere is going to stop you.
sshd creates the X forwarding by opening a TCP port (6000+offset specified from sshd config file+increment to find unused port). That port is then passed to the X clients using the DISPLAY environment variable (value is localhost:<port-6000>.0). Any other value causes an access failure due to improper credentials.
The usual offset value is 10, to skip a possible 10 locally based TCP X servers. The first port used by sshd should then be 6010... with an increment of one for each sshd that may be forwarding that users X applications. The display environment value should be "localhost:10.0" for the first ssh login forwarding windows. 11.0 for the second.
The credentials should be shown by a "xauth list", one for each key. If you are logged in remotely, with X forwarding there would normally be only one key. It is possible to get multiple keys... just login a second time through another ssh login...
The fact that you have a DISPLAY value of other than localhost:10.0 (or 127.0.0.1:10.0) implies that some login script is forcing the environment value to a wrong number. DISPLAY is one of the few variables that should not be modified except for extremely good reasons - usually related to testing.
I appreciate the responses, I can forward from the server to a windows host running an Xserver (mochaX). I can't find jack on how to enable Xserver in fedora to listen so that I can send the display back to my fedora box. Well, what I do find doesn't fit the system, the files it says to modify don't exist... Either something has changed, or I don't have the right packages installed, IMHO.
Right now I'm using mochaX in a TS/rdesktop session in windows. But my desktop has several monitors and it's just a functional thing to me that I should be able to send it directly to my desktop (Linux to Linux vs. Linux to Windoze).
I appreciate the responses, I can forward from the server to a windows host running an Xserver (mochaX). I can't find jack on how to enable Xserver in fedora to listen so that I can send the display back to my fedora box.
It already is, there's nothing you have to do to make that happen. You should be able to install Fedora from scratch on two different machines, ssh -X from one machine to the other (assuming the sshd server is running on the destination machine), and open an X application without a problem.
As both myself and jpollard pointed out, your DISPLAY environment variable does not look correct. Are you SURE that you didn't hard-code anything in your log in scripts on the remote servers to force DISPLAY to some non-default value?
Last edited by suicidaleggroll; 02-05-2013 at 03:14 PM.