Comment 15 for bug 1016559

Vim, I'm learning too, but when I ran into that problem, I found that I was able to free up the lock by using the system monitor and then locating the process using it. I tried to end it in the GUI, however root was the owner, so I used:

   sudo pkill PROCESS

And that seemed to clear up the issue. Someone please correct me if I'm wrong/there is a better way to do this. That error was a frequent occurance, as I exited terminal when the Dropbox bug froze the configuration process.

Hope I helped,