Desktop becomes unclickable after scheduled backup
 

For about the past month SuperDuper has been causing my Desktop to become unresponsive — although the rest of the Finder continues to work just fine. This only happens after a scheduled backup which is performed every day at 5.00am.

My MacBook is set to wake a few minutes before the backup and afterwards SuperDuper sleeps my Mac. When I go to use my computer in the morning the Desktop accepts no clicks on files/folders until I relaunch the Finder.

Any ideas?

Jon.

Sounds like, perhaps, the backup drive itself isn't always responding right. Any errors in the system.log?

I’m not sure. Here’s the system.log:

May 7 04:58:01 jon-carrs-macbook kernel[0]: System Wake
May 7 04:58:01 jon-carrs-macbook kernel[0]: Previous Sleep Cause: 5
May 7 04:58:03 jon-carrs-macbook mDNSResponder[24]: ERROR: mDNSPlatformTCPConnect - connect failed: socket 17: Error 65 No route to host
May 7 04:58:03 jon-carrs-macbook mDNSResponder[24]: ERROR: mDNSPlatformTCPConnect - connect failed: socket 17: Error 65 No route to host
May 7 04:58:05 jon-carrs-macbook kernel[0]: AirPort: Link Up on en1
May 7 04:58:09 jon-carrs-macbook kernel[0]: AppleYukon2: 00000000,00000000 sk98osx_dnet - recovering from missed interrupt
May 7 05:00:00 jon-carrs-macbook com.apple.launchd[1] (0x10cfd0.cron[924]): Could not setup Mach task special port 9: (os/kern) no access
May 7 05:00:03 jon-carrs-macbook SuperDuper![934]: .scriptSuite warning for attribute 'boundsAsQDRect' of class 'NSWindow' in suite 'NSCoreSuite': 'NSData<QDRect>' is not a valid type name.
May 7 05:00:03 jon-carrs-macbook SuperDuper![934]: .scriptSuite warning for type 'NSTextStorage' attribute 'name' of class 'NSApplication' in suite 'NSCoreSuite': AppleScript name references may not work for this property because its type is not NSString-derived.
May 7 05:00:03 jon-carrs-macbook SuperDuper![934]: .scriptSuite warning for type 'NSTextStorage' attribute 'lastComponentOfFileName' of class 'NSDocument' in suite 'NSCoreSuite': AppleScript name references may not work for this property because its type is not NSString-derived.
May 7 05:00:03 jon-carrs-macbook SuperDuper![934]: .scriptSuite warning for attribute 'boundsAsQDRect' of class 'NSWindow' in suite 'NSCoreSuite': 'NSData<QDRect>' is not a valid type name.
May 7 05:00:03 jon-carrs-macbook SuperDuper![934]: .scriptSuite warning for type 'NSTextStorage' attribute 'title' of class 'NSWindow' in suite 'NSCoreSuite': AppleScript name references may not work for this property because its type is not NSString-derived.
May 7 05:00:03 jon-carrs-macbook SuperDuper![934]: .scriptSuite warning for superclass of class 'NSAttachmentTextStorage' in suite 'NSTextSuite': 'NSString' is not a valid class name.
May 7 05:00:21 jon-carrs-macbook KernelEventAgent[26]: tid 00000000 received unknown event (256)
May 7 05:00:21: --- last message repeated 1 time ---
May 7 05:00:21 jon-carrs-macbook fsaclctl[962]: HFSIOC_SETACLSTATE 1 on /Volumes/Macintosh HD clone returns 0 errno = 2
May 7 05:11:13 jon-carrs-macbook com.apple.launchd[1] (0x10c650.nohup[1111]): Could not setup Mach task special port 9: (os/kern) no access
May 7 05:11:31 jon-carrs-macbook kernel[0]: System Sleep
May 7 10:00:59 jon-carrs-macbook kernel[0]: System Wake
May 7 10:00:59 jon-carrs-macbook kernel[0]: Previous Sleep Cause: 5
May 7 10:01:02 jon-carrs-macbook ntpd[14]: sendto(17.72.133.42) (fd=25): Can't assign requested address
May 7 10:01:03 jon-carrs-macbook mDNSResponder[24]: ERROR: mDNSPlatformTCPConnect - connect failed: socket 17: Error 65 No route to host
May 7 10:01:05: --- last message repeated 3 times ---
May 7 10:01:05 jon-carrs-macbook kernel[0]: AirPort: Link Up on en1
May 7 10:01:07 jon-carrs-macbook kernel[0]: AppleYukon2: 00000000,00000000 sk98osx_dnet - recovering from missed interrupt

Don't see anything particularly interesting, although do you have any network drives mounted?

Nope. None.

I'm really not sure what else to suggest, Jon. We're not doing anything other than copying files and, perhaps, asking the system to sleep (if you requested that). We have no interaction with the desktop except as files in a folder...

Okay, well thanks anyway. I guess I’ll just have to live with it for the time being and see if any other application is the source of the problem.

Cheers,
Jon.