So, Growl 1.4 uses a new, sandboxing friendly, method for handling start at login. Unfortunately, there are some issues with it that are out of our direct control. Apple is aware of these issues, and its not just our app that has them. I realize this isn't much comfort to you, but know that we are working with Apple on them. In the mean time, here are some diagnosis steps, to ensure Growl is properly registered to start at login, use the following command in terminal: launchctl list | grep growl
And in the list, you should see com.growl.GrowlLauncher. That is the helper that launches Growl at login. If it is properly registered, then the issue lies elsewhere and Im not entirely sure what to offer here other than the usual list of OSX repair tools, repair permissions, reset/repair launchd database, and reset/repair user ACL's. On Sep 1, 12:58 pm, greyhound <[email protected]> wrote: > The same thing has happened to me starting a month or two ago. (I think it > was not just at the moment that I bought and installed Growl 1.4, but some > time later.) This is happening on my iMac 10,1 running Lion (10.7.4), and > of course Growl 1.4. Strangely, while Growl starts up at login on the iMac > only 20-25% of the time, on my MacBook Air, running all the same software, > it always starts up. So far. One difference: my iMac logs in > automatically on boot-up, while the MacBook Air requires a manual login > after boot-up, for security reasons. Any ideas out there? -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. 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.
