In Beta 4, the launcher does not start on Linux.
This is as far it gets:
2011-02-16 13:51:56: BEGIN - chipmunk\mgriffith
2011-02-16 13:51:56: Start-up
2011-02-16 13:51:56: 2011-02-16 13:51:55
2011-02-16 13:51:56: Deadline Launcher 5.0 [v5.0.0.43942 R]
2011-02-16 13:51:56: Launcher Thread - Launcher thread initializing...
2011-02-16 13:51:56: Perfoming remote admin check
2011-02-16 13:51:56: Remote Administration is now enabled
2011-02-16 13:51:56: Launcher Thread - Remote administration is enabled
2011-02-16 13:51:56: Launcher Thread - Launcher thread listing on port 5042
It hangs after that point, and the GUI does not show up, not even a splash screen.
Just checked, this is still an issue with Beta 5
Other than the “listing” typo, I don’t see any problems…
Can you check your deadline.ini file (~/Deadline/deadline.ini) to see if you have “LaunchLauncherGuiAtStartup” specified in there? If it is, and it’s set to False, that would probably explain the problem.
Cheers,
Ah, that was it! Although, the auto-upgrade didn’t occur when the GUI wasn’t going.
Cheers!
-Matt
The auto-upgrade only triggers when other Deadline applications are run via the launcher. Running the launcher itself won’t trigger the upgrade. If the Launcher UI is visible, you can just launch something from the Launch menu to upgrade. The alternative is to use the command line. For example:
deadlinelauncher -monitor
deadlinelauncher -slave
The command line method will work regardless of if the Launcher UI is visible.
Cheers,
Hmmm, somehow I’ve been observing different behaviour (which has been the source of my confusion). I’ve been starting (or restarting) the launcher by itself to initiate the self upgrade, which has worked. I’ve never started a secondary application via launcher to get the upgrade going. I got confused when the launcher didn’t show up and start the auto-upgrade (not sure how that ini gui key got set. Good to know about though!).
Thanks for the clarification 
Cheers!
-Matt