> Meelis Roos wrote:
>
> > $ glxinfo
> > name of display: localhost:10.0
> > Xlib: connection to ":0.0" refused by server
> > Xlib: Client is not authorized to connect to Server
> > display: localhost:10 screen: 0
> > direct rendering: No
> >
> > If the display is different from :0.0 (:1.0, remote
> display, whatever)
> > then GLX initialization tries to connecxt to :0.0 and
> fails. Sometimes
> > this takes time, depending on user configuration. For example, on my
> > home computer I have to wait quite a long for this :0.0
> connect timeout
> > for some reason when running GLX things on :1.0. I have seen this
> > behaviour several times and today I decided to find out
> what's wrong.
i am thinking of something like this for your case:
export DISPLAY=localhost:1.0
or something similar like this:
glxgears --display=:1.0
thats the way you can launch X programs on a specific
desktop from a different X-Server (e.g. trough a VNC session)
or even from the console or a remote shell (ssh, telnet, ...).
Regards Alex.
...maybe i missed the point here...
if you find any typos - they are a free gift.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
