Re: Having difficulty exporting display

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



And now it works :) .  Thank you.


On Sun, Jul 7, 2013 at 10:04 PM, linuxsupport <lin.support@xxxxxxxxx> wrote:

> Have you installed xorg-x11-xauth ?
>
>
> On Mon, Jul 8, 2013 at 6:55 AM, Yves S. Garret
> <yoursurrogategod@xxxxxxxxx>wrote:
>
> > Hi, sorry for the very long response, but to answer your question,
> > set | grep DISP outputs nothing.  I still can't get the display to
> > output.
> >
> > This is what happens when I try to export firefox:
> > $ ssh someuser@xxxxxxxxxxxxxxxx firefox
> > someuser@xxxxxxxxxxxxxxxx's password:
> > Error: no display specified
> > $ ssh -X someuser@xxxxxxxxxxxxxxxx firefox
> > someuser@xxxxxxxxxxxxxxxx's password:
> > Error: no display specified
> > $ ssh -Y someuser@xxxxxxxxxxxxxxxx firefox
> > someuser@xxxxxxxxxxxxxxxx's password:
> > Error: no display specified
> >
> >
> > On Mon, Apr 22, 2013 at 6:09 AM, Anthony K <akcentos@xxxxxxxxxx> wrote:
> >
> > > On 19/04/13 06:42, Yves S. Garret wrote:
> > > > Hello,
> > > >
> > > > This is my issue, my remote machine (CentOS 6.3, hosted in Azure
> > windows
> > > > environment) has an application that I need to test on my local box
> > > (CentOS
> > > > 6.4, a laptop behind a router).
> > > >
> > > > Now, this is what I'm doing and the issue that I'm encountering:
> > > > Local:
> > > > $ xhost +
> > > > $ ssh -X someusername@xxxxxxxxxxxxxxxx -p 49283
> > > I don't believe you need to export DISPLAY, it should already be set by
> > > virtue of using -X.  Try omitting the export below and just run xclock.
> > > That ought to work.
> > >
> > > When you log in, what does set|grep DISP output?I always get the
> > > following output:
> > > DISPLAY=localhost:10.0
> > >
> > > And all my GUI apps end up on my local desktop!
> > >
> > > > Remote:
> > > > $ export DISPLAY=192.168.1.6:0.0
> > > > $ xclock
> > > >
> > > > ... and nothing, it just sits there and no xclock shows up :( .  I'm
> > > fairly
> > > > convinced
> > > > that this is due to my router, but I don't know how to deal with it.
> >  Any
> > > > ideas?  Am I
> > > > way off in my guess?
> > > > _______________________________________________
> > > > CentOS mailing list
> > > > CentOS@xxxxxxxxxx
> > > > http://lists.centos.org/mailman/listinfo/centos
> > >
> > > _______________________________________________
> > > CentOS mailing list
> > > CentOS@xxxxxxxxxx
> > > http://lists.centos.org/mailman/listinfo/centos
> > >
> > _______________________________________________
> > CentOS mailing list
> > CentOS@xxxxxxxxxx
> > http://lists.centos.org/mailman/listinfo/centos
> >
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux