--
Nicholas J A Sanders
_____________________
semiotek
T: +44 [0]7092 153 409
_____________________
What in the world are you talking about? Growl works fine on 10.5. GrowlMail doesn't, but that's because apple has a private plugin setup that they changed, there are workarounds on the forums.Instead of assuming that Growl just plain doesn't work, why not tell us what's actually occurring so that we can try to help you? It'd be appreciated.
ChrisIt's just as I say - two or three days ago Growl notifications stopped altogether. It might therefore be the more correct to say that nothing is occurring, rather than to tell you what is.
(I suppose that my being a mite miffed by your not having responded to the sampling information that I had sent earlier, at your request, may - along with all the other stresses and strains of life - have helped to encourage me to be a degree more cryptic than was entirely appropriate, but nevertheless, there it is, Growl don't , and it's a mystery to me too.)
As before, I'm more than happy to accept your direction in pursuing the reason…
Is anything showing up in /Applications/Utilities/Console for GrowlHelperApp?Is GrowlHelperApp running?What version of Growl do you have installed?
Growl: Standard process of debugging and cool emotions all around go far.1. Is Growl running? (verify in both the preference pane and in Activity Monitor)2. Are your applications added and configured in Growl's Applications tab?3. Are the applications configured appropriately to use Growl? (like Adium's setup instructions)4. Are the applications running and sending notifications (the former is simple to determine, the latter more likely the result of eliminating all of the above)5. What display(s) have been tested? (is it particular to one, or all, or what)Basically we need to clarify your very nebulous 'Growl don't' and the assertion that Growl on Leopard isn't working (which is false) - it's that your computer's particular configuration with Growl, Leopard, and various aspects are not working.Meta: Each discussion should be unto itself, bringing baggage in only leads to additional problems. We are in a neutral medium that doesn't provide implicit contexts - your emotions, your tenses or speaking patterns, your anything else - and lends itself to exactly what is in front of the viewer.
Leopard has reversed all of this.
I have Growl 1.1.2 setup on Leopard (10.5.1 currently and before on
10.5), and GrowlMail has always worked for me (ok I need to write the
defaults thing on the prompt, but that was it). Also Skype works,
OsiriX 3.0fc8 works and all other apps that I'm used to work just fine.
I really don't get why so many people say it does not work. Should I
just count my blessings or something, because it is inexplicable that
it could work? I did an upgrade install of Leopard from Tiger when it
came out. I've seen more trouble coming from fresh Leopard installs
that I never had. Other than that I don't know.
Alexander
I really don't get why so many people say it does not work.
Growl doesn't pull data from applications; applications must push
data to it.
Please try this test app and tell us what happens:
http://boredzo.org/stuph/Simplest_Notifier_Evar-1.0.zip
Brian, if you want me to put that app's source code into the Growl
source directory's Examples subdirectory, I can do that later today.
> 1. Growl is running.
Please verify this: after running the test app above, please run this
script in the Script Editor and tell us the results:
application "GrowlHelperApp" is running
(I want to rule out whether the prefpane is lying.)
Please also run this script (*after* the previous script) and tell us
the results:
path to application "GrowlHelperApp"
> 2. Applications are configured.
>
> 3. Applications are set up just as they were when Growl was working.
Which applications?
Are you talking about in their own preferences, or only in Growl's?
To check whether the helper app is running, use this:
tell application "System Events" to exists process "GrowlHelperApp"
The “is running” command was added in Leopard.
Interesting.
> The script returns "true".
What about the “path to” script?
What about the “path to” script?
Please open the Growl preference pane, switch to the Displays tab,
take a screenshot, and send it to us.
Instructions for taking a screenshot are here:
<http://docs.info.apple.com/article.html?artnum=151947>
These instructions are the same on Mac OS X 10.4 and later, except
that screenshots will be saved as PNG rather than PDF, which is fine.
Instructions for taking a screenshot are here:
Please open the Growl preference pane, switch to the Displays tab,
take a screenshot, and send it to us.
What default did you have chosen? I'd like to get this fixed so that
nobody else has this problem in the future, knowing that will be
important.
>
> 5. Built in 24" display on late-2006 iMac - Growl working on MacBook.
I didn't mean your computer display, I meant your Growl display style,
computer displays would have no relevance. I should have made this
clearer.
>
> In general, you seem to have missed the point that everything was
> fine at one moment, but not the next - you have also invented an
> assertion when I actually posed a question.
No, I didn't. I provided a list of steps to follow to isolate the
problem.
>
> It is more than likely that the issue here is entirely specific to
> my situation so, having no expectations of Growl people (who I have
> been happy to praise on more than one occasion) and having
> previously had specifically requested input ignored, I felt it
> entirely reasonable to use a provocative subject header to get
> attention - it worked. Selfishly, I want Growl back - I hope you
> guys have your own reasons for wanting it back too.
We did, thus my comments.
>
> (On a more personal note Brian, although I absolutely take your
> opening and closing remarks as wholly well meaning they are also
> capable of being taken as patronising - maybe you don't see it now,
> maybe you'll see it later.)
On the forums and mailing lists emotions and frustrations are brought
out unnecessarily. I want this project to be as hassle-free as
possible or it causes others, and myself, to choose to ignore it
because we volunteer our time to code and help users when we can. As I
stated, don't read tone or context or intent - simply the words, which
was basically a list-mom action.
All that said, I'm glad we've found the problem and have a bug that
can be addressed as well (thankfully relatively isolated)
On the forums and mailing lists emotions and frustrations are brought
out unnecessarily. I want this project to be as hassle-free as
possible or it causes others, and myself, to choose to ignore it
because we volunteer our time to code and help users when we can. As I
stated, don't read tone or context or intent - simply the words, which
was basically a list-mom action.
All of these are extraneous and should not have come into play in this thread when the real cause was a missing file. I'm done with this thread, I would hope you are as well.
It is known that Mail doesn't work,
nor does Safari.
On Nov 26, 2007, at 9:13 AM, Alexander Henket wrote:
>
>> It is known that Mail doesn't work,
>
> It may be known to you, but I just told you Growl and GrowlMail work
> on my machine so mileage apparently varies.
I believe "It is known" refers to the fact that I posted a
compatibility page on the forums which stated GrowlMail is
unsupported, so his assertion was perfectly valid. You may not have
experienced a problem yet, but we [the Growl development team] will
not support any version of GrowlMail on Leopard right now or any
problems it causes (Mail had a swath of changes and GrowlMail was
quite fragile.)
>
>> nor does Safari.
>
>
> I don't use GrowlSafari, but I just tried it today indeed that was
> the only one that doesn't work so far.
Thus proving the compatibility page right.
You might not be aware of it, but growlnotify is also broken on
Leopard, as listed in that thread. Now we are all up to speed on what
is and isn't supported.
- brian 'bgannin' ganninger
Alexander