fort at October 28th, 2013 19:34 — #1
Hi all. Since I upgraded to Mavericks, TotalTerminal has not been loading on startup. Instead, I get a dialog popping up that says "AppleEvent timed out". To get TT working, I have to run Terminal then run TT and wait a while. I've tried reinstalling TT, with no luck.
Any help much appreciated.
nomizzz at October 28th, 2013 21:32 — #2
I'm having the same issue on Mavericks (using the current TotalTerminal version, 1.4.4)
darwin at October 29th, 2013 05:50 — #3
Unfortunately I have no good solution for you right now. This was also happening to some TotalFinder users and I had to rewrite launching script into ObjectiveC helper app. It resolved most of the issues.
I'm going to do similar thing for TotalTerminal eventually. But it has not priority right now. Please try to experiment with adding/removing items from your login startup items, or change delay in the script.
ricw at October 30th, 2013 14:16 — #4
Same issue here. Extremely annoying
ernie_a_oporto at October 30th, 2013 17:22 — #5
What worked for me was to run the installer for TotalTerminal after a reboot. It works, but it’s annoying.
darwin at October 31st, 2013 06:28 — #6
I have re-evaluated this issue and I will fix it in 1.4.5. I will use the same code I have used in TotalFinder which fixed similar problems for majority of TotalFinder users. Stay tuned.
fort at October 31st, 2013 13:26 — #7
I got it working again by increasing the delay in the script to 5. It might work with lower numbers but I didn't try since this worked for me first time.
darwin at October 31st, 2013 13:40 — #8
These issues should be fixed in 1.4.5:
Please test it and report back.
fort at November 2nd, 2013 08:25 — #9
It's not working for me. TT isn't loading on startup at all and, although I don't get the timeout error, I have to load Terminal first and then TT, in order to get it to work. The pity is that I had got the previous version working.
darwin at November 2nd, 2013 08:37 — #10
Do you have TotalTerminal.app in your login startup items? Is it really TotalTerminal.app coming with 1.4.5 release? In you Console.app you should see something like:
11/2/13 12:40:41.659 PM Terminal: TotalTerminalInjector v1.4.5 received init event
fort at November 2nd, 2013 09:30 — #11
I do see that, but presumably it logs that if you run TT manually, no? Here's what gets logged:
I'll try another clean install and see if it works.
fort at November 2nd, 2013 10:18 — #12
The clean install did it - it's loading on startup, as it's supposed to now. Thanks for making TotalTerminal compatible with Mavs so quickly!
pnomolos at November 4th, 2013 16:00 — #13
I'm getting the same issue, but I'm seeing the following in Console.app:
11/4/2013 13:02:50.086 Terminal: AppleEvents/sandbox: Returning errAEPrivilegeError/-10004 and denying dispatch of event BATT/init from process 'TotalTerminal'/0x0-0x2d02d, pid=356, because it is not entitled to send an AppleEvent to this process.
darwin at November 5th, 2013 14:58 — #14
@pnomolos Please make sure your TotalTerminal.app is in
/Applications and not in
~/Applications, also look into
~/Library/ScriptingAdditons there should be no trace of
TotalTerminal.osax. I assume you might have installed some historic versions and moved them around. This applescript error usually happens when apps from user folder try to talk to system apps in system directories.
pnomolos at November 5th, 2013 18:58 — #15
The TotalTerminal.osax scripting addition that was hanging about is what was causing the issue, thanks for the fix!