nlm / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

GrowlNotify 2.1 registers, but can't notify with Mac OSX Mavericks #617

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Send any message with growlnotify -m

What is the expected output?
A successful notification to Growl

What do you see instead?
2013-10-23 18:37:32.848 growlnotify[55143:507] We failed to notify after 
succesfully registering

What version of the product are you using? On what operating system?
GrowlNotify 2.1
Growl 2.1.2
Mac OSX 10.9

Please provide any additional information below.
This issue was discussed on the mailing list starting in July, but the dev team 
was under NDA with Apple and couldn't discuss anything related to Mavericks 
until it was released. 

https://groups.google.com/forum/#!msg/growldiscuss/2Syu5vCEe-8/vUyCzpy1Z8kJ

Original issue reported on code.google.com by cr...@platfor.ms on 23 Oct 2013 at 11:42

GoogleCodeExporter commented 8 years ago
I'm experiencing the same issue, but noticed that it INTERMITTENTLY WORKS, if 
you retry repetitively for a few seconds (although sometimes after 20-30 repeat 
attempts it still fails).

MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'
2013-10-25 10:09:19.263 growlnotify[15156:507] We failed to notify after 
succesfully registering
MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'    <<<<<< WORKED
MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'
2013-10-25 10:09:19.710 growlnotify[15158:507] We failed to notify after 
succesfully registering
MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'    <<<<<< WORKED
MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'
2013-10-25 10:09:20.053 growlnotify[15160:507] We failed to notify after 
succesfully registering
MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'
2013-10-25 10:09:20.228 growlnotify[15161:507] We failed to notify after 
succesfully registering
MM-MBP2012:~ mark$ growlnotify --appIcon Xcode Build complete -m 'growlnotify 
has finished building'
2013-10-25 10:09:20.427 growlnotify[15162:507] We failed to notify after 
succesfully registering

Console logs during that period say:

25/10/13 10:09:13.000 am kernel[0]: IOPPF: Sent cpu-plimit-notification last 
value 3 (rounded time weighted average 3)
25/10/13 10:09:19.262 am Growl[14976]: (null) doesn't have enough information...
25/10/13 10:09:19.264 am growlnotify[15156]: We failed to notify after 
succesfully registering
25/10/13 10:09:19.709 am Growl[14976]: (null) doesn't have enough information...
25/10/13 10:09:19.711 am growlnotify[15158]: We failed to notify after 
succesfully registering
25/10/13 10:09:20.052 am Growl[14976]: (null) doesn't have enough information...
25/10/13 10:09:20.054 am growlnotify[15160]: We failed to notify after 
succesfully registering
25/10/13 10:09:20.227 am Growl[14976]: (null) doesn't have enough information...
25/10/13 10:09:20.229 am growlnotify[15161]: We failed to notify after 
succesfully registering
25/10/13 10:09:20.426 am Growl[14976]: (null) doesn't have enough information...
25/10/13 10:09:20.428 am growlnotify[15162]: We failed to notify after 
succesfully registering
25/10/13 10:09:25.000 am kernel[0]: IOPPF: Sent cpu-plimit-notification last 
value 3 (rounded time weighted average 3)

/Mark

Original comment by mcac...@gmail.com on 24 Oct 2013 at 9:12

GoogleCodeExporter commented 8 years ago
this issue should be addressed by 2.1.3 which should hopefully be available in 
the store tomorrow.

Original comment by rarich...@gmail.com on 25 Oct 2013 at 2:03

GoogleCodeExporter commented 8 years ago
Issue 615 has been merged into this issue.

Original comment by r...@growl.info on 28 Oct 2013 at 9:49

GoogleCodeExporter commented 8 years ago
I can confirm that with the Growl 2.1.3 update, this issue appears to be 
resolved. I can no longer cause the error to occur.

Original comment by cr...@platfor.ms on 30 Oct 2013 at 5:07

GoogleCodeExporter commented 8 years ago

Original comment by r...@growl.info on 30 Oct 2013 at 10:06