Skip navigation

The application Finder.app can't be opened.

463685 Views 693 Replies Latest reply: Mar 14, 2014 2:16 PM by registered99 RSS
  • placid Calculating status...
    Currently Being Moderated
    Sep 6, 2009 11:14 PM (in response to Kel Solaar)
    Same error just popped up.

    It isn't Time Machine because I don't use it.

    Although I have a ReadyNAS, I connect via AFP so I don't think it is CIFS (SMB).

    I did get a Finder window freeze when trying to look at a subdirectory of a mounted drive running FAT32. Attempting to relaunch Finder prompted the error requiring reboot.
    MBP 2.2, Mac OS X (10.6)
  • JimW_DC Calculating status...
    Currently Being Moderated
    Sep 7, 2009 5:33 PM (in response to placid)
    Same problem. I noticed my Lacie drive that supports Time Machine was churning. I turned off the drive; Finder came up properly. I think it's something with the Lacie and, possibly, its interaction with Time Machine. Time Machine has been churning with the Lacie on and off all day ... Thank you.
    Mac Pro, Mac Book, Mini, Mac OS X (10.6), Mini is Tiger O/S
  • Lauco Calculating status...
    Currently Being Moderated
    Sep 7, 2009 6:21 PM (in response to JimW_DC)
    I met the same problem,
    But only with network Users. (LDAP & NFS)

    If I'm log on with my macBook Pro OS X 10.5, no problem.
    If I'm log on with the Mac Pro (with the same network user) Finder Error 10810.

    I try to create a new profile without any success (fresh empty), still the same.
    If I put 777 permission on network profile folder, I can use the mac pro for a while,
    and the finder's error appear.

    And, in every case, the profile work fine with my macBook Pro 10.5.

    Any idea to explore ?

    Thanks
    Mac Pro, Mac OS X (10.6)
  • Osmo Calculating status...
    Currently Being Moderated
    Sep 8, 2009 2:42 AM (in response to Kel Solaar)
    Same problem here. Using SuperDuper with my WD MyBook has been problematic since SL. Finder crashes with this error when trying to do anything with external drives, my Lacie Rugged included. Very annoying
    iMac 20" 2.4 GHz, Mac OS X (10.6)
  • wolrah Calculating status...
    Currently Being Moderated
    Sep 8, 2009 1:14 PM (in response to Kel Solaar)
    Same issue here.

    I was working with files on a network drive (hosted by Samba 3.0.24 on Debian Linux 4.0) and pulled up the Get Info window to change the default file association (whoever's dumb idea it was to have every audio file not only open in iTunes but also import in to the library needs to be removed from the building via cannon) so double-clicking WAVs no longer floods my iTunes library with useless files.

    I clicked the drop-down, selected Quicktime Player, and Finder immediately beachballed. After giving it a minute or two I right-clicked on the Dock and told it to relaunch. Finder went away, then didn't come back. Clicking on the Dock icon brings up the error familiar to this thread.

    From the Terminal, I get a more verbose but unfortunately no more useful error:

    *Phoenix:~ wolrah$ open /System/Library/CoreServices/Finder.app/*
    *LSOpenURLsWithRole() failed with error -10810 for the file /System/Library/CoreServices/Finder.app.*

    As others are also noticing, a process list (ps aux) shows a dead Finder process which does not respond to anything.

    wolrah 92 0.0 0.0 0 0 ?? E 29Aug09 0:00.00 (Finder)


    Doing 'sudo kill 92' doesn't throw an error, but of course it doesn't kill the process either. I've had this problem in the past, there seems to be some failure mode in OS X where a process can die in an unkillable manner. The only way to get this to go away is to reboot. Apple really needs to fix their process management, I've never had a process that root can't kill on a Linux box, yet it's happened to me dozens of times on OS X.
    MacBookPro4,1, Mac OS X (10.6), 2.4GHz, 4GB RAM
  • Ben Steeves Level 1 Level 1 (15 points)
    Currently Being Moderated
    Sep 8, 2009 1:22 PM (in response to wolrah)
    It's called a zombie process (not alive, not dead, can't be killed...) and they happen on Linux too, it's just a bit harder to make them. This issue definitely appears to be related to open files suddenly "going away" and giving Finder the heebie-jeebies. This is nothing new... but the inability to kill and restart Finder is new with SL. It would appear the issue is the open file handle. As people have noted, if the file comes back, Finder can sometimes recover enough to finally die.
  • Lauco Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 8, 2009 3:52 PM (in response to Ben Steeves)
    Hi,

    For more info, in my case, the problem always log this :

    08/09/09 15:04:29 mds[26] (Normal) DiskStore: Rebuilding index for /Network/Servers/enes.loc/vol/home/enes/users/public
    08/09/09 15:04:29 mds[26] (Normal) DiskStore: Creating index for /Network/Servers/enes.loc/vol/home/enes/users/public
    08/09/09 15:04:33 loginwindow[28] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 mds[26] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 coreaudiod[128] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /Applications/TextEdit.app/Contents/MacOS/TextEdit[243] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[182] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 com.apple.audio.coreaudiod[128] coreaudiod: CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /usr/sbin/blued[39] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /Applications/Utilities/Console.app/Contents/MacOS/Console[216] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/Dock.app/Contents/MacOS/Dock[180] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /Library/Parallels/Parallels Service.app/Contents/MacOS/prldispservice[124] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/fontd[190] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 81] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/fontd[282] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Support/fontworker[283] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/Menu Extras/TextInput.menu/Contents/SharedSupport/TISwitcher.app/Contents/MacOS/TISw itcher[205] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[278] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[281] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 com.apple.launchd[1] (com.apple.coreservicesd[46]) Job appears to have crashed: Segmentation fault
    08/09/09 15:04:33 /usr/libexec/UserEventAgent[196] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[280] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/MacOS/iTu nesHelper[207] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 loginwindow[28] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /Applications/TextEdit.app/Contents/MacOS/TextEdit[243] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[182] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/Dock.app/Contents/MacOS/Dock[180] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /Applications/Utilities/Console.app/Contents/MacOS/Console[216] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 81] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /System/Library/CoreServices/Menu Extras/TextInput.menu/Contents/SharedSupport/TISwitcher.app/Contents/MacOS/TISw itcher[205] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 /usr/libexec/UserEventAgent[196] CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
    08/09/09 15:04:33 com.apple.ReportCrash.Root[290] 2009-09-08 15:04:33.726 ReportCrash[290:2703] Saved crash report for coreservicesd[46] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd2009-09-08-150433localhost.crash
    08/09/09 15:08:28 /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[208] No valid tickets, timing out
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 15:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices: _LSDoInitializeProcessesServices() returned 268435459, err=-1 vers=0, we are 10600000. sessionID=0x2100cc0
    08/09/09 16:58:33 /usr/libexec/UserEventAgent[196] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it.


    Hope this help.

    Thanks.

    Lauco
    Mac Pro, Mac OS X (10.6)
  • pmhesse Calculating status...
    Currently Being Moderated
    Sep 9, 2009 9:12 AM (in response to Kel Solaar)
    I just ran into this same thing. Finder had locked up, so I did force-quit, and tried to relaunch it. Got the -10810 error. Here's how I fixed it:

    Launch a terminal window; run "mount" to see what your currently mounted volumes are. In my case, I had mounted a volume from a Windows machine which had since been shut down. So, I unmounted it (umount /Volumes/MOUNTNAME) and then tried restarting Finder. It worked like a charm.
    MacBook Pro, Mac OS X (10.6)
  • fitzyjoe Calculating status...
    Currently Being Moderated
    Sep 9, 2009 3:56 PM (in response to Two Weims)
    I'm having the same problem - When I try to "Connect to Server" from the Finder. I select afp://<the ip address on my vpn>/<share name>. Then, I'm prompted to authenticate. Authentication seems to complete successfully and an entry is created in /Volumes. If I try to expand the volume or do an "ls -al" in Terminal, the Finder freezes. I right-click on Finder and choose to restart it. Then, I'm hosed... Can't start a new Finder with "The Application Finder can't be opened -10810" message. If I wait long enough, the Finder restarts. The shared drive on my server is a Drobo.
    Macbook Pro, Mac OS X (10.6)
  • Two Weims Level 1 Level 1 (50 points)
    Currently Being Moderated
    Sep 10, 2009 8:24 PM (in response to Kel Solaar)
    I have just updated to 10.6.1 with the hope of being rid of the dreaded -10810 error. NO LUCK!
    I even tried the suggestion of unmounting my NAS shares from the terminal but that did not work.
    Two iMac G5s, Two C2D MacBook Pros, & a Mac Mini, Mac OS X (10.6)
  • REBELinBLUE Level 1 Level 1 (5 points)
    Currently Being Moderated
    Sep 11, 2009 2:15 AM (in response to Kel Solaar)
    I too am having this problem, except not with network shares but an external hard drive.

    SL doesn't seem to spin it up again after waking from sleep. You can still see the folder structure you had previously viewed but not any new folders and of course you can't open files.

    Finder/Disk Utility report the disk as mounted, but you can't unmount them. Any apps that attempt to access to drive beach balls. After a fresh restart disk utility reports no problems with the drive

    Restarting also isn't possible as the computer (MBP Unibody) just hangs after everything has shut down, leaving you with just the wallpaper. All I can do is cut the power by holding the power switch.

    The drive worked perfectly in Leopard.

    I reported this issue to Apple 6 days ago (Issue 7201341) but have yet to hear a response
    24" LED Cinema Display and 2.53GHz Macbook Pro, Mac OS X (10.5)
  • Osmo Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 11, 2009 3:56 AM (in response to REBELinBLUE)
    Same problem, exactly. Except on a 20" iMac. When Superduper attempts to do my scheduled backup at night, I wake with an error and then when I do anything with my WD My Book external drive it hangs with that very same scenario you described.
    2.4 GHz 20" iMac, Mac OS X (10.6), 350 MHz PowerMac, 466 MHz PowerMac
  • Jason Sewell Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 11, 2009 10:47 AM (in response to Kel Solaar)
    Having same problem.

    OS: Snow Leopard
    Mac: 2009 MacBook Pro 13 inch
    Drive: Drobo connected to AirPort Extreme Gigabit.

    Everything is software/firmware updated. Plenty of free space all around.
    2009 MacBook Pro 13 inch, Mac OS X (10.6)
  • REBELinBLUE Level 1 Level 1 (5 points)
    Currently Being Moderated
    Sep 11, 2009 10:53 AM (in response to Osmo)
    Interestingly mine is also a WD My Book

    The Maxtor Basics drive doesn't seem to have had the problem from what I have so far seen
    24" LED Cinema Display and 2.53GHz Macbook Pro, Mac OS X (10.5)
  • Osmo Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 11, 2009 1:24 PM (in response to REBELinBLUE)
    I've had my first successful SuperDuper scheduled backup last night. This is what I've tried: connecting with USB instead of FW800, deleting any reference to the WD Drive Manager software (I've read on other threads of the evils of this package, it's not up to date for SL anyways and bombards the console with error messages), upgraded to 10.6.1. Everything has been going smoothly since. Will try using FW800 again soon but I have functionality and a bootable backup so that's all that matters until WD release an update to firmware/software for SL.
    2.4GHz 20" iMac 4GB DDR2 SDRAM, Mac OS X (10.6), 350 MHz PowerMac, 466 MHz PowerMac
1 2 3 4 ... 47 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.