This is a long standing annoying bug which is related to apple events in macOS. Operating system can sometimes end up in a bad state where apple events are not being delivered to Finder. This prevents TotalFinder from injecting code into Finder.
I have been having this problem for the last week. Your latest update 1.6.21 did not solve it!
Ah :-/ Can you please follow this post and report Console.app log?
TotalFinder 1.6.23 has fixed another startup issue and should be good.
@Paul_Wilkinson It would be great if you could confirm that the problem went away.
I was getting the message before, but it didn’t seem to affect much of anything. TotalFinder totally shut down on me at version 1.6.22. and just kept crashing and freezing. Those times that it actually launched, when ever I would right click, it would freeze.
I did what you asked Paul to do and here’s what console had to say: link to pastebin. I didn’t leave anything out, so it’s a bit long…
I updated to 1.6.23. and for some reason the issue just continued. After relaunching and opening totalfinder like dozen times, now it seems to work…
Thanks for posting your log. All looks good there. Since line mentioning “agent v1.6.23 started” all worked as expected (at least what I can see in the log).
After it continued to work just fine, I figured I’d try to recreate the issue. I relaunched finder and opened totalfinder like ~20 times in a row and every time the very first right click froze it.
The console didn’t give me anything about it, as far as I could decipher, so I decided to reboot and then decided to try and relaunch it multiple times, just like I did before. It seems to be working now.
Hi Darwin, Sorry for delay in replying.
Works like a dream. All gone! Thanks for solving this!
1 Like
v1.6.25 won’t install with this error, leaves Finder hung, and Finder cannot be “Relaunched” necessitating a reboot.
Console is a complete mess with com.apple.xpc/launchd errors. Failed install, even after reboot, left system in a really bad state vis a vis launchd.
Crap.
Steve
Hi Steve,
I’m sorry for the troubles, but TotalFinder has nothing to do with launchd. The problem must be related to some other change you did to your system.
Also we could look at your install.log if you could find it at /var/log/install.log or go to Console.app and from the list of logs on the left side pick /var/log -> install.log
I’m having the same issue here - everytime I try to update to Total Finder 1.6.27, the Finder becomes unresponsive and everything stops working. Looking in console.app, I see the following:
6/8/15 12:56:10.471 PM osascript[2131]: ApplePersistence=NO
6/8/15 12:56:10.000 PM kernel[0]: Over-release of kernel-internal importance assertions for pid 2130 (syncdefaultsd), dropping 1 assertion(s) but task only has 0 remaining (0 external).
6/8/15 12:56:12.429 PM TotalFinder[2103]: [debug] trying to acquire TotalFinder lock
6/8/15 12:56:12.430 PM TotalFinder[2103]: [debug] target apps (
"<NSRunningApplication: 0x618000109c60 (com.apple.finder - 256)>"
)
6/8/15 12:56:12.431 PM TotalFinder[2103]: [debug] target app is <NSRunningApplication: 0x618000109c60 (com.apple.finder - 256)>(terminated=0, pid=256)
6/8/15 12:56:12.431 PM TotalFinder[2103]: [debug] sending injection events to Finder[256] bundleID=com.apple.finder (trial #47)
6/8/15 12:56:12.431 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'ascr'\'gdut'{ }>
6/8/15 12:56:12.431 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'BATF'\'init'{ }>
6/8/15 12:56:14.429 PM TotalFinder[2103]: [debug] trying to acquire TotalFinder lock
6/8/15 12:56:14.431 PM TotalFinder[2103]: [debug] target apps (
"<NSRunningApplication: 0x60000010c180 (com.apple.finder - 256)>"
)
6/8/15 12:56:14.431 PM TotalFinder[2103]: [debug] target app is <NSRunningApplication: 0x60000010c180 (com.apple.finder - 256)>(terminated=0, pid=256)
6/8/15 12:56:14.431 PM TotalFinder[2103]: [debug] sending injection events to Finder[256] bundleID=com.apple.finder (trial #48)
6/8/15 12:56:14.431 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'ascr'\'gdut'{ }>
6/8/15 12:56:14.432 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'BATF'\'init'{ }>
6/8/15 12:56:16.428 PM TotalFinder[2103]: [debug] trying to acquire TotalFinder lock
6/8/15 12:56:16.429 PM TotalFinder[2103]: [debug] target apps (
"<NSRunningApplication: 0x60000010c180 (com.apple.finder - 256)>"
)
6/8/15 12:56:16.429 PM TotalFinder[2103]: [debug] target app is <NSRunningApplication: 0x60000010c180 (com.apple.finder - 256)>(terminated=0, pid=256)
6/8/15 12:56:16.429 PM TotalFinder[2103]: [debug] sending injection events to Finder[256] bundleID=com.apple.finder (trial #49)
6/8/15 12:56:16.430 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'ascr'\'gdut'{ }>
6/8/15 12:56:16.430 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'BATF'\'init'{ }>
6/8/15 12:56:18.427 PM TotalFinder[2103]: [debug] trying to acquire TotalFinder lock
6/8/15 12:56:18.429 PM TotalFinder[2103]: [debug] target apps (
"<NSRunningApplication: 0x618000109c60 (com.apple.finder - 256)>"
)
6/8/15 12:56:18.429 PM TotalFinder[2103]: [debug] target app is <NSRunningApplication: 0x618000109c60 (com.apple.finder - 256)>(terminated=0, pid=256)
6/8/15 12:56:18.429 PM TotalFinder[2103]: [debug] sending injection events to Finder[256] bundleID=com.apple.finder (trial #50)
6/8/15 12:56:18.429 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'ascr'\'gdut'{ }>
6/8/15 12:56:18.430 PM TotalFinder[2103]: [debug] ~~> <NSAppleEventDescriptor: 'BATF'\'init'{ }>
6/8/15 12:56:20.427 PM TotalFinder[2103]: [debug] trying to acquire TotalFinder lock
6/8/15 12:56:20.429 PM TotalFinder[2103]: [debug] target apps (
"<NSRunningApplication: 0x61000010aef0 (com.apple.finder - 256)>"
)
6/8/15 12:56:20.429 PM TotalFinder[2103]: [debug] target app is <NSRunningApplication: 0x61000010aef0 (com.apple.finder - 256)>(terminated=0, pid=256)
6/8/15 12:56:20.429 PM TotalFinder[2103]: [debug] launching shell command: osascript -e "tell application \"Finder\" to «event BATFinit»"
over and over and over…
Any suggestions for what to do to resolve this?
Hi Darwin, sorry to say this, but its happened again twice in the last few days. I will monitor and let you know if it comes back regularly. Cheers.
Alas TF 1.7.0, El Capitan Beta2. Workaround doesn’t work.
I’m sorry. TotalFinder no longer works under El Capitan Beta2. Apple decided to block injections into Finder.app.
Please read On System Integrity Protection in El Capitan, OSX 10.11 for more info.
Just got the latest upgrade - and install FAILED. the error message took me to this page… Tried this workaround, but it hasn’t done anything… whats it supposed to do? Im in OS X 10.10.3
1 Like
On El Capitan Developer Preview 5 i just received a weird error message, when i try to run the app manualy, which says:
“TotalFinder is not open anymore”… and also the appleevents notification.
I’ve been having this exact problem since yesterday’s update. Even going back to an earlier version didn’t fix the problem. 1.7.3 has fixed it. TotalFinder launched right away without issue.
On OSX 10.10.5 - had issues with finder lag - so I removed ~/Library/Preferences/com.apple.finder.plist. TotalFinder crashed, and now won’t startup. Unintalled & reinstalled thinking maybe there was some setting that was a dependency and only written on installation, however TotalFinder still won’t startup.
It generates a system notification that sends me to this thread.