Shirt Pocket Discussions

Shirt Pocket Discussions (http://www.shirt-pocket.com/forums/index.php)
-   General (http://www.shirt-pocket.com/forums/forumdisplay.php?f=6)
-   -   Copy Job.app - "Can't continue 'event notifygr'" (http://www.shirt-pocket.com/forums/showthread.php?t=6808)

vicchi 08-28-2013 08:15 AM

Copy Job.app - "Can't continue 'event notifygr'"
 
Firstly some background, I'm running a registered copy of Super Duper! 2.7.1 (v91), which update checking tells me is the latest version, on a MacBook Pro running Mountain Lion (10.8.4) and backing up a 320 GB LaCie and to a 500 GB LaCie external FireWire drive. I have two scheduled copies configured, one per drive, running every week day using Smart Update to sparse bundle images on the drives.

I'm a significant fan of Super Duper! ... it's saved my data over two catastrophic failures of my Macintosh HD volume and thanks to being overly attentive to backing up, I've been back up and running with pretty much no data loss after restoring from the latest backup.

But since upgrading to Mountain Lion, I've noticed that at the end of a successful backup, I get a window appearing as you can see in the screen grab below. I can select the window and move it around, but I can't make it active, nor click on the OK button.

http://i.imgur.com/9oypj4v.png

From looking at Activity Monitor, I can see that there's an instance of Super Duper's Copy Job.app running (and producing this window), with a parent of launchd and it's slowly clocking up CPU time and taking up just under 10 MB of real memory.

I've gone through the usual remedial steps of verifying both my Macintosh HD volume and the external drive volumes, of verifying/repairing permissions as well as rebuilding LaunchServices, but this still recurs.

I'm not running Growl but am running Hiss (http://collect3.com.au/hiss/) to forward Growl notifications to Mountain Lion's Notification Center, which may or may not be related to this.

At the end of the day this is a minor niggle; I'm able to force quit the instance of Copy Job.app and thus free up the allocated system resources.

Has anyone else come across this or know what's happening here and, hopefully, how to stop it happening?

-Gary

dnanian 08-28-2013 08:26 AM

This is because Hiss is not properly emulating Growl. Use Growl instead, which can also send Growl notifications to the Notification Center.

vicchi 08-28-2013 08:38 AM

Quick Reply!
 
Thanks; I'll give that a try and see how it goes.

-Gary

vicchi 09-02-2013 04:40 AM

Looks like this is all down to my use of Hiss. Stopping Hiss and re-enabling Growl (v1.2.2) resolves this. Which is a shame as Hiss was working rather well; although to look at the support forums for Hiss, there's very little response from the developers and most responses are from almost a year ago.

Haven't upgraded to (and paid for) Growl v2 yet, so no Notification Centre integration on my machine right now. But I can live with that.

dnanian 09-02-2013 09:36 AM

Unfortunately, if they're going to replace Growl, they need to properly implement its various interfaces...


All times are GMT -4. The time now is 05:02 PM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2017, vBulletin Solutions, Inc.