cocoaforge

pboreham wrote:So perhaps apps dont show on the list until they are 'called' for the first time?

Applications don't show in the list until they register. Usually, this is either on launch or when they first post a notification.

bridgestew wrote:Any ideas what could be causing this?

Safari 4 beta.

Is anyone else having this problem?

Yes:

• http://forums.cocoaforge.com/viewtopic.php?f=6&t=19522
• http://forums.cocoaforge.com/viewtopic.php?f=6&t=19487
• http://forums.cocoaforge.com/viewtopic.php?f=6&t=19467

Yes. 1.1.5 is now in beta.

Well Omnifocus's website video indicates it functions with it! So attempted to use with same. NO GO! Only functions with Backup Notification and no others even though programmed for other notification selections. DONT BOTHER, less u enjoy life as a guinea pig! Have you reported your problems to the...

No, this is not currently in any release. I've filed a bug (https://bugs.launchpad.net/growl/1.2/+bug/361502) and attached katzlbt2's replacement script. It'll be in 1.2 if we don't find anything wrong with it (and I don't see anything wrong with it on a quick look).

vox wrote:Am I right in assuming that'll come soon in a 1.1.5 update then?

1.1.5b1 will be out tomorrow. I don't yet know whether I'll have it in by then.

About 15/20 there for you. Unfortunately, there was no symbol information in these crash logs, so it's impossible to say what the crash was. I do plan to switch to a different method of recording symbol information; when we release a version with that change, crash logs you obtain on that version w...

vox wrote:I have plenty of crash logs if you would like them.

We would.

I've been seeing GrowlHelperApp quit a lot. Here are a few crash logs: http://maz.nu/fs/crash-0.txt http://maz.nu/fs/crash-1.txt ...et cetera, up to... http://maz.nu/fs/crash-5.txt Yeah, those are a couple crashes that several people have reported, but we have absolutely no clue on. In one of them,...

terryjfundak wrote:HERE'S THE TERMINAL

You should post this on the other thread. It's more appropriate there, as it has nothing to do with an empty applications list.

terryjfundak wrote:I don't understand the above. Do you mean with Activity Monitor - Take a sample when it locks up?

Yes.

I have two machines that are working together but I was only successful doing this after I removed the Server password in the NETWORK>Allow remote application registration>Server Password: BLANK HERE. Is there same sort of rules for the password? Using UDP or DO? The [notification window]s pile up ...

terryjfundak wrote:So what would you recommend for a person such as myself...

Certainly not writing a Growl plug-in. growlnotify will already do the job, once you get it to work (I see in your other threads that you're having problems with it).

I'm not sure, should growlnotify show up on the client machine? It is not the target for the notices, another machine is so is it necessary to have growlnotify register? No, growlnotify doesn't need to register on the client machine. It will register on the server machine. All machines have current...

terryjfundak wrote:What is DNC?

Distributed Notification Center. We used to use it as the medium for Growl notifications. We still support it, but the framework only uses it as a fallback, and I think we should remove it at some point.

The_Tick wrote:I could swear we provided a way for the misattempt at a dashbaord widget to get growl notifications in some way.

Perhaps it relied on the DNC?

Update: Adding the -w option (--wait) and sending the process to the background causes growlnotify to work every time: $ growlnotify -w --image ~/.autotest.d/fail.png -m "Tests Failed" & Hopefully, this piece of information helps debug the underlying issue. I already found the underly...

We need to be able to reproduce it to be able to find it and fix it. If we can't reproduce it, we can't fix it. Good news! I've written a hammer script that slams the GrowlHelperApp with 30 (by default) growlnotifies at once. With this, I'm able to get it to drop most of the notifications. As I pre...

We need a growlnotify command that tries, and fails 100% of the time, to post a notification. That sounds like a bit of an unfair request, considering this problem is an intermittent one. We need to be able to reproduce it to be able to find it and fix it. If we can't reproduce it, we can't fix it....

~HP wrote:

Code: Select all

> growlnotify --version
> which growlnotify

I don't think either one of those commands will reproduce the problem. ☺

We need a growlnotify command that tries, and fails 100% of the time, to post a notification.