Comment 6 for bug 476500

I haven't been able to reproduce the problem in my Fedora 11 VM under the circumstances you described, but I've now run into the same error message while working on an unrelated issue. Unfortunately, I can't reproduce it consistently, so I'll probably need to rely on you to confirm that any forthcoming fix actually fixes it.