Comment 6 for bug 487649

Turns out I had changed something in my local client that made it work with the way it currently is defined in the uploaded module.
I've now fixed this problem and am now able to reproduce this problem consistently regardless of windows/linux.

I'll invalidate this bug for now until I find out why the module still is not behaving like I expect it to.