Re: SSH tunnelled X sessions become unresponsive.

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

 



On Fri, 2007-03-23 at 23:02 +0000, Andy Burns wrote:
> On 23/03/07, Adam Jackson <ajackson@xxxxxxxxxx> wrote:
> > My usual method for debugging this sort of thing is to use wireshark to
> > see which side's network traffic is stopping.
> 
> that sounds, errm ... fun, I wouldn't recognize good X protocol over
> the wire if it slapped me, I'll give it a go though, otherwise I can
> see that I might end up without remote GUI when F7 comes out, I've put
> an xming bug into fd.o bugzilla just in case too.

wireshark has a built-in decoder for X.  If you filter on port 6000 then
you'll only see the X traffic, and examining packet timestamps should be
enough to tell you where the stall is happening.

- ajax

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux