Bug #1809
closedGrowl issue
0%
Description
I reported Bug #1769 that Growl stopped working and it got rejected.
So I tried some other stuff and updated the bug report but get no replay.
So here are my new findings:
I reinstalled the system (2.0 RC1) and Growl worked, I updated to 2.0 RC3 and it still worked, than I restored my config and after that it did not work anymore.
So I reinstalled again started configuring (from nothing) but after changing the advanced settings it stopped again.
I did not restore any data and no other settings where changed jet.
So something is not going right...
I hope you can take a better look at this.
If you need the info about what I changed let me know.
Thanks.
Updated by Warren Baker almost 14 years ago
How are you testing Growl to say it is not working?
Growl creates a temp file (/var/db/growlnotices_lastmsg.txt) of the last message sent to avoid spamming a host. So if you click change something on the advanced setting page it wont re-send a test message.
You can test this by deleting this file and then clicking save.
Updated by Richard van Herp almost 14 years ago
Well oke, thats now...
Never noticed that in RC1, But yes, it's working now :)
Thanks.