|
#1
|
||||
|
||||
OK. Let me know what happens.
__________________
--Dave Nanian |
#2
|
|||
|
|||
I deleted my scheduled backups, quit SD, relaunched SD, re-entered scheduled backups, and now the backups are occurring and the Copy Job dialog box no longer appears. Most mysterious.
Could all of the problems with SD and Mavericks and Copy Job be related to the change in accessibility preferences in Mavericks? That is, the need to give control of the computer via Accessibility on Privacy Panel of Security and Privacy Preferences in System Preferences? |
#3
|
||||
|
||||
It shouldn't. Copy Job - as I explain in the blog post - asks whether SuperDuper! (and Growl) are running by using a pretty standard Applescript call - "exists process 'SuperDuper!'".
Doing that now flags the process as trying to "control the computer with the Accessibility API" which, of course, is entirely wrong. We're simply trying to determine if those applications are running (eg no sense sending a Growl notification if Growl's not running). If you don't "OK" Copy Job in the Accessibility part of the security and privacy preference pane (it appears as "applet" in the list, due to a Mavericks bug, even though it appears as "Copy Job" in the panel), you'll get errors.
__________________
--Dave Nanian |
#4
|
|||
|
|||
Not knowing what it was, I did not have "applet" checked on the Accessibility portion of Privacy Panel, which may be why I was getting inconsistent results with scheduled backups. I will let you know what happens now that I have it checked.
|
#5
|
|||
|
|||
With the "applet" checked, two CopyJob failure dialogs promptly appeared when SuperDuper! launched at the scheduled time. However, when I clicked the OK button, SD! promptly quit. So I did a manually copy.
|
#6
|
||||
|
||||
What exact failure? It sounds like you may need to wait for 2.7.2...
__________________
--Dave Nanian |
#7
|
|||
|
|||
The failure was that after clicking OK on the CopyJob error dialog, that window disappeared and SD! quit without having done anything. I will wait for 2.7.2.
|
Currently Active Users Viewing This Thread: 5 (0 members and 5 guests) | |
|
|