Project

General

Profile

Actions

Bug #1809

closed

Growl issue

Added by Richard van Herp almost 14 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Notifications
Target version:
-
Start date:
08/20/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
i386

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.

Actions #1

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.

Actions #2

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.

Actions #3

Updated by Chris Buechler almost 14 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF