10810 error on mac osx
i’ve recently been getting the horrible 10810 error upon trying to launch a new program. a bunch of investigation online resulted in the following information (which i have compiled for my uses, and anybody else that suffers the same problem):
Symptoms: cannot launch new programs.
Problem definition: The following file defines the error -10810:
/System/Library/Frameworks/CoreServices.framework/… /Frameworks/LaunchServices.framework/… /Headers/LSInfo.h
as:
/* ======================================================== */
/* LaunchServices Type & Constants */
/* ======================================================== */
enum {
kLSUnknownErr = -10810, /* Unexpected internal error*/
};
Basically, it means that the Launch Services framework is misbehaving and is encountering errors when trying to launch an application.
Potential solutions:
1) open Activity Monitor, sort by thread, and close whatever has the most threads open. Certain programs launch new threads often, and at times, they get bad at killing them, so many threads will be open. Keep closing stuff until you can launch programs again.
2) unmount any external devices (not clear how this is related, but empirically, some people seem to use this solution effectively).
3) Remove from the Dock any “old” preference panes, in particular, preference panes that are not updated for your current osx version.
4) Uninstall or update any “old” programs, in particular, ones that do not support your current osx version.
5) Reboot
6) Rebuild launch services, by typing the following into terminal (on one line, without backslashers). Note that the below is for Leopard. Do a search for the appropriate command for other versions. Also, some programs will allegedly do it for you, such as OnyX. See http://reviews.cnet.com/8301-13727_7-10362043-263.html?tag=mncol;txt for details:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/\
LaunchServices.framework/Versions/A/Support/lsregister -kill\
-r -domain local -domain system -domain user
7) Fix permissions and disk.
See also http://reviews.cnet.com/8301-13727_7-10365239-263.html for some additional ideas. I may have solved the problem, but maybe not yet, so I might update this soon.
