I'm also seeing this on 10.8.4; restarting growl fixes it for a while here too... Then it just stops working again (using Growl 2.1.1, Notify 2.1)
~ Doug. On Thursday, September 5, 2013 2:12:39 AM UTC+8, justdave wrote: > > I'm seeing this on 10.8.4, using Growl 2.1.1. When Growl gets in this > state I also can't open the preferences to look for the version number (the > window opens, but the tabs are all blank and there's no content). > Restarting Growl fixes it. For a while. > > On Friday, July 12, 2013 9:01:08 AM UTC-4, Alex wrote: >> >> Hi. >> >> growlnotify is randomly failing to send notifications to Growl 2.0.1 >> >> Reproducing: >> >> Not always, but I'm getting errors at least for each second time. >> >> /usr/local/bin/growlnotify -m 'Text' -t 'Title' -d 'Test' >> >> Logs: >> >> stdout: >> 2013-07-12 16:52:52.410 growlnotify[2165:507] We failed to notify after >> successfully registering >> >> growl.log: >> 12/07/13 16:52:52,410 Growl[236]: (null) doesn't have enough >> information... >> >> Versions: >> >> growlnotify 2.0 >> growl 2.0.1 >> OSX 10.9b3 (13A510d) >> >> Thank you. >> > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/growldiscuss. For more options, visit https://groups.google.com/groups/opt_out.
