Comments on: Leopard 10.5.3 Fixes Some Navigation Services Crashes

By: Jay Kenna

Jay Kenna — Fri, 27 Jun 2008 08:47:13 +0000

CS3 was working OK for me for a while and then started crashing when placing images or exporting etc, re-installed, deleted preferences and checked for font problems, but it was still crashing, moved Version Cue and Bridge folders to the trash (Version Cue never installed the first time anyway and I think Bridge is more usefull on a PC than a Mac anyway) Anyway trashing those folders seems to have it working properly again…fingers crossed.

By: David Blatner

David Blatner — Thu, 26 Jun 2008 13:40:25 +0000

Wow, that’s bad. Make sure you rebuild your preferences (see Popular Posts on this site). Reinstalling the software doesn’t necessarily rebuild prefs. Other than that, I’m not sure what the solution could be.

By: Twin Dots

Twin Dots — Thu, 26 Jun 2008 08:02:39 +0000

Thanks David,
I tried to install-reinstall: no Joy!

By: David Blatner

David Blatner — Wed, 25 Jun 2008 13:24:42 +0000

Twin Dots: That sounds pretty bad; perhaps something in the InDesign app got moved or destroyed somehow. (Remember that InDesign relies on hundreds, if not thousands, of tiny files in various locations on your drive.) You may need to run the installer again (or uninstall and reinstall).

By: Twin Dots

Twin Dots — Wed, 25 Jun 2008 08:44:26 +0000

I have been reading through the comments hoping to find somebody with similar InDesign symptoms but you guys seem to be able to start InDesign ok.
Unfortunately, after installing the latest version of Leopard 10.5.3, I am unable to fire up InDesign in any way.
Every time I try to open it, I get the following error:

Adobe InDesign is shutting down. A serious error was detected. Please restart InDesign to recover work in any unsaved InDesign Documents.

I’d highly appreciate any help with this issue.

By: George Coghill

George Coghill — Mon, 23 Jun 2008 03:01:00 +0000

Adobe posted a few fixes for the “Place file” crash bug: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402930

Solution 2 worked for me – Launch InD, open a new document, invoke the “Place” command, cancel, then open your file and work as normal. Weird, but it worked.

By: Daniel Cilia

Daniel Cilia — Tue, 17 Jun 2008 08:49:46 +0000

I have a G5 which stills gives me this problem even after the 10.5.3 update. I never had the problem on my MacBook Pro. If I try to access the finder from InDesign (like ask to place a photo) the program crashes. One simple way around this is that IMMEDIATELY as you open InDesign CS3 open a file from InDeign’s Open Menu (or command -o) and access the hard disk of your Mac. Afterwards the problem does not arise again, until you quit ID of course.

By: David Blatner

David Blatner — Thu, 05 Jun 2008 14:31:04 +0000

Doug, I'm sorry to hear about all your problems. Thanks for pointing out the "Don't save to a server" issue, too. Yes, that certainly bites a lot of people. I have argued for years that people should not open/save files from a server. Working locally is just waaaay safer.

By: Doug

Doug — Thu, 05 Jun 2008 11:24:03 +0000

I have had lots of issues since upgrading to 10.5 with CS3. I would go back to 10.4 but I upgraded from 10.3! I consistently crash when I try to place a photo into a current image in the document. My workaround is to place it on the art board and then paste into the image I want to replace. I’ve noticed other minor irritations like menus disappearing (tab cycle through and they are back), changed workspace (reset it to the one I want). I sure hope all this gets resolved soon, I would like to design not trouble shoot.

Also, no one has mentioned the 10.5.3 update and the save to server file corruption. I heard about it from the MacGeekGab #154. Excerpt regarding 10.5.3: “Adobe does not support opening from or saving a file to a server, because of potential file corruption,” according to Adobe document #333037.

By: David Blatner

David Blatner — Tue, 03 Jun 2008 14:58:23 +0000

I just heard that at ADIM (Russell Brown's wonderful creative event) they had a room with something like 150 Macs running Leopard and they used CS3 for three days and had zero crashes due to Nav Svcs. Virtually all the people at the show used IDcs3 at their home offices without trouble either. But three attendees said they crashed multiple times each day when they're at work. That helps confirm my intuition (that it's a minority of users), and makes the mystery of why does it happen to some and not others all the more plaguing. I really hope Apple can fix this problem, or Adobe can find a workaround, or some resolution can happen, so that people feel comfortable working in Leopard (which is so great in other ways).