29 Oct
2009
29 Oct
'09
10:08 p.m.
If this really started happening only with v1.2.4 -> v1.2.5, the only change that looks anything like it could have to do with this problem is the attached patch. I guess you could try reversing it and seeing if it helps..