cocoaforge

Blergh, it turns out the culprit is BBEdit. I don't suppose there's a way I can just swap out the Growl.framework inside the application with a newer one?

Is there any way to trawl through the growlRegDict files or the console to determine which applications are at fault? I have a few likely suspects in mind, but I'm concerned it may be more than one application using old frameworks.

In 1.2, this is still happening.

Any updates from the developers? This has been going on for a shockingly long time.

That permissions repairing did the trick. After applying the changes, a quick restart of Safari was all it took for it to end up in my Growl applications list again.

Many thanks for the fix! While 1.1.3 itself seems to run smoothly, that install seems to have been a [i]bit[/i] of a mess :\

Nothing at all; the only evidence I have that it's installed is that I can see it in the /Library/InputManagers folder. I can see when GrowlMail starts up, but nothing Growl related happens when either Safari starts up, or the entire system (restarted and scoured the logs for any references)

GrowlSafari doesn't seem to be showing up at all after installation. It's not registering in Growl, it's not seemingly doing anything. I'm running Safari 3.1.1, Mac OS 10.5.3.