Comments on: Launch Services Cache Corruption

By: Luke Rodies

Luke Rodies — Sat, 28 Feb 2009 20:25:19 +0000

Thanks for this posting. My wife was having this problem. (login loop). Luckily, I had a second admin account on her machine. From the command line in the second account, I su(d) into her account and renamed the associated ‘csstore’ file. The problem is resolved.

By: Jose Luis

Jose Luis — Sun, 28 Sep 2003 21:26:34 +0000

I just want also thank you for your post. I have spent two days trying to get my os x to log in, but only got the same bad result. I have been reading about people having the same problem and resolving it by a similar way (deleting preferences files, the .plist ones under home directories), etc. But thanks to you now I am not going to wipe my disk
But I still keep thinking how did you found that that f***ing file was corrupt? Maybe by doing a ‘find / -inum xxxxx’ after running fsck?
Thank you very much.
Jose Luis Garcia

By: Andrew

Andrew — Mon, 08 Sep 2003 20:47:40 +0000

I would also like to thank you. I had the same problem as blah, due to the fact that i’d let myself run ridiculously low on space. I had determined (through looking at which crash logs were updated) that the problem was with lsregister or lsrecenttool, but was afraid i’d have to reinstall my whole damn system.
Interesting sidenote: it seems that inducing some sort of dialog box bypasses this corrupted login cache and lets you log in. For example, I was able to log in by starting up with an external HD on, then switching it off, prompting the “you’ve removed a drive. you are a bad person” dialog box, which seemed to trigger login.
In any case, THANK YOU!

By: Blah

Blah — Sat, 09 Aug 2003 19:39:59 +0000

I just wanted to thank you for this post. I began to experience this login issue today, and spent more time than I care to admit trying to figure it out. I found a few other weird things running Disk Utility from cd (overlapped extent allocations), but the login issue continued after resolving those. After a few Google searches, I found your post, and my login issue is now resolved.
Thanks again.