Comment 2 for bug 917575

It's not clear to me either what causes this. It seems the lock is only held for a very short time, because I don't have to terminate any process and can try the switch again after the revert update dance.

I've never seen the error from bug #901104.

I want to note again that I don't really care about the fact that the operation fails with an error about a lock. It's the fact that the state of the working tree get's screwed up that's the real problem.

I've attached the log from a failed switch and a subsequent click on retry (where it reports the tree is out of date).