What to do? logs: Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Running on Darwin Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Starting Red5 Oct 28 14:33:07 macserver soffice.bin[9062]: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login. Oct 28 14:33:07 macserver soffice.bin[9062]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Fri Oct 28 14:33:07 macserver.private soffice.bin[9062] <Warning>: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login. Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Fri Oct 28 14:33:07 macserver.private soffice.bin[9062] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. Oct 28 14:33:07 macserver /Applications/OpenOffice.org.app/Contents/ MacOS/soffice.bin[9062]: _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL. Oct 28 14:33:07 macserver com.openmeetings.start[9059]: _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL. Oct 28 14:33:08 macserver com.openmeetings.start[9059]: Red5 root:
http://developer.apple.com/library/mac/#technotes/tn2083/_index.html Pre-Login Trust Issues If, in Mac OS X 10.5 and later, you see a message like that shown in Listing 9 you might mistakenly think that the solution is to get the system to 'trust' your application, perhaps via code signing. Listing 9 Pre-Login Trust Message Untrusted apps are not allowed to connect to or launch Window Server before login. However, this isn't the case (r. 5544764) . This message is really telling you is that you're trying to connect to the window server from the wrong context. You see this message if you try to connect to the global window server service from outside of the pre-login context before the user has logged in; typically this means that you're trying to use the window server from a daemon. You should not attempt to fix this by convincing the window server to trust your program; doing so will just cause other problems further down the road. For example, if you do successfully connect to the window server from your daemon, you still have to deal with window server lifecycle issues described previously. Instead, you should fix this problem by changing your code to run in the correct context. If you need to connect to the window server in a pre-login context, create a pre-login launchd agent. For an example of this, see Sample Code 'PreLoginAgents'. -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-user@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
