Dreaded 10810 Error
I installed the latest version of Leo4All couple of days ago. Everything seems to be working great but I have gotten this 10810 error twice now already. When looking in the console logs, I see that this is what's causing the error to…
- Primary Author
- @CyCLoBoT Published 2008-09-14
- Collection
- Leopard 10.5
- Archival Footprint
- 4,001 historical reads · 2 curated field notes (from 9 dispatches) · 2008-09-14 – 2008-09-17
- Credited Voices (2)
- @CyCLoBoT (6)@R0GUE (3)
I installed the latest version of Leo4All couple of days ago. Everything seems to be working great but I have gotten this 10810 error twice now already. When looking in the console logs, I see that this is what's causing the error to appear:
13/09/08 10:21:10 PM loginwindow[40] ERROR | -[ScreenSaverDaemon _screenSaverStart:checkMouse:overrideToBlackScreen:] | LSOpenApplication returned -10810
Is there any way I can fix this? This is the same message I had gotten few days back as well. Could my mouse be causing this issue? I have some generic laser mouse (Acrox brand).
Author Updates & Technical Revisions
Follow-up dispatches by @CyCLoBoT
Thanks for the reply ROGUE. One thing though, I don't see that first file. I have these two there instead:
com.apple.LaunchServices-0230.csstore
com.apple.LaunchServices-023501.csstore
Should I delete both these files instead?
Well I deleted both those files and the other one as well. After restarting, those two file appeared again. I wonder if that is the problem with 2 file getting created.
One other thing I noticed was that right after I deleted those files, after a while the screensaver came on but then something was preventing from it to come on. What I mean is that the screen kept on flashing between desktop and screensaver.
Still getting this error on the following file:
16/09/08 5:26:38 PM loginwindow[39] ERROR | -[ScreenSaverDaemon _screenSaverStart:checkMouse :overrideToBlackScreen:] | LSOpenApplication returned -10810
Any other way to fix this?
I was hoping no one wouldn't mention that. I am seriously thinking about switching over to Intel right now.
Synthesized Community Field Notes
2 technical responses curated from 9 original dispatches
This error appears because of a bad process that keeps respawning eventually flooding the proc table. Try deleting the following:
/Library/Caches/com.apple.LaunchServices.6B.csstore
~/Library/Preferences/com.apple.LaunchServices.plist(where '~' means your Home directory, i.e. '/Users/yourname')
Now reboot and repair permissions.
This problem is also related to the dual core timing bug. The only real way to prevent it is to boot with CPUS=1