Re: [growl-discuss] Growl does not automactily start at login
725 views
Skip to first unread message
Chris Forsythe
Jun 9, 2012, 12:32:37 PM6/9/12
to growld...@googlegroups.com
Remove GrowlHelperApp, that's Growl 1.2.2 and below.
There is a way to start Growl, through the Growl General preferences at growl://preferences/general . This will use a newer function than Startup Items in Growl 1.4+.
On Saturday, June 9, 2012 at 6:25 AM, jmbreitigan wrote:
Hi, I have version 1.4 installed from the App Store. I have start Growl at login turned on in Growl preferences. When I look at my login items in my sytem preferences I see GrowlHelperApp with a yellow triangle with a note that it can't find this item. I assume this is why it will not start at login. Any ideas?
I found the Growl application and selected it this way in my start up at login window and it now starts at login. But when I look at my login items to start up at login in system preferences I do not see Growl even thought i did select it prior ?? I do not have the check box for reopen all windows when restarting checked. I would like this to work as advertised. Where is the GrowlHelperApp ?
John
--
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/-/F_geeBDbPwAJ.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
Daniel Siemer
Jun 11, 2012, 4:05:17 PM6/11/12
to Growl Discuss
Growl 1.4 will no longer appear in your login items in System
Preferences. We are preparing for 2.0 which will be sandboxed, and we
will no longer be able to access that list. The method 1.4+ uses
installs an item into launchd for running on login, which then
launches Growl.
On Jun 11, 10:37 am, Evgeniy Yablokov <etc.gu...@gmail.com> wrote:
> +1, I have a same problem. Tried uninstall it (via CleanMyMac), reboot,
> install (via Mac Appstore) and reboot. Same result - I can start it by
> hands only.
>
>
>
>
>
>
>
> On Monday, June 11, 2012 5:37:07 PM UTC+4, Joe wrote:
>
> > Hello I updated yesterday Growl 1.4 from Mac app store.
> > Now when I turn off and turn on my mac and when I restart Growl does not
> > start automatically.
> > The item "Growl start at boot" is ON.
> > I try going to system preferences and adding Growl in the boot options but
> > after the first boot removed from the list and is still experiencing the
> > same.
> > What can I do?
Preferences. We are preparing for 2.0 which will be sandboxed, and we
will no longer be able to access that list. The method 1.4+ uses
installs an item into launchd for running on login, which then
launches Growl.
On Jun 11, 10:37 am, Evgeniy Yablokov <etc.gu...@gmail.com> wrote:
> +1, I have a same problem. Tried uninstall it (via CleanMyMac), reboot,
> install (via Mac Appstore) and reboot. Same result - I can start it by
> hands only.
>
>
>
>
>
>
>
> On Monday, June 11, 2012 5:37:07 PM UTC+4, Joe wrote:
>
> > Hello I updated yesterday Growl 1.4 from Mac app store.
> > Now when I turn off and turn on my mac and when I restart Growl does not
> > start automatically.
> > The item "Growl start at boot" is ON.
> > I try going to system preferences and adding Growl in the boot options but
> > after the first boot removed from the list and is still experiencing the
> > same.
> > What can I do?
Charlie S
Jun 11, 2012, 9:30:10 PM6/11/12
to growld...@googlegroups.com
I seen one person report doing a repair disk permissions might have fixed it for them
--
----
Charlie Schloss
Grab Opera the fastest browser on earth @
http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop
Why Open the Web?
Despite the connecting purpose of the Web, it is not entirely open to all of
its users. When used correctly, HTML documents can be displayed across
platforms and devices. However, many devices are excluded access to Web
content.
http://my.opera.com/community/openweb/info/
On Mon, Jun 11, 2012 at 11:37 AM, Evgeniy Yablokov <etc....@gmail.com> wrote:
+1, I have a same problem. Tried uninstall it (via CleanMyMac), reboot, install (via Mac Appstore) and reboot. Same result - I can start it by hands only.
On Monday, June 11, 2012 5:37:07 PM UTC+4, Joe wrote:Hello I updated yesterday Growl 1.4 from Mac app store.
Now when I turn off and turn on my mac and when I restart Growl does not start automatically.
The item "Growl start at boot" is ON.
I try going to system preferences and adding Growl in the boot options but after the first boot removed from the list and is still experiencing the same.
What can I do?
--
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/-/x8T8f9PIavwJ.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
--
----
Charlie Schloss
Grab Opera the fastest browser on earth @
http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop
Why Open the Web?
Despite the connecting purpose of the Web, it is not entirely open to all of
its users. When used correctly, HTML documents can be displayed across
platforms and devices. However, many devices are excluded access to Web
content.
http://my.opera.com/community/openweb/info/
Daniel Siemer
Jun 11, 2012, 10:46:12 PM6/11/12
to Growl Discuss
Did you look in launchctl via the command line? launchctl list | grep
growl and it should list a com.growl.GrowlLauncher. If it isn't
there, there are various troubleshooting techniques, including the
standard repair permissions, and resetting/cleaning the launchd
database (Can be done by a gui utility such as Cocktail, or if you
want to, via command line).
On Jun 11, 6:31 pm, Keith Kastorff <kasto...@gmail.com> wrote:
> I'm using Growl 1.4 from the App Store, and Growl does not start at login
> even though the preference is set. I don't have an entry in launchd. This
> is a bug if setting the preference is supposed to add one.
growl and it should list a com.growl.GrowlLauncher. If it isn't
there, there are various troubleshooting techniques, including the
standard repair permissions, and resetting/cleaning the launchd
database (Can be done by a gui utility such as Cocktail, or if you
want to, via command line).
On Jun 11, 6:31 pm, Keith Kastorff <kasto...@gmail.com> wrote:
> I'm using Growl 1.4 from the App Store, and Growl does not start at login
> even though the preference is set. I don't have an entry in launchd. This
> is a bug if setting the preference is supposed to add one.
Daniel Siemer
Jun 12, 2012, 10:24:28 AM6/12/12
to Growl Discuss
In general, please send replies to the thread in question so that all
can benefit from the response.
In order to use launchctl to check if GrowlLauncher is registered
properly, do the following:
Open Terminal.app (Its in /Applications/Utilities)
At the command prompt, paste the following:
launchctl list | grep growl
If there is no output at all, that is because GrowlLauncher is not
registered. If Growl's start at login switch is in the on position,
it should be listed, and there is something wrong with your Launchd
system, either permissions, or a corrupt launchd database.
If it lists com.growl.GrowlLauncher, then it should be working as
intended. If Growl is listed, and is not starting at login, again,
launchd may be corrupt, or you may have a permissions problem. Also,
this system I believe works best when Growl is installed in /
Applications, so if you've moved it out to any other directory, try
moving it back there and toggling the switch off and back on.
To repair permissions:
Open Disk Utility.app (also in /Applications/Utilities) and select
your hard drive (the named partition, such as Macintosh HD) in the
list at the left, then select "Repair Disk Permissions" and let it
run.
To fix Launchd database corruption, run a utility such as Cocktail (a
third party app, http://maintain.se/cocktail) and use its repair
Launch Services Database function. There is also a command line way
to do this, but it is more involved to explain.
On Jun 12, 2012, at 5:32 AM, Joe wrote:
Daniel, how do you do that?
can benefit from the response.
In order to use launchctl to check if GrowlLauncher is registered
properly, do the following:
Open Terminal.app (Its in /Applications/Utilities)
At the command prompt, paste the following:
launchctl list | grep growl
If there is no output at all, that is because GrowlLauncher is not
registered. If Growl's start at login switch is in the on position,
it should be listed, and there is something wrong with your Launchd
system, either permissions, or a corrupt launchd database.
If it lists com.growl.GrowlLauncher, then it should be working as
intended. If Growl is listed, and is not starting at login, again,
launchd may be corrupt, or you may have a permissions problem. Also,
this system I believe works best when Growl is installed in /
Applications, so if you've moved it out to any other directory, try
moving it back there and toggling the switch off and back on.
To repair permissions:
Open Disk Utility.app (also in /Applications/Utilities) and select
your hard drive (the named partition, such as Macintosh HD) in the
list at the left, then select "Repair Disk Permissions" and let it
run.
To fix Launchd database corruption, run a utility such as Cocktail (a
third party app, http://maintain.se/cocktail) and use its repair
Launch Services Database function. There is also a command line way
to do this, but it is more involved to explain.
On Jun 12, 2012, at 5:32 AM, Joe wrote:
Daniel, how do you do that?
Chris Forsythe
Jun 13, 2012, 4:14:15 AM6/13/12
to growld...@googlegroups.com
That's actually a really good summary. Neat. :)
On Tuesday, June 12, 2012 at 6:34 PM, gordon245 wrote:
I was curious how/why Growl was doing things this way, so I did a little digging. The following article is extremely helpful:In a nutshell:
- Sandboxed (i.e., any App Store apps) apps can't access the file that controls Login Items.
- Instead, they provide a helper application that lives in the main app bundle in Contents/Library/LoginItems (this approach documented here.)
- The SMLoginItemSetEnabled function can be used to register the helper app with launchd so that it runs on user login. The helper app launches the main app before terminating.
- Apps that use this approach do not show up in Login Items.
--
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/-/R6emB-iYe5sJ.
Reply all
Reply to author
Forward
0 new messages