The Problem

Frequently, say, one out of 10 times, when I try and log back into my Mac from the screensaver, or when I wake it from sleeping, I will get a spinning beachball and be unable to type my password. Other times I will be able to log in, but I am prompted to enter my password multiple times for various applications, and invariably one of them (usually gconsync) will get stuck after I enter my password with a spinning beach ball. I can still use most applications, but application that needs keychain authorization locks up.

I happen to be using a very handy tool called SSHKeychain, which turned out to be the culprit.

If you are using SSHKeychain, this post will walk you through fixing the unstable-wake-from-screensaver, and also solves the problem of having to type your keychain password 3-5 times when I returned to my computer.

I struggled with this for a long time, but it turn out its quite simple to get Eltima SyncMate to talk to your T-Mobile Wing. This might be applicable to other Windows Mobile devices as well… I initially had trouble getting the program to ‘see’ my phone.It turned out the problem was with a bad setting on the phone itself. To correct it, go into Settings, then on the Connection tab click USB to PC. Make sure the box labeled Enable advanced network functionality is checked.One that is done, SyncMate should be able to ‘see’ your phone.Unfortunately, I spotted some other problems with SyncMate: 

• Groups within groups are not synced to the phone.
• Only one iCal calendar is handled
• Todo entries are not synced to the phone. 

When I upgraded from a PowerBook to a new MacBook Pro, I used Windows File Sharing (also known as Samba or SMB sharing) to transfer all of my files from one computer to the other via a network, and it looks like that corrupted my Aperture Library.

It look me a few days to realize the problem, but here are a few symptoms I noticed:

1. Images that were in the library BEFORE the move were not visible in iLife applications (iPhoto, the screen saver, etc). The projects appeared in the listings, but the images themselves were not visible. For example, the screen saver would always say “The selected folder contains no pictures. Please choose a new folder that contains pictures or add images to the folder.”
2. Managed RAW images would not display correctly. I would click on them and the image would appear with a ‘loading’ message, and then eventually I would see a solid red or maroon background with the text “Unsupported Image Format”.

Knowing that the Aperture Libary is just a special directory (called a bundle in Mac-speak), I started poking around inside, comparing a good project (one that I had imported on my new MacBook) to a bad project (one that has been around BEFORE the upgrade).

It turns out that there were directories within the Aperture project directories whose names must have gotten corrupted when I copied the project over from my old computer.

So I wrote a small program to repair the damage. If you have a similar problem, feel free to use this script to help recover your library.

Make sure you close Aperture and BACK UP your Aperture Library before you start!

Ok, now that you’ve backed up your library, download the fixApProject.sh script and save it to your home directory.

Open up Terminal.app (Application->Utilities) and cd INTO your Aperture Library.

If your library is in the default location, do it like this:
cd ~/Pictures/Aperture\ Library.aplibrary/

Now, assuming you’ve put fixApProjech.sh in your home directory, run the following commands:

chmod +x ~/fixApProject.sh

find . -name "*.approject" -type d -exec ~/fixApProject.sh \{\} \;