The application Finder.app can't be opened.

I know, it's not the most elegant way, but what choice do you have other than force restart? I made a simple Applescript that I put in the dock to do a software force restart instead of holding down the power button:

*do shell script "sudo reboot -q" password "xxx" with administrator privileges*

Replace xxx with your admin password and save the script as an application. After that drag it in the dock and you only have to start it from the dock to reboot within a second.

In most cases.... just *_UNPLIUG THE USB CABLE to the OFFENDING / EXTERNAL DRIVE_*... and the finder will "spring back to life" as I reported earlier in this thread.... but who has time (Seriously) to read every...single...page...in this thread ?
.
.
BUT PLEASE send a report to apple... complaining about the problem... this is _the minimum_ that should be done by everyone !

Message was edited by: Alfred Abraham

That's a pretty clever idea, for any system having a repeating issue that causes partial lock-ups...

One concern, however, is having such an easily accessible script that contains your admin password. Not very secure, is it? I'm no AppleScript expert, but is there a way to protect the password when embedding it in the script like that?

Thanks, and sorry for the thread sidejack!

I'm back with my new Mac Pro (see pages 15&16) 8-core 2xXenon Quad 2,26GH with 640 Go HD, 6Mo SDRAM and ATI Radeon HD 4870. I carefully put my applications. I put my 2 Samsung HD103HJ (1To): each has 3 partitions. I checked everything with Techtool Pro.
And yesterday I had again my "improperly ejected" disck. Off course I did nothing special. But this time I closed and save everything. I didn't opened my Finder. I ran Onyx and ask it to clean, maintain and rebuilt almost everything and this time i could close softly.
This morning I had a new "improperly ejected" this time with a Iomega firewire HD.
I did the same and I could close.
I will try for a week to work only with the master HD and plug my others HD only when i need to back up or find a file.
If its's not working may be I will send it back to Apple and get refund.
This is not a good solution for my work but I'm loosing my confidence in Apple since this Snow Leopard.

So this is a second machine? If so, and you're having the same issues, you've got to get in touch with the support people at Apple, and explain that there's something in your software setup that is causing this reproduceable error!

And I repeat what others have said: EVERYONE experiencing any variation of this issue should contact Apple directly somehow (either through their feedback page <http://apple.com/feedback/macosx.html>, or by calling support at 800.275.2273), and make sure they hear you! DON'T count on them reading this thread, that's for sure...

Remember, even though there are possibly hundreds of people experiencing this issue, it is still likely less than 1% of all users of Snow Leopard. This is not to say that it's not a serious bug, or that it's not Apple's "fault", but just to point out that it's not as widespread as it may seem by reading this thread. I'm not sure what "The DiD" means by "pages 15&16", as I see 5 pages, with a total of 245 posts (including this one).

Hang in there folks, this too shall pass!

John,

I think you are vastly underestimating the problem. I did a quick and dirty poll of a group of people on a professional camera forum I belong to, where 60%+ of the members are not surprisingly, Mac users. Virtually every one who has upgraded to Slow Leopard, has had external drive problems at one time or other. About 30%, who upgraded to SL, have reinstalled Leopard. The other comment I got was that they have seen far too much of the SBOD (spinning beachball of death) since upgrading to SL.

Wilson

All due respect Wilson, it's irrelevant whether I'm under-estimating or you're over-estimating. As I said, I'm not downplaying the issue, but it's only going to be dealt with when Apple hears from enough people (DIRECTLY) to warrant action.

If the problem is as serious as I bet it is, then Apple's already working on it, as they've been able to reproduce it in their labs. That said, I'm a small-time Mac consultant, with 100-plus clients, and I would bet about a quarter of those have moved to Snow Leopard. I'm the only one I know who has experienced the issue, and it was one time, never to return...

Again, don't get me wrong! I'm not an Apple apologist!! I, too, believe Snow Leopard to be far from the "performance and stability" upgrade we were told it was. I've had far too many weird little issues, though too many spinning beach balls is not one of them. Apple has some work to do to bring the situation around, and I'm simply writing to urge everyone to make concerted efforts to spread the word directly to Apple as much as possible.

I believe the vast majority of issues with SL have to do with legacy software. Since it's attempting to initiate the move to 64-bit, and begin the process of eliminating all PPC code altogether, the more old software you run that requires Rosetta, the more issues you're going to have. This is one of those painful transition periods that will eventually lead to much better times. It's just painful as heck in the interim!

Thanks for posting, and hopefully we'll start seeing some improvement from Apple very soon. I sure hope so!

Wilson
It's interesting because at the beginning i was asking to myself if my problem was connected with the hard drive Samsung HD103HJ.

John.
Off course I will call Apple and told everything about it.
The last time I did, they changed my Mac pro and the guy said it was certainly an hardware problem. Now i know that it is not. I not sure he will give me an answer!
And pages 15 & 16 are on this topic and are the beginnings of my posts.

That is right - it might be a security risk. Unfortunately Applescript doesn't provide a way to hide that password other than to save it as an executable-only application. At least there is no solution that keeps the script simple and fast. I could have added some "display dialogue" to let the script ask for the password. But then it's easier to press & hold the power button.

The bottom line is:

1) The Core Services daemon, coreservicesd is crashing.

