42485 Views Previous 1 … 5 6 7 8 9 … Next 215 Replies Latest reply: Jul 3, 2010 2:50 PM by salspix Go to original post
One of the more frustrating aspects of this is that there is no indication I can find that Adobe and/or Apple is doing anything to fix this. It would be helpful for either company to even simply acknowledge the issue and say they are working on a fix but I don't see even that.
I tried the Rosetta Stone fix and running AppleJack but no luck. Guess I will wait a few days more for an official fix and then downgrade back to 10.6.2
Sharon Goodman wrote:
Without attaching the very long crash reports,
The one that are actually useful?
IN CASE SOMEONE AT APPLE IS READING THIS
They aren't. This is a user-to-user tech support forum.
all crash reports had one thing in common:
Code Type: X86 (Native);
KERNPROTECTIONFAILURE AT 0x0000000000000005
I think you will find that same sequence in any crash report. Look at your crash report. If it is identical (more or less) to a crash report someone else has posted, then you do indeed have the same problem. If your crash report has significant differences (different functions in the stack of the thread that crashed), then you have a different problem and you should create your own question and post the full crash report there.
Steve Crow wrote:
One of the more frustrating aspects of this is that there is no indication I can find that Adobe and/or Apple is doing anything to fix this.
Apple is typically pretty tight-lipped about these things. You'll never know what is going on inside there.
It would be helpful for either company to even simply acknowledge the issue and say they are working on a fix but I don't see even that.
Adobe is doing something - actively pointing the finger at Apple. If you read the postings by Adobe employee in the Adobe support forums, you would be left with the impression that MacOS X is horribly unstable and applications have had serious crashing problems for 3 years.
Unfortunately for Adobe, no one other than their customers seem to experience this level of crashing and instability.
Guess I will wait a few days more for an official fix and then downgrade back to 10.6.2
There will be no official fix. Adobe has really, really funky licensing schemes that no one else has. If all other suggestions fail, backup, re-parition your hard drive, re-install MacOS X 10.6.3, then reinstall your Adobe software. It should work fine until the next software update.
I had a different, but - perhaps - related, problem. I'm using CS4 and, after installing 10.6.3, I could not open pdf files. Everything else in CS4 worked properly.
My default reader was Adobe Acrobat, which would crash immediately when I tried to open it, or a pdf file. I changed by default app to Adobe Reader. Both the app and files opened normally. I changed my default app back to Adobe Acrobat and, voila, both the app and files opened OK. I don't know what caused the problem, and I'm satisfied that I got it resolved.
I am having the same issue, but it seems to extend farther than Photoshop or any Adobe Creative Suite apps for that matter. I use many Audio/Video/Graphics programs and seem to have MAJOR issues with all of them after the 10.6.3 update. Pro Tools is toast as well as CS3. FCE and LiveType asked me to re-serialize my copies. I tried all of the usual tricks to no avail. Not real pleased with this upgrade. Taking the system back to 10.6.2.
Brought my system back to 10.6.2 and all things are back to normal. I received a phone call from Adobe to follow up my tech support call. The technician said the CS3 / 10.6.3 incompatibility is a known issue and they are working on a patch.
I personally wonder if the issue has something to do with having downloaded trial versions of CS4 apps? In all of the work I did to try to get CS3 to launch correctly in 10.6.3, there seemed to be some unpredictable behavior with unexpected, remaining CS4 components from a trial Fireworks CS4 I had installed a while ago. Anybody else have a similar experience?
I was thinking the same thing ... I once installed the trial of Dreamweaver CS4 but removed it as I didn't find it worth the money to upgrade. Now that Dreamweaver CS3 is not working anymore I tried to re-install the trial of Dreamweaver CS4. I know that probably won't work as the 30 days have long passed, but I cannot even install it, it says that I already have it installed ... which is not the case anymore ... So I was thinking the same, maybe that caused the problem ...
We at Adobe are working hard to determine the root cause of this and find a solution to get the applications working again for users who are impacted by this. Unfortunately, we've not been able to reproduce this in various tests. We need to identify the common thread that connects systems that are affected by this.
If you are experiencing a crash, can you please gather a system profile report from your machine and email it to me at firstname.lastname@example.org. To gather the report, do the following:
1) Choose About this Mac from the Apple Menu,
2) Click More Information button
3) Choose File > Save As and choose the System Profiler format
Your help would be greatly appreciated!
Adobe Systems, Technical Response Team
Message was edited by: M@Adobe
Message was edited by: M@Adobe
I did most of those things too and I'm now running.
1. Uninstalled CS3 (I'd already deactivated it because this is a brand new 10.6.3 install from scratch).
2. Tried an install and test with no joy, uninstalled again
3. Ran the cleaner script, level 2.
4. Installed CS3
5. Discovered it wouldn't come up - with the same single bounce error.
6. Turned off Rosetta
7. CS3 came up, activated, updated and runs fine (of course now I can't use Focus Magic).