I tried to start ID CS6 today and it hung during "Startup Services". It gave me a "serious error" message stating and the only option to choose was "Return to Finder". I restarted the computer and it started up but once the toolbars loaded it hung with a "spinning beachball". Trashing caches, temp files, prefs and turning off font management resulted in the same hang. Here's my crash log. http://pastebin.com/fhYqX9cM
I'm not very good with the sample process reports (and John Hawkinson doesn't come around as much as he used to). The crash report shows ID doing something with Digital Publishing just before the crash, though. Are your DP plugins up to date?
The other thing I noticed, and it may not be relevant, is that you are running suitcase. Try removing the suitcase plugin and see if that makes a difference.
I thought the suitcase thing might have worked, so I deleted it as I was no longer using Suitcase, but I had had Font explorer running, too. So I removed both plugins. After the hang I described above, forcing the app to quit will not allow me to get back to the panels loading with out trashing caches and things. It crashes early on with a crash log viewable here. http://pastebin.com/u6dE5g9Z
I think we've seen that crash a few times, and I don't recall the cause, if we even know.
You say you force quit? You could have damaged recovery data causing a problem, so find and empty or rename the InDesign Recovery folder in your user library.
Well, not that it helps, but after disabling the plugins, cleaning the font cache, deleting the caches and temp files still no go. I then logged in with a guest account, opened ID fine. Logged back in to my main account, and ID launched fine. I reenabled my FEX plugin and it still worked fine.
That indicates a problem in the other user profile. Inaddition to trashing the prefs, see http://forums.adobe.com/message/4315274 for John's list of other files to trash, and if you didn't emptythe recovery folder, do it. All bets are off if there is bad data in that folder.
I suspected that, but once I logged in to the guest account, and back into the problematic user account, I had no problems with ID. So the problem is solved, but I'm not sure what solved it. I had done all the steps above to no avail. The only thing new I did was open the guest account and then launch ID from there before launching from my problematic user account.