[SOLVED] Set display on a terminal and run an Xwindow from it

ethereal1m · 01-11-2011, 05:15 AM

Dear all,
I'm trying to run an Xwindow application from terminal but I'm unable to do it.

What I did:

Code:

oracle@firefly:/usr/local/temp/database$ export DISPLAY=:0.0  

oracle@firefly:/usr/local/temp/database$ xhost +
No protocol specified
xhost:  unable to open display ":0.0"

oracle@firefly:/usr/local/temp/database$ xterm
No protocol specified
xterm Xt error: Can't open display: :0.0

Did I miss anything?

Best regards,
ethereal1m

DonnieP · 01-11-2011, 05:22 AM

Is an X server running? Consider this googling result:
http://forums.oracle.com/forums/thre...hreadID=569326

ethereal1m · 01-11-2011, 05:52 AM

Hi Donnie,
when I do ps:

Code:

oracle@firefly:/usr/local/temp/database$ ps -ef|grep X
root      3736  3724  0 14:23 tty7     00:01:56 /usr/bin/X -br -novtswitch -quiet -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-LvVpK5

but when I do xset:

Code:

oracle@firefly:/usr/local/temp/database$ xset -q
No protocol specified
xset:  unable to open display ":0.0"

not sure what's going on. Do you?

Keith Hedger · 01-11-2011, 01:54 PM

If you are on a virtual console just type

Code:

startx -- :1

to start a new X session and then run your x application

ethereal1m · 01-11-2011, 09:09 PM

hi Keith,
is this what you meant?

Code:

[oracle@firefly]$ startx xterm:1
xauth:  creating new authority file /home/oracle/.serverauth.5652
xauth:  creating new authority file /home/oracle/.Xauthority
xauth:  creating new authority file /home/oracle/.Xauthority


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


Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 



Invalid MIT-MAGIC-COOKIE-1 keygiving up.
xinit:  Interrupted system call (errno 4):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

for some reason the shell cannot connect to X server. Any ideas?

ethereal1m · 01-11-2011, 09:22 PM

Oh, I forgot to mention that the terminal runs on KDE if that makes any difference...

ethereal1m · 01-11-2011, 09:41 PM

I solved the problem by doing xhost + in the original shell. Turns out that the fact I did su [username_whatever] from a terminal and tried to do xhost+ there is causing a problem. I must do xhost + from the original shell instead.