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.
those of you having the problem with the external drives (as me...), do you guys have FireWire or USB drives connected?
Actually, my LaCie comes with an FW800, FW400 and USB2 connector and since I crashed multiple times yesterday, I choose to try USB today instead of the FW800 I use generally... and lucky me, this was the first day under Snow Leopard the Finder did not crash on me 🙂
BTW, I also believe the disk is not getting that hot.
I have tried my Freecom Datatank on both FW400 and USB on my iMac. It did not seem to make much difference but just maybe slightly less crashes on USB but a lot slower as well. I have also been having the same problems with Iomega eGo FW800 on my MacBook Pro. Time Capsule via Ethernet is fine - no problems.
Yes, I have the quad interface as well but it doesn't seem to make a difference. Today I've had good luck with unplugging the drive once Finder crashed which allows it to restart. I get about an average of 10 minutes between crashes while using the drive.
Finder was using a lot of memory (had 20 or so windows open) so I did a "sudo killall Finder", since in 10.5 that would restart things. It didn't, and now I've got that same error -10810.
Running "open /System/Library/CoreServices/Finder.app" in terminal gives the same error as clicking the icon in dock:
"LSOpenURLsWithRole() failed with error -10810 for the file /System/Library/CoreServices/Finder.app."
Here's the interesting part, running:
"sudo open /System/Library/CoreServices/Finder.app" doesn't give that error! Of course it doesn't do me any good, since I'm not logged in as su, but this may be a permissions thing.
Same problem, Finder not responding. Cannot open Finder. However, as soon as I unplugged Time Machine external WD drive Finder relaunched.
Now have the choice of no Finder or No backup.
We need an answer from Apple
You can still do your back-ups. You just have to eject the drive after doing the back up but before your Mac goes to sleep. You can alter the settings in Energy Saver to give yourself a wider time window (sorry for using the 'W' word!)
Same problem here. Since upgrading my Macbook Pro (late 2009) to 10.6.1 I was unable to successfully mount network shares over AFP. After a reboot it worked again, but after waking up from sleep mode any attempt would hang the finder. Force quit and restart of the finder resulted in de dreaded -10810.
Reinstall of 10.6.0 did not resolve the problem, nor did all standard fixes (permissions etc.) or the tips in Maxfixit.
Since my Macbook is still new and has no critical data on it, I decided to try an erase&install of SL. Somehow this has completely solved the problem for me. I think I tried everything to reproduce the error, but until now all mounting scenarios work without a hitch. Fast browsing of the shares is also ok now as is mounting over Firewire, USB en card-slot.
It seems that there is some leftover from 10.5 that is causing this problem. It is as if after sleep the mounter, instead of checking the current (and renewed) network configuration, relies on some old preference file or cash....
No external Firewire or USB drives, but I was using a Terminal to SSh to a networked NAS box when it appeared. Cant do a re boot just yet as I am ripping some music from old cassette tape.
I think Apple have introduced all this stuff as a sort of way to Welcome people like myself, that have just switched away from Windows to get away from problems like this. Very pi
*d off with this £2000 doorstop
I had the same problem and it seems like I got this a lot when I connect my 4th generation iPod classic I use both on Mac and on PC, so I think it's related to the external hard disc too.
Just got this back from Apple in response to my bug report:
"This is a follow up to Bug ID# 7256664. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 7152276. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#."
I've received that response before (for a different bug). It appears that I can't see your reported bugs and you can't see mine. The most unfortunate thing is that neither of us can see the original bug report that this is duplicating.
When I click on "State" in the bug report, it defines Duplicate:
"The reported issue is being tracked under the original bug number. You may check status of this issue by writing to ADC Bug Reporting (devbugs@apple.com)."
My Finder error happened through a VPN connection to my home server that is connected to a Drobo over USB.
I helped a customer solve this problem by doing these steps.
1. Boot from his original Install DVD or boot from whatever DVD you installed the current OS from.
2. Run Disk Utility and repair the disk.
3. Reboot and log in.
This fixed the issue for my client. Hope this helps!