10.5.3 Photoshop CS 3 issues

Join the ADC. Help run these new releases through your series of tests. Apple can't possibly replicate every variable out there. Nobody can. Seeding programs exist so those of us who are interested in the new releases can test and offer feedback. It's open if you're serious about wanting to catch all bugs before updates are released. 😉

Don

I run a creative business. One overlooked bug has cost me several hundred pounds in lost revenue - not to mention the increased stress levels.

If I was to participate then I could only imagine the levels of monetary loss along with the stress levels would be exponential!

don montalvo wrote:
Apple didn't make a mistake. The seeding program depends on ADC members to thoroughly test a release before it goes out to the public. We missed this one, plain and simple. Rest assured, Apple is actively working to get a fix out.

Don

Unless by "we" you mean you represent Adobe or Apple I'll have to refer to Mitch Cohen's previous post in this thread where he put it very well:

Developer seeds aren't (primarily) for users to test Apple's code to please Apple. They're for developers to test their own code in Apple's revised OS, and resolve any issues.

It's $500 bucks to get a developer account to get seeds that Apple clearly state are not for production machines, so come on Don, no need for us to bear the weight of this gaffe. Sure it'd be nice if we'd have caught it but as I said in the Adobe forums before they got out the pitchforks "How hard is it to have an automated Photoshop script that runs a suite of actions and reports on the pass/fail of them?" Not hard for someone if that's their full time job at Adobe, I think the department would be called QA? 🙂

Anyway enough finger pointing, in the meantime I haven't had time or free machines to test this out but for the adventurous and time-strapped, if you've gone to 10.5.3 and don't want to do a complete re-install, getting these files from a 10.5.2 machine and replacing them on your afflicted machine might work:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwor k.framework
/System/Library/Filesystems/AppleShare/afpfs.kext

