Can't open display, though DISPLAY defined...

Can't open display, though DISPLAY defined...

Post by doug a blaisde » Sat, 13 Jul 1996 04:00:00



Hi y'all--
Just getting X set up... I can exec things from system.fvwmrc OK,
but not from the command line, eg:

root> echo $DISPLAY
darkstar:0.0
root> oclock
Xlib: connection to "darkstar:0.0" refused by server
Xlib: Client is not authorized to connect to Server
Error: Can't open display: darkstar:0.0
root>

Anyone know what's going on here? I looked in the X FAQ, but
couldn't find anything relevant.

                         yer fellow Linux lover,
                                                 doug

 
 
 

Can't open display, though DISPLAY defined...

Post by Dan Wiedenbe » Sat, 13 Jul 1996 04:00:00



: Hi y'all--
: Just getting X set up... I can exec things from system.fvwmrc OK,
: but not from the command line, eg:

: root> echo $DISPLAY
: darkstar:0.0
: root> oclock
: Xlib: connection to "darkstar:0.0" refused by server
: Xlib: Client is not authorized to connect to Server
: Error: Can't open display: darkstar:0.0
: root>

: Anyone know what's going on here? I looked in the X FAQ, but
: couldn't find anything relevant.

Try this:

xhost +darkstar

Dan.
--

#define LocalRulesFile <Motif.rules>

 
 
 

Can't open display, though DISPLAY defined...

Post by John Wiggi » Wed, 17 Jul 1996 04:00:00


I have added /dev/tty9-12 and can now run multiple x
servers via xinit --:1, 2, etc. but any way to do it so that
it automaticaly knows which one to use?  Otherwise, I get a
device 0 lock error.
--
    Gunther Dragon --=(UDIC)=-- John Wiggins  

 
 
 

Can't open display, though DISPLAY defined...

Post by Daniel-Marian Baboi » Wed, 17 Jul 1996 04:00:00




> : but not from the command line, eg:
> : root> echo $DISPLAY
> : darkstar:0.0
> : root> oclock
> : Xlib: connection to "darkstar:0.0" refused by server
> : Xlib: Client is not authorized to connect to Server
> : Error: Can't open display: darkstar:0.0
> : root>

> Try this:

> xhost +darkstar

Better use:
DISPLAY=:0.0; export DISAPLAY

This sets the DISPLAY to point to the local host, whatever this is.
If you leave DISPKAY to point to darkstar:0.0, you will also need to set
an alias for darkstar to the local host.

--

-------------------------------------------------
Daniel-Marian Baboiu
University of Central Florida / CREOL
4000 Central Florida Blvd
Orlando, FL 32816-2700
407-823-6919       Fax: 407-823-6955

--------------------------------------------------

 
 
 

1. Problem: 'can't open display'-error message

Hi,

I have a problem using Linux and remote graphical display. Maybe someone
can help me? I installed the Slackware 3.0 distribution, and the system
seems to work perfectly. Except for the following :-(

My problem:
I want to use graphical display information from a sg (sg1) on my Linux
computer (pc). However, when I start a graphical program it tells me:
      'can't open display'.

Here is what I do:
pc:   rsh sg1
sg1:  setenv DISPLAY pc:0.0
pc:   xhost +sg1
sg1:  winterm
[I actually get the sg1-winterm screen on my pc-screen at this time, so
env variables are set correctly (?)]
sg1:  xv (or any other program)

This is the result:
      'xv: can't open display'

Someone can gimme a clue?

Thanks in advance,
Rene van Donkelaar,


2. SS5 and Solaris 7 != Network connectivity

3. Can't display xterm on another display

4. which utilities come with freebsd 2.2.7 to partition a hard drive ???

5. "Can't open display" on Debian 3.0's X-Windows

6. latest kdebug?

7. xsetroot: unable to open display ''

8. Tekram P6B40D-A5 Problem With Dual 350s

9. FreeBSD 4.6.2 Xfree86 4.2.0 with gnome2 can't open display

10. Can't open display, IN SPITE OF xhost

11. can't open display question

12. XF86 problem (Can't open display)

13. Error: Can't open display: