10810 Error
I have installed Leo4All v3 and everything is working smoothly except sometime all of sudden I get the "10810 error". This happens at least once a day and its not just on this version of Leo. I have tried Zephyroth and Kalyway's dvd and…
- Primary Author
- @CyCLoBoT Published 2008-04-26
- Collection
- Leopard 10.5
- Archival Footprint
- 3,101 historical reads · 3 curated field notes (from 4 dispatches) · 2008-04-26 – 2008-04-27
- Credited Voices (3)
- @CyCLoBoT (2)@R0GUE@christurner
- Hardware Reference
- USB 3.2 Boot Flash Drives ↗ AMD Desktop Processors ↗ SATA III & NVMe SSDs ↗
I have installed Leo4All v3 and everything is working smoothly except sometime all of sudden I get the "10810 error". This happens at least once a day and its not just on this version of Leo. I have tried Zephyroth and Kalyway's dvd and still the same. Anyone else experienced this problem? I really hope there is a solution for this issue. It usually goes away if I logout or restart but that's just not convenient to do every single time.
Synthesized Community Field Notes
3 technical responses curated from 4 original dispatches
I've had this numerous times. Unfortunately it happens after prolonged periods of uptime. It's an old bug that stems back to 2004 and has been a problem for owners of real Macs. Basically it's a cache problem with the launch services database that from time to time gets messed up due to too many processes. The culprit that causes this to happen is old non-Leopard proof applications running from within the system. The best thing to do is hunt down and remove any old apps to avoid this from happening. Also download this small app (homepage.mac .com/mdouma46/images/LaunchServicesDatabaseRebuildApp.zip) to rebuild the database. Make sure you kill the finder while rebuilding. Alternatively you could also use Onxy to clean out and rebuild the caches.
The only app that I can think of that was running was QuickSilver. It was the latest beta version. Not sure if it was meant to be for Leopard. So I have closed that one and will see if that was the problem.
i am not sure why, but I seem to get them as well after long up times, with only firefox and adium running. I just Log Out and log back in, problem solved… LOL
Sources & Contributor Provenance (3 credited usernames · Thread #998)
| Username | Dossier Contribution | Dispatches | Active Window |
|---|---|---|---|
| @CyCLoBoT | Primary Author | 2 | 2008-04-26 |
| @R0GUE | Contributor | 1 | 2008-04-26 |
| @christurner | Contributor | 1 | 2008-04-27 |