These files are updated in the 10.5.4 seed that is said to fix the PS save bug, so I am deducing they are the culprits. However you mileage may vary and I don't have the spare machines to test this on, so things could go awry but it is similar to the fix that was done back in 10.4.x days to fix another Adobe/Apple bug. We have 140 Macs where I'm at have kept the number of Leopard machines down to 5 (only because we couldn't run Tiger on them!) and of those we have kept them at 10.5.2, so I thankfully have not had to do this down and dirty triage.

It's $500 bucks to get a developer account to get seeds that Apple
clearly state are not for production machines, so come on Don, no
need for us to bear the weight of this gaffe.

Appleseed program FAQ:

https://appleseed.apple.com/cgi-bin/WebObjects/SeedPortal

I agree with Kevin Neals comments. '18,000 people viewing this topic' sounds like it may well be a MAJOR problem.

This isn't about a Mac that won't shut down this problem is costing people money. As a small design agency with no IT dept apart from myself this kind of debacle can be crippling. At the moment we have lost nearly £3000+ worth of work and time when the files were worked on in the morning and then didn't open in the afternoon!!! No chance of backups there, a crystall ball to see the future would have helped so maybe Apple will ship those as a Widget with 10.5.4.

PULL YOUR FINGER OUT APPLE and either admit the fault via this forum or else maybe MacUser, etc.

At least we know with "almost" certainty that it will be fixed before 11th July, as requirements for Mobile Me state it needs 10.5.4 and Mobile Me is launched on 11th July

Hello,
I work for an advertising agency and we are experiencing this issue as well. It seems to occur in all CS3 apps. I have tried many solutions to this problem, that didn't work for me.
Didn't work:
Creating new AFP/SMB shares.
Changed default mask to allow everyone permission to read/write.
Applied all known CS3 fixes about 5 known work arounds for various issues.
Reinstalling CS3/Mac OS X 10.5.3.
Interestingly, one of our 10.5.2 Macbook Pros has the same issue.

So I was thinking how we could share files to remote shares. I had the idea to try webdav/idisk. I successfully saved an ID file to my .mac/idisk account and worked on the file. Created text boxes with text, photos, moved elements around, and resaved. No problems. It saved successfully to the documents folder in my idisk even though it was a little slow. Is it possible that others can try this fix, or set up a webdav share and see if this works?

We are in the process of setting up the share with webdav. I also called Apple with this idea and they said it would be looked at, and they would let me know if its a viable workaround in 4 days.

Thanks.
Brian Povlsen

I and two of the other users in our design department have also had this issue, both with .tif and .psd files. We never had problems working from our file servers on our PowerMac G5s running OS X 10.4. But since purchasing Mac Pros running OS X 10.5, we've had all number of issues. And I don't fault the hardware -- by all accounts, it appears to be functioning just fine. But the numbers of operating system glitches in Leopard seem to be increasing.

I agree with the users who argue in support of working on file servers -- when you are working in a workgroup situation such as ours, where several people need to work on different parts of the same project, then the ability to work from a centralized server is imperative. And until now, we've never really had any problems in doing so.

It's a shame that OS X 10.5 is showing so many problems in general (see some of the other discussions on other issues -- these file sharing issues are not the only ones!) after OS X 10.4 was SO rock-steady.

Hopefully, Apple will work with the other software publishers to get these issues resolved, instead of all of those entities (Apple, Adobe and other publishers) just trying to pass the buck, leaving the users in a lurch.

We are getting similar problems here. Mine is the only machine so far updated to 10.5.3.

If i load an RGB tiff file directly from our linux server, convert to CMYK, and then save directly back to the server, it corrupts the file every time. This has never been an issue before.
As for Adobe not recommending working on files over a network, in all my time in the Reprographics business (18 years) i've never ever come across problems in doing this. And we've been doing this here for the last 10 years on various servers.

This is definately an OSX/Adobe problem which has arisen since the update to 10.5.3.

Just weighing in here with the hope that SOMETHING will be done by Apple - seems clear that the responsibility for solving this problem is shared 50/50 by Apple / Adobe.

Saving files across a network not supported by Photoshop?!! This is beyond a joke, literally millions of users must have been using this workflow as part of their daily routines for years!

I have posted bug reports to Apple and Adobe too, and suggest that everybody on this topic does the same - the more fuss made by users the better! Lets make this a numbers game.

fingers crossed

Just found a way to recover corrupt photoshop documents!!

It might not work perfectly but I have just salvaged a image I thought was lost.

All you do is in the open dialog window select "all Documents" and change the file type to "Photoshop Raw" now you have to remember the dimensions of the image ( or best guess ) and it should open, might take a few goes to get it right but you should get most of the image back.

Obviously this is far from perfect, but if you're facing re-doing hours of work give this a try, It has just saved me from reshooting a load of fridges stocked with food from last week

FYI you may not have to guess. The get info window in Leopard should actually have the pixel dimensions if the file was saved with CS3 (it may also have that info for previous versions, but I can't confirm with my current setup.)

Unfortunately, this does not work with layer files or this wouldn't be such a big deal.

You might have the dimensions in the spotlight comments but the corrupt images don't have the dimensions in the more info section of the get info window, at least not in my corrupt images

So when I updated to 10.5.3, my entire machine went down. I wish it was just corrupting server-based files on "save." It corrupted my catalog tree so badly that I'm ordering a new hard drive and burning the one I had 10.5.3 installed on.

I tried formatting to all zeros and reinstalling, and my drive was almost instantly giving me errors. This after months of flawless performance with 10.5.1/10.5.2 (according to disk utility, anyway).

I will say that I got errors like this (the save to server errors from photoshop) with a single point release of Tiger, and that the problem caused me a lot of grief. I can't remember which exact version had the error, but the next point release fixed it completely. It looks like they brought the bug back with 10.5.3...and they still haven't fixed the NavServices issues with InDesign...über-lame.

Same problems here. Only on one machine so far, but I suspect it will happen on a few others. Saving photoshop as PSD to an XServe file server. We've swapped out RAM, reinstalled CS3, run all of the utilities with the same crippling results.
Specs: Dual Core Xeon, 6GBs RAM, OS 10.5.3.
X-Serve OSX 10.1
I was shocked to see that this was a rampant issue. Apple/Adobe... please!