Aperture 3..1.3 and Lion - progress, or lack of it.

Ernie,

Looks like it would. I get the drop down asking me to give the new Library a name. I have not created one, as this thing seems such a mess already. What would be your suggestion, given that I can in theory create a new Library?

Tom

In ordinary mode (as opposed to safe Mode) I can open an app like Pages, but virtually any action causes it to lock up. The Force Quit menu will then say that the app isn't responding. If I choose to force that app to quit, it quits, but all other app on my Dock freeze up at that point and won't even open. Happens every time.

In Safe Mode, I can open and close apps. It is only in Safe Mode, which takes 5 mins plus to start up, that I got Aperture to open and I found the viewing problem described in this thread.

I am clear that Lion is at the root of the problem, as I had full and happy functionality on all fronts until last Saturday when I made the regrettable decision to install it. However, that being so, I cannot yet rule out a bug in the new release of Aperture, as I have never yet managed to get it to do anything.

Currently, the most worrying part of all of this is that even under Safe Mode, I cannot get my iMac to recognise a card reader of external HDD. This robs me of the option of moving all of the photos on my iMac to safer ground, except via something like Dropbox, which I am going to explore.

Yes, but consistent with what others are reporting about Lion, and in my mind there is no doubt it is Lion that is the root cause.

Some progress today. Spoke to Apple Support, to see what they knew. Guy I spoke to was very tactful, and I am sure could have been indiscreet had he wanted, but he talked me through some stuff that has resored basic functionality. The fact that he went straight for the options he chose makes me think Apple have spotted some principal bugs already.

Before downloading Lion I had given my machine a pretty thorough healthcheck. It was therfore a surprise to find a very large list of disk permissions that had become corrupted. I had not thought to check this. (Cmd-R on boot up and use the Utilities menu). Once fixed (and the only way I can see they became broken was by the Lion installation), I got back use of Finder, and all viewing options in Aperture now work.

That's been as far as I have been able to go since then, but I am cautiously optimistic.

Tom

Hi Jan,

I spoke to soon, of course. When I closed the call with Apple, everything worked fine. I was unable to recreate any of the problems I had had with Aperture, Finder, or anything else. However, when I turned on my iMac next day, they were all back again, just as before.

I have made two more calls to Apple support since. I have been talked through so many minor system tweaks that I have lost count - removing files from this folder and that, changing settings etc.

Right now, I have just ended a call with a very knowledgeable and helful support agent, and I appear to have a fully working machine. I have been advised to test everything except Aperture very thoroughly, and if it all works, to try opening Aperture and see what happens. The Support team are going to call me again tomorrow, and if there are still issues, they will refer me to the support agents who specialise in Aperture.

Stay tuned. My conclusion is that at the very least, there must be dozens of issues with which Lion is incompatible, and that we users are, of course, doing Apple's product testing for them.

Tom

My situation too. I have 10,000 photos from the recent World Masters track and field championships an eager world is waiting to see!

I have spent the last few hours giving my system a tough time before attempting to use Aperture. Already, I have USB HDDs that it will not recognise, and an ethernet network drive, both used for backups, that Finder will not "see", but which are there when I open the third party "Path Finder" app. Clearly a Finder fault.

I am also seeing Time Machine just endlessly report that it is "preparing for backup" to an external HDD - one which Finder does show, because it has a backup from last week on it - yet no backup happens. For the moment, I have switched off automatic backups and will raise this with Apple tomorrow.

All this before I get to opening Aperture. It's 10.30 pm here now. Probably be tomorrow morning before I delve into what Aperture now does.

Well, as far as I can tell, I have a fully working version of Aperture. It even seems prepared to import from external drives. Been using it to do some sorting and editing this morning, and it has worked normally.

However, my research with the apps on my iMac show the following don't open, and give error messages (see if you can spot the pattern here!):

Address Book

iCal

iChat

Numbers

Pages

Keynote

Photobooth

Preview (though double clicking a photo file will open it)

QuickTime Player

Activity Monitor

System Profiler

Yup - these are all Apple's own products. Third party apps on my machine all seem to work fine. What's the betting that Apple Support, from whjom I am supposed to be getting a call in half an hour from now, try to suggest that it is third party apps that are causing the problem.

Ernie,

OK, update. Hold on to your seat. I now have a basically operational iMac running Lion.

Problem was a bizarre one in the end, and it was only me uncovering the errors in my previous post that pointed Apple Support at the solution. All the disfunctional apps were Apple's own. The list included System Profiler, which gave me an error message when I opened it from the Utilities folder inside the Apps folder. The error message said I had a version for OS 10.6

The point is, there is no System Profiler app in Lion! It has been replaced with a utility called System Information, though confusingly this keeps the same icon. Upon devling into my folders and files, we found that Lion appeared to have installed a new, updated Applications folder, but had not put this on the Dock. The old one, containing pre-Lion software, was still on the dock.

Rebuilding the dock, deleting the former dock preferences, and relacing the Appls folder with the new one appears to have solved everything. Apple Support had no explanation for why or how this had happened, though.

I have been using Aperture through today, and it has worked just fine in all respects. Touch wood.