You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

The application Finder.app can't be opened.

I upgraded to Snow Leopard yesterday, and I'm having a lot of troubles, Finde, Time Machine and Disk Utility being the most annoying of them. I don't really know which one of them is making the others unstable / crash but well that's starting to be very irritating, now when I try to start the Finder I get this :

*The application Finder.app can't be opened.*
-10810

Restarting the Computer ( Mac Book Pro Uni ) usually fix that, but it's the second time that it's crashing a 220 go files package copy. I ended up doing it with rsync, the copy is still going on ( it will take a long time ) but I'm left with a Zombie Computer where I can't open a finder, and every Application that use it to open some file is crashing itself.

Is there a way to manually relaunch it ( I don't want to reboot, my computer is stuck backing up a lot of files ) ? I tried Sudo Launch the Finder from /System/Library/CoreServices/Finder.app/Contents/MacOS with no luck, any help would be appreciated.

KS

Message was edited by: Kel Solaar

Mac OS X (10.6)

Posted on Aug 30, 2009 12:35 PM

Reply
696 replies

Nov 10, 2009 10:25 PM in response to Kel Solaar

I've just gone back to 10.6 in hope that it makes it all better. My iMac has been reduced to a beautiful piece of technology that only gets sworn at over the last few days, and after upgrading to 10.6.2, hoping that the problem would be solved, it only made matters worse.

External drive connected or not - the Finder would simply refuse to let me open/close/force quit any applications - and only keep the application menu for Tweetdeck as active (which wouldn't matter seeing as selecting an option would not lead to any action by the finder). If another user tried to log into the machine, it would simply take it's self to the User login window and then go on strike.

So back to 10.6 - so far, so good. I don't really want to go back further, but we'll see what happens. It's a frustration that I have never experienced - in my 20 years of being an Apple user, except when I've been made to use a Windows machine. Perhaps this is the tech-universe getting back at me for all those 90, XP, 2000, Vista and 7 jibes?

Nov 10, 2009 11:06 PM in response to Kel Solaar

This is quite the thread!

I've not had the time it would take to read the entire thing, but I'm curious about a couple things. First off, have any of you that have the problem quite a lot, tried creating a new user account, logging into that and seeing if the problem persists there? Also, have you tried your Apple Hardware Test on the install discs that came with your machine? I believe you hold down the D key while booting from the first install disc to invoke the hardware test...

I'd be very cursious to hear if either of those things yield any positive results. Also, keep posting your feedback at Apple's feedback page: http://www.apple.com/feedback/macosx.html; they need to keep hearing about this problem, and it's been shown that they really don't pay as much attention to the forums as they should.

Hang in there folks. I hope they get to the bottom of this soon!

Nov 11, 2009 8:04 AM in response to awado

Awado,

Please forgive me if my post was disrespectful in any way. I know it's a serious bug, but that doesn't mean one of the usual trouble-shooting techniques couldn't yield a fix, even if it's just for a subset of the folks experiencing the problem. Severity obviously varies by user. Myself, for example, only saw it one time, caused by trying to copy to/from an external drive connected to another computer on my local network. I was able to cleanly shut down however, and have not seen the issue again (thank god).

"It feels like Vista"

Ouch. Now that's harsh! Not that it doesn't feel that way to you, but obviously this issue isn't so large as to have caught the attention of many in the tech media (yet). I don't deny that it might reach that proportion either. For an OS that was supposed to be all about performance and stability, my experience with Snow Leopard is not very good, overall. It seems to have as many, if not more, niggling little issues as any other release, imho...

If only someone could actually make a universally stable, fast operating system!

Again, here's hoping Apple releases a fix for this issue, and soon!

Nov 11, 2009 11:01 AM in response to John I. Clark

+*OK, here's my story and I"m sticking to it!+.*

Am running an early 2009 Mac Pro with a Drobo Pro (8Gb) on Firewire 800 and a Sonnet E4P SATA card with two 5-drive Fusion 500s attached.

Everything was running fine on 10.6.0 and 10.6.1. Then I noticed that Sonnet had a newer driver for the SATA card - 2.2.0 and I was currently running 2.1.9. After I installed the update, things slowly seemed to go to pieces - many strange things, including a change in my sound preferences and various open and close problems. Worst of all, the dreaded Finder 10810 error. Later that day 10.6.2 came out and I installed it, but there was no change. If anything it was a little worse.

The next day I downgraded to the previous SATA driver, rebooted and one at a time reattached my external drives. For two days now all has been running fine.

I tend to not think the driver is at fault as there has been too many other configurations listed here that have the problem. I believe there are probably a number of things that will trigger the problem so I'll stick with what works until Apple has found a fix - and I hope it's soon!

Nov 13, 2009 9:08 PM in response to Kel Solaar

On my machine this appears to be a bug in coreservicesd.
The machine will start up normally and everything seems ok for a short while after boot. Watching /var/log/system.log (tail -f /var/log/system.log) will eventually show a massive spew of messages of the form:

com.apple.coreservicesd\[59\]: _FreeSegGetLength: invalid marker.
com.apple.coreservicesd\[59\]: _FreeSegGetNext: invalid marker.

finalized with:
com.apple.coreservicesd\[59\]: \[59\] detected buffer overflow

and then forever peppered with:

<some process>: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.

and:

<some process>: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.


Anyone at Apple want to comment on this bug?

Nov 13, 2009 9:48 PM in response to Kel Solaar

Crash log for when coreservicesd crashes:

Process: coreservicesd [61]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/Support/coreservicesd
Identifier: coreservicesd
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [1]

Date/Time: 2009-11-13 21:25:43.361 -0800
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
__abort() called

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff86cf2fe6 __kill + 10
1 libSystem.B.dylib 0x00007fff86d93dd3 __abort + 103
2 libSystem.B.dylib 0x00007fff86d88617 mach msgreceive + 0
3 libSystem.B.dylib 0x00007fff86ca67fd _memcpychk + 14
4 com.apple.LaunchServices 0x00007fff85bd75ff _LSBindingListDeactivate + 100
5 com.apple.LaunchServices 0x00007fff85bd1b90 _LSClaimRemove + 139
6 com.apple.LaunchServices 0x00007fff85bcf261 _LSBundleRemove + 443
7 com.apple.LaunchServices 0x00007fff85bcb3ae _LSServerItemInfoRegistration + 864
8 com.apple.LaunchServices 0x00007fff85bd4df7 LSServerRegisterItemInfo + 128
9 com.apple.LaunchServices 0x00007fff85bddaf1 LSPluginServerRegisterItemInfo + 86
10 com.apple.LaunchServices 0x00007fff85bd64c4 _XRegisterItemInfo + 373
11 com.apple.LaunchServices 0x00007fff85bd5bee LSPlugin_server + 106
12 ...ple.CoreServices.CarbonCore 0x00000001000b7113 scHandleMessage(mach msg_headert*, unsigned int ( )(machmsg_headert, mach msg_headert*), unsigned int*, unsigned char*) + 119
13 ...ple.CoreServices.CarbonCore 0x00000001000b49d8 SCServerSession::handleMessage(mach msg_headert*) + 370
14 ...ple.CoreServices.CarbonCore 0x00000001000b3bfc serverCallback(_CFMachPort*, void*, long, void*) + 342
15 com.apple.CoreFoundation 0x00007fff85108f7e __CFMachPortPerform + 366
16 com.apple.CoreFoundation 0x00007fff850e1551 __CFRunLoopRun + 5201
17 com.apple.CoreFoundation 0x00007fff850dfc2f CFRunLoopRunSpecific + 575
18 com.apple.CoreFoundation 0x00007fff850df9b6 CFRunLoopRun + 70
19 ...ple.CoreServices.CarbonCore 0x00000001000b3972 _CoreServicesServerMain + 522
20 coreservicesd 0x0000000100000eac 0x100000000 + 3756

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff86cbdbba kevent + 10
1 libSystem.B.dylib 0x00007fff86cbfa85 dispatch_mgrinvoke + 154
2 libSystem.B.dylib 0x00007fff86cbf75c dispatch_queueinvoke + 185
3 libSystem.B.dylib 0x00007fff86cbf286 dispatch_workerthread2 + 244
4 libSystem.B.dylib 0x00007fff86cbebb8 pthreadwqthread + 353
5 libSystem.B.dylib 0x00007fff86cbea55 start_wqthread + 13

Thread 2:
0 libSystem.B.dylib 0x00007fff86cdf9ee _semwaitsignal + 10
1 libSystem.B.dylib 0x00007fff86ce37f1 pthread_condwait + 1286
2 ...ple.CoreServices.CarbonCore 0x000000010006823f fmodWatchConsumer + 347
3 libSystem.B.dylib 0x00007fff86cddf8e pthreadstart + 331
4 libSystem.B.dylib 0x00007fff86cdde41 thread_start + 13

Thread 3:
0 libSystem.B.dylib 0x00007fff86caf426 read + 10
1 ...ple.CoreServices.CarbonCore 0x0000000100068f08 fmodWatchProducer + 140
2 libSystem.B.dylib 0x00007fff86cddf8e pthreadstart + 331
3 libSystem.B.dylib 0x00007fff86cdde41 thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff5fbfc5e0 rcx: 0x00007fff5fbfc5d8 rdx: 0x0000000000000000
rdi: 0x000000000000003d rsi: 0x0000000000000006 rbp: 0x00007fff5fbfc600 rsp: 0x00007fff5fbfc5d8
r8: 0x0000000000000001 r9: 0x000000010065b080 r10: 0x00007fff86cef026 r11: 0x0000000000000202
r12: 0x0000000102a756c4 r13: 0x0000000100830c00 r14: 0x0000000100830c00 r15: 0x00000000ffffdae5
rip: 0x00007fff86cf2fe6 rfl: 0x0000000000000202 cr2: 0x00007fff86d7e61a

Binary Images:
0x100000000 - 0x100000fff coreservicesd ??? (???) <D804E55B-4376-998C-AA25-2ADBFDD24414> /System/Library/CoreServices/coreservicesd
0x100004000 - 0x100336fef com.apple.CoreServices.CarbonCore 861.2 (861.2) <39F3B259-AC2A-792B-ECFE-4F3E72F2D1A5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <B633F790-4DDB-53CD-7ACF-2A3682BCEA9F> /usr/lib/dyld
0x7fff800ef000 - 0x7fff80130ff7 com.apple.SystemConfiguration 1.10.1 (1.10.1) <FFCA91A7-ADDB-E3D0-234A-47609BC37556> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff80928000 - 0x7fff80939fef libz.1.dylib ??? (???) <3A7A4C48-A4C8-A78A-8B87-C0DDF6601AC8> /usr/lib/libz.1.dylib
0x7fff81014000 - 0x7fff8105eff7 com.apple.Metadata 10.6.2 (507.4) <A28A5E0C-DCDC-A5CE-4EB7-39752E63956A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff812ba000 - 0x7fff8134afff com.apple.SearchKit 1.3.0 (1.3.0) <4175DC31-1506-228A-08FD-C704AC9DF642> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff816be000 - 0x7fff8171bfef com.apple.framework.IOKit 2.0 (???) <EBBEED67-D5BE-5F7F-96F4-9023BBA1B913> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff819b1000 - 0x7fff819dcff7 libxslt.1.dylib ??? (???) <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib
0x7fff819dd000 - 0x7fff81a18ff7 com.apple.AE 496.1 (496.1) <27D2D2E9-B309-7E65-8C3F-7FF01148F0DE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff81a19000 - 0x7fff81a1dff7 libmathCommon.A.dylib ??? (???) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
0x7fff82463000 - 0x7fff82471ff7 libkxld.dylib ??? (???) <568C35E7-B101-3F1E-0361-3E1E9F15C90B> /usr/lib/system/libkxld.dylib
0x7fff82548000 - 0x7fff827cdff7 com.apple.security 6.0 (36910) <67DF686D-B991-D0D6-20B6-9EA668018466> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff82dff000 - 0x7fff82e05ff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff83162000 - 0x7fff83162ff7 com.apple.CoreServices 44 (44) <210A4C56-BECB-E3E4-B6EE-7EC53E02265D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff831ef000 - 0x7fff83205fef libbsm.0.dylib ??? (???) <42D3023A-A1F7-4121-6417-FCC6B51B3E90> /usr/lib/libbsm.0.dylib
0x7fff83206000 - 0x7fff833c4fff libicucore.A.dylib ??? (???) <5BD16988-545F-6A8C-9A6F-FB18ACDCAEC2> /usr/lib/libicucore.A.dylib
0x7fff85095000 - 0x7fff85208ff7 com.apple.CoreFoundation 6.6.1 (550.13) <1E952BD9-37C6-16BE-B2F0-CD92A6283D37> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff85919000 - 0x7fff85939ff7 com.apple.DirectoryService.Framework 3.6 (621.1) <FC0C2E15-84E2-B4A8-18EE-3AE620111627> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x7fff85b6c000 - 0x7fff85c0cfff com.apple.LaunchServices 362 (362) <CCBFC037-7162-E392-B11F-90098891AE20> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x7fff85c11000 - 0x7fff85c20fff com.apple.NetFS 3.2.1 (3.2.1) <FF21DB1E-F425-1005-FB70-BC19CAF4006E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff85c21000 - 0x7fff85c9efef libstdc++.6.dylib ??? (???) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
0x7fff86360000 - 0x7fff86419fff libsqlite3.dylib ??? (???) <5A15E12A-AE8F-1A36-BBC7-564E7D7AD0FB> /usr/lib/libsqlite3.dylib
0x7fff864ff000 - 0x7fff86616fef libxml2.2.dylib ??? (???) <EE067D7E-15B3-F043-6FBD-10BA31FE76C7> /usr/lib/libxml2.2.dylib
0x7fff86b9d000 - 0x7fff86c53fff libobjc.A.dylib ??? (???) <F206BE6D-8777-AE6C-B367-7BEA76C14241> /usr/lib/libobjc.A.dylib
0x7fff86c7b000 - 0x7fff86ca3fff com.apple.DictionaryServices 1.1.1 (1.1.1) <9FD709FC-23F0-F270-EAC1-C590CD516A36> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff86ca4000 - 0x7fff86e62ff7 libSystem.B.dylib ??? (???) <526DD3E5-2A8B-4512-ED97-01B832369959> /usr/lib/libSystem.B.dylib
0x7fff86f17000 - 0x7fff86fe3fff com.apple.CFNetwork 454.5 (454.5) <319C7138-2839-DA5E-413A-618248BD4A32> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x7fff87ab3000 - 0x7fff87b6fff7 com.apple.CoreServices.OSServices 352 (352) <CD933BBD-B260-552F-E64E-291D6ED3091A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff87eaf000 - 0x7fff87efbfff libauto.dylib ??? (???) <072804DF-36AD-2DBE-7EF8-639CFB79077F> /usr/lib/libauto.dylib
0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <526DD3E5-2A8B-4512-ED97-01B832369959> /usr/lib/libSystem.B.dylib

Nov 15, 2009 6:37 AM in response to Kel Solaar

Hello,

I'm pleased not to be alone in the dark (But it's still dark).

I have just received my new Mac Pro (Early 09) last week replacing my 4 years old Power Mac. I bought 2 HD Samsung Model HD103UJ (1000GB each) and put them internal.
I powered my Mac Pro,searched for update (10.6.2), installed my softwares and then the nightmare began:
Frozen Finder, Disk "improperly ejected". I didn't get any "N° 108103", but it's may be because I didn't wait so long.
I got troubles with my internals disks, with firewire HD and when I tried to empty trash.

This is my second "Clean install". I put away my 2 HD Samsung and try to see if it's working.

But with all that I read here on this threat I'm not optimist.

Nov 15, 2009 9:05 AM in response to shotbro

Forgive me if this has been asked and answered but ...

I just installed the .2 update and the icons [including Hard Drive and the few others I have on my desktop] will flash: dissapear and then reapper.

And, the Finder will only open intermittently, when it does not open I get the following message:

The application finder can't be opened
-10810

Can you help?

Much thanks,

Peter

Message was edited by: pberke

Nov 15, 2009 10:05 AM in response to Neil Paisnel

Neil,
Unfortunately I bought it online but I have 14 days to send it back if there is a "latent defect".
I experiment with this new Mac/SL the same losts: time,hair and energy than 10 years ago with Windows when nothing worked but you know than there is may be, somewhere over the rainbow,a solution but you don't find it and you don't sleep...

The application Finder.app can't be opened.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.