Unsupported Image Format

In spite of the beginning of this post it is related to this thread.

I use Shirt-Pocket's Superduper to create a "sandbox" copy of my primary OS X for testing purposes. I apply updates to the "sandbox" and once I'm sure they are stable I merge them to my primary OS X. If I get a bad update, I just reboot from the primary. The "sandbox" system shares user and application subdirectories with my primary.

In my case the "invalid image format" with referenced files occurs only when booted from the "sandbox" but does not occur when booted from the primary OS X drive. Recent testing has confirmed this. While I do not think this is a Superduper problem there may be a clue here somewhere. I'm hoping that if we get enough information someone will be able to pin-point the cause.

For details on my "invalid image format" problem see my earlier post in this thread.

Here is the post I sent to Shirt-Pocket.

--Begin Shirt-Pocket post.
Sandbox causing Aperture 2 "invalid image format" issues.
A unknown but significant number of Aperture 2 users have been experiencing "invalid image format" issues. See this thread: Apple - Support - Discussions - Unsupported Image Format ... This problem only affects Aperture and not other image processing programs. I have tested these same images with Photoshop Sony IDC, SilverFast, Viewscan, Adobe Reader and Preview.

The cause is unknown. In my case it primarily occurs with referenced images from scanners or other image processing programs like tiff or psd. I have definitely linked it to using a sandbox. After extensive testing using my primary OS X drive, Sandbox with shared users and apps, Sandbox with shared users, and Sandbox as a full back up I've obtained the following results. Referenced images always fail when booted from Sandbox shared users or Sandbox shared users and apps. They always work when booted from the primary OS X and the full back up.

Please note that in each case the Sandbox systems and the full back up were created with the erase option from the primary OS X system and no updates or modifications were applied.

As a side note Aperture is an apple application but creating a Sandbox with shared users and apps creates and alias in the applications folder. Hence the test with only shared users.

Does anyone have any suggestions as to what may be happening?
--End Shirt-Pocket post.

I'm getting this too -- first time every. Restarting doesn't fix it, the project seems to have gone south. I suspect some system update has exposed an Aperture bug.

It's extremely nasty.

There's a new Aperture version out, but the download is huge, I won't be able to get it from the hotel I'm at.

Very bad bug.

Replying to my own post.

The "unsupported" message was a red herring. The real problem had to do with copying a library between machines, and not redoing permissions after the copy.

See http://tech.kateva.org/2009/08/major-new-old-aperture-bug-unsupported.html for the details.