Hello, so Growl 1.4 is a transition release with regards to the Start at Login feature. While Growl 1.4 is not sandboxed, Growl 2.0 is, and after we are sandboxed, we will no long be able to influence the Start at Login list in your user preferences. There is a new method for doing launch at login that is sandbox friendly. When you add the item to the start at login list manually, when growl launches again, we detect that, and upgrade you to the new method, and delete the old so you don't wind up with two things trying to launch growl. Growl 2.0 will no longer do this, and the start at login switch will only be tied to the new method.
The new sandboxing friendly method uses launchd to start a launcher for us, which then launches Growl. Unfortunately launchd is an annoying beast that likes to screw up, no matter how right our code is (And believe me, we aren't the only app developer facing this issue). To check if the new launcher is registered properly, you can use the following command in terminal: launchctl list | grep growl And if its been added properly, you should see in the result an entry with the identifier com.growl.GrowlLauncher. If it isn't getting registered, there are some things you can try, repair permissions, repair your launchd database (can be done using a utility like cocktail if you prefer), and repair the user acl list. On Aug 31, 7:18 pm, Bobby Thompson <[email protected]> wrote: > I've had this happen more than once, and can seemingly re-create it every > time... > > If I turn auto load in growl off, Quit the Program, then go back in and try > to re-enable it, the switch will show on but if I log out & back in it will > NOT load... > > No matter what I do I cannot get Growl to load on login... I even go as > far as to turn off auto load & add growl to login items in system > preferences... > > Upon loading, Growl will automatically turn the auto load switch on then > REMOVE the entry from login items. Again if I then log out then log back > it, Growl does NOT load... > > The only solution is to fully delete Growl and all related items (styles, > preferences), reboot, re-download Growl and re-configure it from scratch. > One this is done it will work as expected, but if I ever disable auto load > for any reason I end up in the same place all over again... > > I'm using the most current version of grows (1.4) and the latest version of > Mac OS X (10.8.1)... > > The install I'm using is a clean format and install that I setup a couple > weeks ago. This same problem happened to me on my prior image which was an > upgrade install of 10.8... -- 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.