2) Without the core services daemon, the system cannot function. Any attempt to launch a new program without a running core services daemon will cause Launch Services to fail with the return code kLSUnknownErr, meaning "An unknown error has occurred." kLSUnknownErr has a numeric value of -10810.

(For the morbidly curious, see:

http://developer.apple.com/mac/library/documentation/Carbon/Reference/LaunchServ icesReference/Reference/reference.html )

The problem is that if coreservicesd crashes, it's supposed to restart automatically, which it does, but when it restarts its versioning information appears to be set incorrectly, and so launch services will no longer talk to it.

Looking at the various crash logs posted here, the frustrating thing (from both Apple's and users' points of view) is that it seems to be crashing for various unrelated causes.

What Apple should be able to fix is the issue that is causing coreservicesd to restart without properly setting its versioning information.

Until Apple releases a fix, my best advice is that when those of you experiencing the issue have it occur, be sure to open a case with AppleCare if you haven't already, as that is how Apple engineering gets more data as to the causes of the issue.

I echo what William says above. Make sure your case gets escalated to a level 2 tech. He should email you a copy of Capture Data, which you should run as soon as possible after a problem/crash/lock up, having noted the time of the crash so you can attach that to the capture file. You then send the capture file or files back to the email of the Apple guy, who sent you the CD program, for analysis.

Wilson

*I send FEEDBACK for the 2ND TIME.* just now.

Does Apple respond to the feedback, or acknowledge anything ?

Alf

Alfred Abraham wrote:
*I send FEEDBACK for the 2ND TIME.* just now.

Does Apple respond to the feedback, or acknowledge anything ?

Did you read the feedback page?

It explicitly states:

Use the form below to send us your comments. We read all feedback carefully, but please note that we cannot respond to the comments you submit.

http://www.apple.com/feedback/macosx.html

The way to get a response from Apple is to open a case with AppleCare.

thanks..... I will open an Applecare case.

(was probably too upset to read the "fine print" !)

I have the same problem on my MBP, finder non responsive, error 10810... I connect to SMB network shares and use MS RDP client both frequently, but didn't ever have this issue prior to Snow Leopard as far as I can remember.

I have also noticed other strange issues on occasion, such as occasional unexplained sluggishness and network shares not showing files that were added PRIOR to opening them on the Mac - which was very weird.

I love my Iphone and other Apple stuff, got my first Apple II in 1980 - but overall this is quite frustrating, especially in light of the mac "Switching" commercials I keep seeing. I am an IT director for a mostly windows based company as well where I have recently deployed some Imacs - they're great machines, but between these issues at home and other frustrations with exchange support on the imacs I've added for the creative side of our marketing dept I have to say that may experience lately has been opposite of what those commercials imply.