startx doesn't start in server

knowNothing23 · 12-05-2014, 05:14 PM

I am ssh -X -i <INFO> to a server.
I have changed ssh config files to allow X11 forwarding in client and server.
My Redhat is version 7

If I type:
$startx

I get:
(EE) xf86OpenConsole: VT_ACTIVATE failed: No such device or address

Relevant output:

Code:

[971105.735] (II) Module glx: vendor="X.Org Foundation"
[971105.735]    compiled for 1.15.0, module version = 1.0.0
[971105.735]    ABI class: X.Org Server Extension, version 8.0
[971105.735] (==) AIGLX enabled
[971105.735] Loading extension GLX
[971105.735] (==) Matched cirrus as autoconfigured driver 0
[971105.735] (==) Matched modesetting as autoconfigured driver 1
[971105.735] (==) Matched fbdev as autoconfigured driver 2
[971105.735] (==) Matched vesa as autoconfigured driver 3
[971105.735] (==) Assigned the driver to the xf86ConfigLayout
[971105.735] (II) LoadModule: "cirrus"
[971105.735] (WW) Warning, couldn't open module cirrus
[971105.735] (II) UnloadModule: "cirrus"
[971105.735] (II) Unloading cirrus
[971105.735] (EE) Failed to load module "cirrus" (module does not exist, 0)
[971105.735] (II) LoadModule: "modesetting"
[971105.735] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[971105.735] (II) Module modesetting: vendor="X.Org Foundation"
[971105.735]    compiled for 1.15.0, module version = 0.8.0
[971105.735]    Module class: X.Org Video Driver
[971105.735]    ABI class: X.Org Video Driver, version 15.0
[971105.735] (II) LoadModule: "fbdev"
[971105.735] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[971105.735] (II) Module fbdev: vendor="X.Org Foundation"
[971105.735]    compiled for 1.15.0, module version = 0.4.3
[971105.735]    Module class: X.Org Video Driver
[971105.735]    ABI class: X.Org Video Driver, version 15.0
[971105.735] (II) LoadModule: "vesa"
[971105.735] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[971105.735] (II) Module vesa: vendor="X.Org Foundation"
[971105.735]    compiled for 1.15.0, module version = 2.3.2
[971105.735]    Module class: X.Org Video Driver
[971105.735]    ABI class: X.Org Video Driver, version 15.0
[971105.735] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[971105.735] (II) FBDEV: driver for framebuffer: fbdev
[971105.735] (II) VESA: driver for VESA chipsets: vesa
[971105.735] (++) using VT number 0

[971105.737] (EE)
Fatal server error:
[971105.737] (EE) xf86OpenConsole: VT_ACTIVATE failed: No such device or address
[971105.737] (EE)
[971105.737] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[971105.737] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[971105.737] (EE)

Also, when I call $X -configure
I get:

Code:

X.Org X Server 1.15.0
Release Date: 2013-12-27
X Protocol Version 11, Revision 0
Build Operating System:  2.6.32-431.5.1.el6.x86_64 
Current Operating System: Linux ip-172-31-60-13.ec2.internal 3.10.0-123.8.1.el7.x86_64 #1 SMP Mon Aug 11 13:37:49 EDT 2014 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-123.8.1.el7.x86_64 root=UUID=668dbd02-c201-44bc-be76-f606fc9ab8db ro vconsole.keymap=us console=ttyS0,115200n8 console=tty0 crashkernel=auto vconsole.font=latarcyrheb-sun16 LANG=en_US.UTF-8
Build Date: 27 February 2014  02:03:18PM
Build ID: xorg-x11-server 1.15.0-7.el7 
Current version of pixman: 0.32.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
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: Fri Dec  5 18:13:30 2014
List of video drivers:
	vmware
	ati
	radeon
	modesetting
	qxl
	v4l
	intel
	nouveau
	dummy
	vesa
	fbdev
(++) Using config file: "/root/xorg.conf.new"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
(EE) Backtrace:
(EE) 0: X (xorg_backtrace+0x55) [0x5917f5]
(EE) 1: X (0x400000+0x195899) [0x595899]
(EE) 2: /lib64/libc.so.6 (0x7f07dc7d4000+0x35640) [0x7f07dc809640]
(EE) 
(EE) Segmentation fault at address 0x0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.

Thank you for your help

michaelk · 12-07-2014, 07:28 PM

Welcome to LinuxQuestions.

What Operating system/version is running on the client? Is it running x windows?

If yes then you can start any GUI application right from the command like xclock. If you want to start the gnome deskstop the you would run gnome-session.

knowNothing23 · 12-07-2014, 07:42 PM

I am ssh into the server from an arch linux machine.
startx is running in the client side.

Do you mean that I need to type 'xclock' once I have ssh into the server?

michaelk · 12-07-2014, 07:55 PM

That was just an example. What are you trying to accomplish?

knowNothing23 · 12-07-2014, 07:57 PM

I want to start the a basic gui for the server.
By gui, I mean just the regular graphic user interface that allows you to use the mouse and keyboard to do stuff rather than using the terminal.

michaelk · 12-07-2014, 08:09 PM

Is a desktop running on the server? If not you need to run startx on the server itself.

knowNothing23 · 12-07-2014, 08:22 PM

I don't think I understand.
So, I have a server running in the cloud. It is an Red Hat instance running on Amazon Web Services.
I ssh into the instance and installed a bunch of software.

I use my latptop to ssh into the server. My laptop is running Arch linux and startx is running in it.

I want to ssh into the server and I want to open up the whole gui features from the server. I achieve this in my latptop when I type startx, so I assume that it would be the same in the server, but errors are thrown.

I have no access to the server other than through ssh.
I don't understand what you mean by "a desktop running on the server". Aren't all server ran by machines.

notKlaatu · 12-07-2014, 09:35 PM

Why not try starting an application, without using startx?
Startx is a very specific command which looks at some config files that you probably do not have, and also will want services that you may not have permission for (or you might; I've never used Amazon cloud so I am not sure). So, as michaelk suggested, maybe just try running a simple application like xclock, xeyes, or xcalc first. If those fail, then we know it's not just startx that is failing.

michaelk · 12-08-2014, 06:03 AM

Desktop is just another term for a GUI. Basically x windows will not run on AWS and can not be used as a desktop like your own computer running Arch.

knowNothing23 · 12-08-2014, 08:28 AM

Why can't it run?
I don't understand. Is this common knowledge?

michaelk · 12-08-2014, 08:51 AM

Sorry.

http://www.idevelopment.info/data/AW...t/AWS_12.shtml

wpeckham · 12-08-2014, 09:15 AM

Have you considered running vncserver in local-only mode and vncviewer over ssh from the client?

There are how-to documents for this, and it is far more likley to give you a useful desktop than startx from remote.

Otherwise, as mentioned above, you can spawn individual applications on the server to display on the client desktop: that is what the ssh Xforward does best.