Comment 7 for bug 128142

I don't know about the other guys, but the bug happened to me while copying files from one location to another. I've since reattempted the copy while waiting for the bug data to upload and it went smoothly. So I don't know if I can reproduce the bug for a valgrind log. Is there a way to set up a running log or something so the next time if it happens, the log will already be generated without having to reproduce it?