Hi,
Since upgrading to Sierra the other day I randomly get errors about the
display not being found when launching apps from a Linux machine. When I
logout and log back in to the remote machine things work again, but then
after some time the problem reappears.
Is this a known issue?
Haroon
On Thu, Sep 22, 2016 at 2:48 PM, Haroon wrote:
> Since upgrading to Sierra the other day I randomly get errors about the
> display not being found when launching apps from a Linux machine. When I
> logout and log back in to the remote machine things work again, but then
> after some time the prob
I don't think that is it.
Today I had one app open and then tried to launch another. The former app
kept running, but the console spit back a display cannot be found error
when I attempted to launch the second. I closed the first app and
attempted to relaunch it -- but it wouldn't.
I kille
This just happened.
I have two apps open. Both are running and functioning normally.
I go to open a third. I get the display not found error.
I open a new SSH session *without* closing the old one. The apps keep
running, and I am able to open the third app in the new SSH session.
I close
On Thu, Sep 22, 2016 at 3:24 PM, Haroon wrote:
> I don't think that is it.
>
> Today I had one app open and then tried to launch another. The former app
> kept running, but the console spit back a display cannot be found error
> when I attempted to launch the second. I closed the first app and
Brandon Allbery writes:
> That would be the exact symptoms of the X11ForwardTimeout issue; the older
> app will keep its display but new ones will be rejected.
Yeah. Maybe the connection to the Sierra upgrade is that the updater
failed to carry over some config file in which the OP had fixed thi
Are there any log files that I could look at (on either end) to help me
verify whether this is indeed the problem?
On Thu, 22 Sep 2016, Tom Lane wrote:
Brandon Allbery writes:
That would be the exact symptoms of the X11ForwardTimeout issue; the older
app will keep its display but new ones wil
On Thu, Sep 22, 2016 at 5:03 PM, Haroon wrote:
> Are there any log files that I could look at (on either end) to help me
> verify whether this is indeed the problem?
It's actually the client end doing this (since the client has the X server
being forwarded) so I can't see it being based on a ch
It's definitely client side. I logged into the same server on a Snow
Leopard machine and did not have the same problem.
I looked at my /etc/ssh directory and no modifications were made there
since 2015, so it doesn't seem that Sierra overwrote anything. What I
think happened is that the defa
On Thu, Sep 22, 2016 at 8:19 PM, Haroon wrote:
> I looked at my /etc/ssh directory and no modifications were made there
> since 2015, so it doesn't seem that Sierra overwrote anything. What I
> think happened is that the defaults in the binary for ssh have changed in
> Sierra. One way to verify
10 matches
Mail list logo
