Repairing permissions and reseting launch services will not solve the problem. It is a permissions problem but not because you have the wrong permissions but because Growl, right off of MAS has the wrong permissions. At least for me. After way too much time wasted trying to get it to work properly, com.growl.GrowlLauncher appears when launchctl list | grep growl is ran.
Run "launchctl list | grep growl" first before doing the simple instructions below so you can see it not appear and then appear after changing permissions on Growl.app bundle. *Fix*: Highlight Growl.app in your applications folder. Click the '+' sign and add administrators. Give administrator Read & Write permissions. Go to growl general prefs. Switch start at login slider from off then BACK so it reads ON. Run the "launchctl list | grep growl" command again and there it is. You can probably revert permissions back to how they were after it writes to launchd, I have not tried it yet but I believe once it's written it will stick. Please let others know if this works for you so they can fix it as well. Don't know much about launchd but thanks to those who advised checking with "launchctl list | grep growl" -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/VraShryONPoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
