Christopher and Peter, it is Growl*Mail, not growl itself. Moving the bundle from ~user/Library/Mail/Bundles/GrowlMail.mailbundle into ~user/Library/Mail/Bundles (Disabled)/GrowlMail.mailbundle solved the issue for me. Possible to post a link to the discussions you mention for someone like me who is new here and has non idea about development thread? Thanks H
On Feb 27, 4:34 am, Peter Hosey <[email protected]> wrote: > On Feb 26, 2009, at 05:09:50, tjl wrote: > > > Removing Growl solves the problem. The Apple OS X system error panel > > correctly ID's Growl as the issue. > > Growl, or Growl*Mail*? > > GrowlMail comes with Growl, but it is not Growl, so if the problem > really is GrowlMail (as we suspect you mean), please don't misidentify > it. > > Also, if it is GrowlMail, then it's a known problem and we have a fix > which we will release as part of 1.1.5. > > > I have this info to Apple. > > That doesn't help us at all, since they don't share crash logs with > us. If it's really Growl and not GrowlMail, please send the crash logs > to us. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
