SuperDuper 2.1.4 Beachballs When I Unlock the App

[DarylF2]

When I click the "lock/unlock" icon (to allow scheduled backups) to unlock the app, SuperDuper 2.1.4 beachballs on me. I need to force-quit it.

Is anyone else seeing this?

EDIT: I tried deleting the preferences files, re-registering, and trying to "unlock" the SuperDuper 2.1.4 again and still get the application freeze...

[dnanian]

Nothing we've heard of before, Daryl. Have you tried restarting your Mac?

[DarylF2]

Reverting to 2.1.3 results in the same issue (which was definitely NOT the case before)...

I'll restart now and report back.

Restarting appears to have fixed the problem. I've never seen this before; does the OS service that handles this authentication dialog sometimes get messed up? I wonder if simply logging out and logging back in would fix the problem as well...

Anyway, thanks for the quick (and very useful!) reply! :)

[t3rockhall]

FYI: I just downloaded the update after I got the announcement; when it finished and started to run, the app and Mac froze after 7 minutes. No beachball, but the mouse wouldn't work and the SD screen clock had stopped. I had to hard reboot. When I tried it again, it ran, albeit a little slower than before (maybe the hard reboot affected the backup drive).

Thought you'd like to know.

G5 iMac, 10.3.9

[dnanian]

I'm certain that this has nothing to do with the update: we can't cause your Mac to freeze. More likely that you were having a problem with your backup drive, FireWire, etc -- what else was attached?

[t3rockhall]

I'm certain that this has nothing to do with the update: we can't cause your Mac to freeze. More likely that you were having a problem with your backup drive, FireWire, etc -- what else was attached?

Just the Firewire drive, 2 USB printers and a USB wireless KB and Mouse.

[dnanian]

OK. Let's make sure everything gets fully powered off and then give the copy another shot.

[t3rockhall]

In my note above, I said it froze after 7 minutes. That should have read 7 SECONDS.

It ran after reboot.

I just ran it again, with my peripherals still on, and it ran fine.

I'm OK with that.

[dnanian]

OK: glad things are working properly now.

[Timmy]

I just installed SuperDuper! and my hamster died!

[dnanian]

Actually, that is our fault. We forgot to comment out the NSHamsterTerminate call before releasing 2.1.4: sorry about that!