std.vcf locked by application
an address book frozen in time…
Every once in a while Kontact, or maybe it’s Kaddress Book, takes a dump and I’m not able to edit my address files. It sucks, I hate it, but what is even more frustrating is the inability to find a fix for this problem in any reasonable amount of time. Google is no help, maybe if I spoke another language, as the search term only brings up more people who have the problem and were left hanging. I suspect part of the problem is that, first, once the problem is solved no one remembers the error message in the first place. Second, the message is so obscure it’s no help. Third,, the message points you to a folder that is involved, but not involved in the fix. Lastly, there’s frustrating need to enter information but instead having to wait and search / post for a solution.
Well my friends, salvation has arrived. I’m posting this here not only for your use, but also for mine. By the time this happens to me again, I’m sure I’ll have not only forgotten the solution but also where and how I found the fix. The lesson is if you get something like along the lines of:
/home/userName/.kde3.4/share/apps/kabc/std.vcf locked by application
Then erase all the files found in:
/home/userName/.kde/share/apps/kabc/lock
2 Comments
This was the only search result on Google for this problem. Thank you for blogging it!
Yeah, it’s one of those problems. When you have it there’s no solution. After some munging around I managed to figure it out, and of course the next time it happened I’d forgotten what I needed to do. After I looked around I noticed there were plenty of people looking for a solution, but no solution. Hopefully this’ll get cleared up from now on. I think it’s brought on by simultaniously syncing with a PDA and using Kontact.
Post a Comment