Im not sure as to why it would show up once and then disappear after next reboot, other than possibly some issue with launchd. As for GrowlHelperApp, Growl.app's bundle ID is still com.Growl.GrowlHelperApp due to backwards compatibility issues. There is a way to reset your launchd database, to see if it was corrupted, using either a utility such as Cocktail, or the command line.
On Sep 30, 4:04 pm, Linda Cline <[email protected]> wrote: > I'm running Growl 2.0 on Lion 10.7.5. I was previously running Growl 1.3 > with no issues, though this was an install over 1.2.2, I believe. I have > tried cleaning all traces of 1.2.2 and 1.3 from my system, and reinstalling > 2.0 from the MAS. I launch Growl.app, bring up the preferences and make > sure that start at login is enabled (and have disabled and reenabled it > repeatedly). When I restart the system, Growl does not get launched. > > After a restart, before I launch Growl manually, "launchctl list | grep > *rowl*" returns nothing. > After I start Growl manually, the same command returns "886 - > [0x0-0x84084].com.Growl.GrowlHelperApp" > If I bring up Growl preferences, and turn off start at login, and then turn > it back on again, the same command returns the above, as well as "- 0 > com.growl.GrowlLauncher" > > After that when I restart, once again, Growl does not get launched, and the > sequence is the same as above. > > I thought GrowlHelperApp was no longer used in 2.0? Any other things I can > try to get this working? > > Thanks. -- 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.
