Ah, ok -- I've got a Growl for Windows installation in a virtual machine for getting Outlook notifications via the network to Growl; and it was frozen up. Killing and restarting it didn't do anything for the problem; neither did removing the notification forwarding and re-adding it.
I also tried stopping growl, turning off network notifications and turning it back on (both stopping growl through the pref pane and killing it in activity monitor). On Mon, Dec 14, 2009 at 2:47 PM, Peter Hosey <[email protected]> wrote: > On Dec 13, 2009, at 19:42:19, Bob wrote: >> No, nothing like that -- the only crash around that time was in >> quicklookd (thanks to a corrupt .mkv video). > > > On further reflection, that makes sense; the form of registration > handling your sample showed doesn't match a local registration (which > would go through Apple Events, as noted in Cyberduck's Console output). > > This was more probably a network registration. Do you have any > machines running network Growl clients? Alternatively, do you have any > machines set to forward notifications to the machine where Growl is > not working? > > If so, please check those machines for crash logs from December 11th. > > -- > > 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. > > > -- -- Bob -- 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.
