SSH tunnelled X sessions become unresponsive.
Adam Jackson
ajackson at redhat.com
Mon Mar 26 13:55:52 UTC 2007
On Fri, 2007-03-23 at 23:02 +0000, Andy Burns wrote:
> On 23/03/07, Adam Jackson <ajackson at redhat.com> 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
More information about the fedora-devel-list
mailing list