Growl stops growling

[Dan Lester]

I have Growl set up to pop a click-to-acknowledge note on my screen reporting that a SuperDuper backup has happened. Inevitably, that reporting simply stops.Maybe after days. Maybe after weeks. SuperDuper keeps doing scheduled backups, but Growl stops reporting them. I stop and restart Growl, and the non-reporting continues.

I think I've killed off the SuperDuper scheduling, and reestablished it, and the Growl reporting returns. So there is some evidence that this is a SuperDuper issue. Is this a known issue? What can I do to preserve this functionality?

[dnanian]

I use Growl here and have never seen this, Dan. I can't see how the backups would be happening but Growl wouldn't be notified: the schedule fires off the event to have Growl do its thing...so if it's running the schedule it'd certainly run the event...

[Dan Lester]

Hmm. OK. I see I am using an archaic version of Growl. I will update and see if that fixes it.

[dnanian]

Let me know!

[Dan Lester]

OK, the problem is resolved. Took a month to figure it out. I updated Growl, and the problem remained. Growl refused to notify me conspicuously with a "stay on screen" bubble when a copy was completed. It did on one machine, but not on another. I thought Growl was set up identically on both, but it turned out not to be.

In Growl Preferences, under Applications, you have to be careful to examine all the tasks the application can be doing. Under "Copy failed", "Stay on screen" was set to "Always". But oops, in "Scheduled copy succeeded", "Stay on screen" was set to "Application Decides" on that one machine. And whaddaya know, SuperDuper! decided to tell Growl not to have it's "scheduled copy succeeded" report bubble stay on screen!

So once I set "Scheduled copy succeeded" "Stay on Screen" to "Always", everything worked. I got up in the morning to see a bubble reporting that SuperDuper! had succeeded in making the copy.

So, Dave, why does SuperDuper! decide to tell Growl not to have the report bubble stay on the screen?

[dnanian]

We don't: that's a setting left up to the user, as far as I know. (We register the application and event, and the notification handling is set by the user.)