LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   startx has problem (http://www.linuxquestions.org/questions/linux-networking-3/startx-has-problem-4175472925/)

windstory 08-10-2013 08:19 PM

startx has problem
 
I want to connect remote Linux with local windows through ssh and kde using xmanager. The remote Linux is Centos 5.4 x86 and local windows is Windows 8 x64.

Using this command I tried to connect.
Quote:

ssh -2 -c blowfish -X testeuser@testeuser.org -p 5769
And the result of "startx" is this.
Quote:

[testeuser@testeuser ~]$ startx
xauth: creating new authority file /home/testeuser/.serverauth.12113


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-308.24.1.el5 i686 Red Hat, Inc.
Current Operating System: Linux testeuser 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:23:01 EDT 2011 i686
Build Date: 09 January 2013
Build ID: xorg-x11-server 1.1.1-48.100.el5
Before reporting problems, check http://wiki.x.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/Xorg.0.log", Time: Sat Aug 10 15:11:01 2013
(==) Using config file: "/etc/X11/xorg.conf"
(WW) ATI(0): Failed to set up write-combining range (0xf6000000,0x800000)
(WW) ATI(0): Failed to set up write-combining range (0xf6000000,0x800000)
FATAL: Module mach64 not found.
[drm] failed to load kernel module "mach64"
(EE) ATI(0): [dri] DRIScreenInit Failed
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Multiple symbols for level 1/group 1 on key <I5F>
> Using XF86Sleep, ignoring XF86Standby
> Warning: Symbol map for key <I5F> redefined
> Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
Could not init font path element unix/:7100, removing from list!
localuser:testeuser being added to access control list
And the result of searching X is this.
Quote:

And the result of searching X is this.
[root@testeuser ~]# ps -ef | grep X
root 6204 6198 0 17:07 tty8 00:00:01 /usr/bin/X -br :0 vt8 -auth /var/run/xauth/A:0-46sTtD
500 6340 6283 0 17:07 ? 00:00:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "/usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients"
500 6375 1 0 17:07 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
root 8057 8045 0 Aug08 tty7 00:00:05 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7
root 18486 29715 0 17:12 pts/7 00:00:00 grep X

Any helpful comment would be appreciated.

Thanks in advance.

PTrenholme 08-11-2013 12:26 AM

startx is a program to start an X server on the local system. In your case, the local system is Windows 8, and the Windows kernel does not (generally) support Linux kernel functions and X-server display commands.

Not being a Windows user, I have no idea what you need to do to get remote X server display commands interpreted on a Windows system.

windstory 08-11-2013 11:19 PM

Please understand Xmanager is X-server for Windows.

And I got another error message:
Quote:

$ /usr/bin/xterm -ls -display $DISPLAY
/usr/bin/xterm Xt error: Can't open display: localhost:12.0

TB0ne 08-12-2013 10:36 AM

Quote:

Originally Posted by windstory (Post 5007551)
Please understand Xmanager is X-server for Windows.

Right...so, you DON'T run 'startx' on the remote Linux host, since that would (as the name implies), start the x server on the machine where you entered that command. And either it's already running there, or can't...which in this case, is immaterial.

Make sure your Xmanager program is running on Windows...how you do that/configure it is up to that piece of Windows software. On the remote Linux system, type in "export DISPLAY=<IP address of Windows system>:0", then run whatever X windows program you'd like. What does the software manual for the Xmanager program tell you?

PTrenholme 08-12-2013 05:07 PM

So, did you read this tutorial? (I didn't read it all, not being a user of the product, but just a few seconds on Google found it.)

windstory 08-12-2013 09:10 PM

TB0ne/
I tried and the result is this.

[root@testeuser ~]# export DISPLAY=xxx.xxx.61.203:0
[root@testeuser ~]# startx
xauth: creating new authority file /root/.serverauth.7942


Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.

Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
giving up.
xinit: unable to connect to X server
xinit: No such process (errno 3): unexpected signal 2.
[root@testeuser ~]# rm -rf /tmp/.X0-lock
[root@testeuser ~]# startx
xauth: creating new authority file /root/.serverauth.8206

_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
giving up.
xinit: unable to connect to X server
xinit: No such process (errno 3): unexpected signal 2.

PTrenholme/

Yes I read the tutorial, and followed.

TB0ne 08-13-2013 09:43 AM

Quote:

Originally Posted by windstory (Post 5008188)
TB0ne/
I tried and the result is this.

[root@testeuser ~]# export DISPLAY=xxx.xxx.61.203:0
[root@testeuser ~]# startx
xauth: creating new authority file /root/.serverauth.7942

Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.

Right...AGAIN, as I posted before, you do NOT HAVE TO RUN STARTX. X is already running on the Linux machine...that's it. Run the APPLICATION you want to run, such as xclock or whatever other GUI/X-Windows based program.
Quote:

PTrenholme/
Yes I read the tutorial, and followed.
Did you?? Because there is NO MENTION of running startx in that tutorial anywhere.

windstory 08-14-2013 07:25 PM

TB0ne/

Quote:

[testeuser@testeuser ~]$ /usr/bin/xterm -ls -display $DISPLAY
/usr/bin/xterm Xt error: Can't open display: localhost:10.0
I tried this xterm command, but I got an error. So I tried startx.

TB0ne 08-15-2013 10:38 AM

Quote:

Originally Posted by windstory (Post 5009439)
TB0ne
Code:

[testeuser@testeuser ~]$ /usr/bin/xterm -ls -display $DISPLAY
/usr/bin/xterm Xt error: Can't open display: localhost:10.0

I tried this xterm command, but I got an error. So I tried startx.

Ok, are you reading/understanding what we're trying to tell you??? From post #4, I specifically said:
Quote:

Originally Posted by TB0ne
On the remote Linux system, type in "export DISPLAY=<IP address of Windows system>:0", then run whatever X windows program you'd like

You haven't done it, so it's not working. Startx will NEVER, EVER WORK the way you're trying to run it. AGAIN, type in the command given to you above (twice now), then try to run Xterm.

Unless you export the display variable, it is going to default to the remote system.

windstory 08-15-2013 10:00 PM

TB0ne/

The result is this::

Quote:

[root@testeuser ~]# export DISPLAY=xxx.xxx.61.203:0
[root@testeuser ~]# /usr/bin/xterm -ls -display $DISPLAY
/usr/bin/xterm Xt error: Can't open display: %s

TB0ne 08-16-2013 10:22 AM

Quote:

Originally Posted by windstory (Post 5010108)
TB0ne/
The result is this::
Code:

[root@testeuser ~]# export DISPLAY=121.151.61.203:0
[root@testeuser ~]# /usr/bin/xterm -ls -display $DISPLAY
/usr/bin/xterm Xt error: Can't open display: %s


AGAIN:
Just run the COMMAND, after exporting the variable. That would be just "xterm". Try xclock first and see what you get...no flags, no switches, nothing....JUST THE COMMAND.

If it doesn't work, then your X emulator on Windows is having a problem...contact the software vendor you purchased it from. Did you configure the SSH parameters, like the tutorial PTrenholme pointed you to in post #5 told you to? The very first step is configuring the SSH daemon on the Linux system, and restarting it.

windstory 08-18-2013 07:57 PM

TBOne/

The result for xclock is this:
Quote:

[testeuser@testeuser ~]$ export DISPLAY=xxx.xxx.61.203:0
[testeuser@testeuser ~]$ xclock
Error: Can't open display: 121.151.61.203:0

And the "sshd_config" of remote Linux is this:
Quote:

Port 5769
Protocol 2

SyslogFacility AUTHPRIV
PasswordAuthentication yes
ChallengeResponseAuthentication no

GSSAPIAuthentication yes
GSSAPICleanupCredentials yes
UsePAM yes

AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL
AllowTcpForwarding yes
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
PermitTunnel yes
Subsystem sftp /usr/libexec/openssh/sftp-server

TB0ne 08-19-2013 11:17 AM

[QUOTE=windstory;5011614]TBOne/
The result for xclock is this:
Code:

[testeuser@testeuser ~]$ export DISPLAY=xxx.xxx.61.203:0
[testeuser@testeuser ~]$ xclock
Error: Can't open display: 121.151.61.203:0

...which is a VERY clear indicator that the workstation at address 121.151.61.203 does not have a working X server on it. So, either your X emulation software isn't working correctly or hasn't been set up correctly. There's nothing to configure/change on the Linux server to make this work, period. Contact the vendor who you bought that X emulator software from, and get support.
Quote:

And the "sshd_config" of remote Linux is this:
...which looks correct.

windstory 08-19-2013 10:46 PM

I installed virtualbox and installed Centos 6.2 x64 as a guest on virtualbox.

I opened terminal and tried to connect as follows:

Quote:

[root@maestro Documents]# ssh -Y testeuser.org -p 5769
Address xxx.xxx.57.28 maps to testserver.xxx.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
root@testeuser.org's password:
Last login: Mon Aug 19 10:06:01 2013 from xxx.xxx.61.203
[root@testeuser ~]# xlogo
Error: Can't open display: localhost:12.0

John VV 08-19-2013 11:13 PM

Quote:

I installed virtualbox and installed Centos 6.2
Why ??
6.2 is a dead and unsupported version of cent
the current and ONLY supported version in the 6 series is 6.4


All times are GMT -5. The time now is 12:19 PM.