SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org. Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).
XFree86 Version 4.3.99.902 (4.4.0 RC 2)
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux linux 2.6.4-52-smp #1 SMP Wed Apr 7 02:11:20 UTC 2004 i686
Build Date: 23 August 2004
Changelog Date: 29 February 2004
Before reporting problems, check http://www.XFree86.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/XFree86.0.log", Time: Sun May 8 03:14:51 2005
(==) Using config file: "/etc/X11/XF86Config"
(WW) I810(0): Failed to set up write-combining range (0xf0000000,0x8000000)
Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list!
X is run locally. Applications that use X are then run remotely by, for example, tunneling X over ssh.
For example, let's say that you have a Linux machine at home, and want to run an X application remotely from your Windows machine at work.
First, start X on Windows. If you need X for Windows, you can download the free cygwin package, which includes Xorg.
Second, ssh from the Windows machine to the Linux machine, requesting that X be tunneled:
ssh -Y userid@host
After you login, you can run any X application, and it will display on your Windows machine. For example, if you want to run the evolution email program:
evolution &
If you are trying to run an X application on a Linux/*BSD/UNIX machine, X is already there. Just start at the ssh.
Then you didn't select it during the installation.
Rerun the Cygwin setup, and in the "Net" section, select openssh. Also make sure that in the X11 section, you've selected the x-startup scripts. The requisites should be automatically selected.
As a followup, this is the sequence of actions you need to take to run a remote X application:
1.Start Windows
2. Run cygwin. This establishes the environment.
3. At the cygwin bash prompt, enter the command startx. This will bring up the local X. An xterm window will open.
4. In the xterm window, ssh to the destination machine, with the "-Y" option. For example:
ssh -Y someuser@somehost
5. When you are logged into the remote system, you can run any X application, and it will display on your local system.
I am getting this error though:
abefro@linux:/root> export DISPLAY=69.211.121.xx:0
abefro@linux:/root> xhost +127.0.0.1
xhost: unable to open display "69.211.121.xx:0"
I think there are some security settings that prohibit the use of the X server from remote locations. In /etc/X11/xdm/Xservers you may have to remove '-nolisten tcp' and in /etc/X11/xdm/xdm-config you may need to comment-out the line 'DisplayManager.requestPort: 0'. Since I have never tried this, I can't tell which one ot those is really required.
I tried running xhost locally and get the same error:
xhost: unable to open display "10.10.0.251:0"
xhost: unable to open display "localhost:0"
xhost: unable to open display "localhost:0.0"
xhost: unable to open display "10.10.0.251:0.0"
No, no, the command xauth knows where to find .Xauthority. The parameter 'keyfile' is just the filename where you would like to extract the key to. Sorry if my post was confusing.
It stil doesnt seem to be working:
linux:~ # >keyfile
linux:~ # xauth extract keyfile 10.10.0.252:0
No matches found, authority file "keyfile" not written
As far as I can see, you are logged in as root. This way xauth assumes .Xauthority in /root. Try the command as user. I edited the above post. Have a look at the link first, maybe the xhost method will work after you applied the changes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.