Summary: | ssh -X hostname fails with repeating crashes on MacOS Sierra 10.12.6 | ||
---|---|---|---|
Product: | XQuartz | Reporter: | Steve McMillan <steve> |
Component: | Other | Assignee: | Jeremy Huddleston Sequoia <jeremyhu> |
Status: | RESOLVED INVALID | QA Contact: | Jeremy Huddleston Sequoia <jeremyhu> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 2.7.11 (xserver-1.18.4) | ||
Hardware: | Other | ||
OS: | Mac OS X (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | attachment-23145-0.html |
Description
Steve McMillan
2017-07-20 23:05:43 UTC
You probably have a configuration problem. Check the FAQ on xquartz.org, and ask for help on the mailing list if you need it. If you're actually seeing a bug in ssh, you should file a bug against OpenSSH. Created attachment 132809 [details] attachment-23145-0.html The problem occurred after the most recent MacOS beta update. I don’t think XQuartz or ssh have changed. I’ve reported it to Apple. Too many ways for the buck to be passed here… I can’t find a FAQ on quartz.org, by the way. > On Jul 20, 2017, at 7:40 PM, bugzilla-daemon@freedesktop.org wrote: > > Jeremy Huddleston Sequoia <mailto:jeremyhu@freedesktop.org> changed bug 101862 <https://bugs.freedesktop.org/show_bug.cgi?id=101862> > What Removed Added > Status NEW RESOLVED > Resolution --- INVALID > > Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=101862#c1> on bug 101862 <https://bugs.freedesktop.org/show_bug.cgi?id=101862> from Jeremy Huddleston Sequoia <mailto:jeremyhu@freedesktop.org> > You probably have a configuration problem. Check the FAQ on xquartz.org, and > ask for help on the mailing list if you need it. If you're actually seeing a > bug in ssh, you should file a bug against OpenSSH. > > You are receiving this mail because: > You reported the bug. Stephen L. W. McMillan Department Head and Professor of Physics, Drexel University +1 215-895-2709/2723, FAX +1 215-895-2940, steve@physics.drexel.edu |
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.