First, apologies for the long break...real life interfered with a vengeance...
2nd apologies because as it turned out that Growl had nothing to do with the card error I was debugging at the time. 3rd clarification: you asked On Dec 17 2010, 4:40 pm, Peter Hosey <[email protected]> wrote: > On Dec 17, 2010, at 06:22:24, eve wrote: > What do you mean by “Growl Hardware”? HardwareGrowler > > … and since then I had regular crashes connected to the new card. > > What do you mean by “crashes”? At the time, I had several types of hangs/crashes. The one provoked by the card would supposedly freeze the machine so no mouse movements were possible anymore and the only thing left to do was push the button. Supposedly, because it actually froze the screens only and not the machine. Later on and still going on only when I run Growl, I had my machine do a "slow crash" in that program after program would stop responding until the machine ground to a halt and the only thing left would be to push the button. No crash or panic log though. The very last input in the console log was a list of the msgs as pasted in my 1st post. Also, this machine is the receipient of remote notifications coming from a mini (10.6.4, Growl vanilla 1.2.1) running the monitoring program Simon. As I just found the way to turn off logging in Growl, I did that and I guess, I'll see in a day or 2 whether that worked. Also, I did find the threads talking about Growl having a problem with remote notification and that will be the next thing to turn off if disabling the logs doesn't work. If neither works, I'll be asking for ideas again. -- 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.
