SD prevents log off
 

After succesfully completing a clone operation SD seems to no longer react to quit requests. I cannot not quit it from the Dock's context menu. Logging off takes forever unless I manually quit SD from within.

Does this happen when you have a scheduled copy, but the drive wasn't attached? If so, what happened is that you changed your settings when SD! was in a "no user prompt" mode.

Try pressing Cmd-s, then Cmd-q, and SD! should quit.

I usually attache the drive before even starting SD.
I don't use scheduling.

Hm. I can't think of any reason why SD! would prevent shutdown, then, unless you were backing up. Could you describe this situation in more detail?

Attach drive, start SD, start copying -> everything green
Select "log out" (not shut down) from Apple menu
Wait until bored
Right-click SD in Dock, select quit (not force)
Wait some more
Give SD focus and press Cmd+Q -> within seconds I'm at loginwindow

Happens every time

OK. I've tried this on a number of different machines, and have had some others try it too, and I can't reproduce your problem.

Is anyone else seeing this?

This problem never went away for me, over various machines. Now it's still there on a fresh 10.8 install with not even the preferences copied. The only sadly unusual thing I'm doing is working as a regular user and entering administrator credentials when SD asks.

Try unlocking the lock in the main window?

Doesn't help.

I also have SD in ~/Applications instead of /Applications.

Move it to /Applications and see if it helps, then.

No. But it quits when I log into an administrator account. Can't you reproduce it by fast user switching to guest?

Re-lock and re-unlock it. And, no - it works fine for me, unlocked as an admin, from a non-admin account.

Now it quits, but only 40 to 60 seconds after I issued the command from the Dock.

(I never use the lock, it's always closed, and just enter credentials whenever I clone)

That's just weird. I'd suggest deleting your copy, re-downloading and reinstalling.

I already did that instead of moving it between Applications folders.

The problem followed me across several computers and more fresh OS installations. Guess I'll just quit it manually for another 6 years.