This really isn't going to help unfortunately. The best workaround for now is to force quit Growl and then restart it until we get this issue resolved.
Chris On Tue, Jun 26, 2012 at 2:30 AM, Liborio Cannici <[email protected]> wrote: > from terminal/console try a > > lsof -i :23053 | cut -d' ' -f1 | sort | uniq -c > > you should see how many connection are on port 23053 per each program. > > This should help finding the culprit... > > yours > libo > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/growldiscuss/-/EvFbYD1XyeUJ. > > 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. > -- Chris Forsythe @The_Tick <http://twitter.com/The_Tick> -- 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.
