Hmm... that bug in the most recent version was believed to be Win32-specific. I'm not sure they've been able to nail it down yet... if the assembled monks could work out why the hell it's happening, it would be helpful.