Bug 93677 - Xquartz El Capitan Dropped ssh Connections
Summary: Xquartz El Capitan Dropped ssh Connections
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.8 (xserver-1.16.4)
Hardware: Other Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
Depends on:
Reported: 2016-01-12 15:37 UTC by Dave
Modified: 2016-01-12 17:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

attachment-30708-0.html (2.10 KB, text/html)
2016-01-12 17:44 UTC, Dave

Description Dave 2016-01-12 15:37:29 UTC
With the apparent move to El Capitan, XQuartz keeps dropping my ssh connections to LINUX machines after a certain period of time.  The exact error is 

packet_write_wait: Connection to <IP address>: Broken pipe

On Yosemite I used 'ssh -Y' and was never dropped.  I have no idea if this is an El Capitan problem or an unexpected interaction between El Capitan and XQuartz.  I am curious is anybody else has reported this issue and if there was a resolution.
Comment 1 Jeremy Huddleston Sequoia 2016-01-12 17:17:56 UTC
This is an ssh "feature," has nothing to do with X11, and is not new to El Capitan.  Read up on ForwardX11Timeout.
Comment 2 Jeremy Huddleston Sequoia 2016-01-12 17:19:51 UTC
I suggest you set:

ForwardX11Timeout 596h
Comment 3 Dave 2016-01-12 17:44:05 UTC
Created attachment 120989 [details]

Thanks.  Will give it a try.

On 1/12/16 12:19 PM, bugzilla-daemon@freedesktop.org wrote:
> *Comment # 2 <https://bugs.freedesktop.org/show_bug.cgi?id=93677#c2> 
> on bug 93677 <https://bugs.freedesktop.org/show_bug.cgi?id=93677> from 
> Jeremy Huddleston Sequoia <mailto:jeremyhu@freedesktop.org> *
> I suggest you set:
> ForwardX11Timeout 596h
> ------------------------------------------------------------------------
> You are receiving this mail because:
>   * You reported the bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.