hg: macosx-port/macosx-port/jdk: Fix for MACOSX_PORT-765: Unable to run an GUI app remotely.

[Mike Swingler]

On Dec 4, 2011, at 12:13 AM, alexander.zuev at oracle.com wrote:

> Changeset: c50bdc544e22
> Author:    kizune
> Date:      2011-12-04 12:13 +0300
> URL:       http://hg.openjdk.java.net/macosx-port/macosx-port/jdk/rev/c50bdc544e22
> 
> Fix for MACOSX_PORT-765: Unable to run an GUI app remotely.
> Do not issue error on awt.dylib loading if we detect that process is initiated by remote or daemon process.
> 
> ! src/macosx/native/sun/awt/awt.m

I don't get it. Why didn't you just remove the +[AWTStarter isConnectedToWindowServer] check if you are going to allow all possible launch modes? Why do the extra work of asking for the session all over again? Is there some failure modes you are still filtering against?

FYI, if you allow the Cocoa AWT to load when run from an SSH or daemon initiated session you _will_ get failures later when trying to use the Cocoa API when you are not logged in as console user. Perhaps this check needs to be re-thought to force headless if the session checks tell us we are not logged in as a console user?

Regards,
Mike Swingler
Apple Inc.