Growl forward message crash

[Francisco Garcia]

I have two macs at home. I noticed that the application crashes every
time one mac forwards a notification to the other one (with/without
firewall)


The receiver settings allows inbound connections.

If I do:

> growlnotify -m foo -H myhost.ip

Everything is fine. It only crashes if I do not wait some seconds
after typing in the command


> growlnotify -m foo

Only displayed on the local mac.

However if I set "forward notifications" to my other computer. The
message is forwarded but the application crashed some seconds letter
on the mac that started the message

[Matt Cowger]

I get the same behavior, and if I look at the Console I see that
GrowlHelper has Sig 11'd.

Note that I personally only get this if my VPN is running.

On Jan 6, 5:59 am, Francisco Garcia <pub...@francisco-garcia.net>
wrote:

[George C]

Seeing similar issues here with forwarded notifications.

On Jan 6, 8:59 am, Francisco Garcia <pub...@francisco-garcia.net>
wrote:

[TJ Luoma]

I am seeing this behavior as well.

Both computers running OS X 10.7.3

Both with Growl 1.3.3

Both with growlnotify --version = "growlnotify 1.3"

I mitigated this somewhat by telling launchd to keep Growl running no
matter what (http://f.luo.ma/launchd/com.tjluoma.alwayson.Growl.plist)
but it's still annoying.

Using --host 127.0.0.1 seems to prevent it from crashing. Not sure if
that's new information or not.

TjL


ps - previous messages in thread, for those who might need it:

http://groups.google.com/group/growldiscuss/browse_thread/thread/c3d45863ab377d93/802acf9559b74f49?lnk=gst&q=growlnotify+crash#802acf9559b74f49